Can anyone post the cmd latency for bbc.co.uk and other eu servers please? I am an IDM subscriber and thinking of switching to Sodetel since I am hearing that their latency improved after the upgrade. IDM are refusing to give me a 4 mbps speed. Sodetel's regular entry plans are up to 4 mbps and higher plans have higher upload speeds. In case the speeds and latency are stable I will definitely switch to Sodetel.
This is ping to bbc.co.uk
pingtest

This is ping to lux.valve.net (Luxembourg)
pingtest2
Thanks georgesmh, I am concerned about the stability of the latency and speed. From the pictures you've posted, it is pretty much like IDM's.
Sodetel has a ping tools program ? Never heard of it !
The pings are currently good but we can't guarantee that they will stay like this forever, they've been bad for a long time.

This is my latency over wifi :
Envoi d_une requête 'ping' sur www.google.com [173.194.35.113] a
 données :
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54

Statistiques Ping pour 173.194.35.113:
    Paquets : envoyés = 20, reçus = 20, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 95ms, Maximum = 98ms, Moyenne = 96ms
Envoi d_une requête 'ping' sur lux.valve.net [146.66.152.1] avec 32 octets de do
nnées :
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=108 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=106 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=107 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=107 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=103 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=202 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=106 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=308 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=114 ms TTL=52

Statistiques Ping pour 146.66.152.1:
    Paquets : envoyés = 20, reçus = 20, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 103ms, Maximum = 308ms, Moyenne = 120ms
You can ignore the 300ms, someone was probably eating some bandwidth in the house.
Sorry for the French, I'm not using my own computer currently.
This is a multiple tests tool created by me and a colleague when we were interns at Sodetel :p
Yeah normally the pings are higher. I hope they stay like this.
Oh nice ! Why didn't you publish it online ? And how was the internship at Sodetel ? I'm interested. Thanks for any info.
We didn't know about this forum before and they told us that they will put it on their website but never did :p They use it themselves in offices though. Here it is if someone is interested in using it: https://dl.dropboxusercontent.com/u/22107212/Sodetel%20Application.zip
There are some bugs since this is the first serious app that we ever did, but it's perfectly usable.

PS: Since I directly sent the standalone app not the installer you should download and paste these 2 files in "Documents" for the SpeedTest to work. They contain the download servers. You can change them in the text files.

https://dl.dropboxusercontent.com/u/22107212/Server%201.txt
https://dl.dropboxusercontent.com/u/22107212/Server%202.txt
downloaded both files. The speed test didn't work.
Server 2 file isn't present or something like that.
8 days later
Yes they should both be in Documents folder. Anyway it's a step needed only here because i sent the standalone app. Everything's else working fine? Couldn't reply earlier sorry didn't notice the reply.
Muh internet is down for more than an hour now.
9 days later


still no change, with the unlimited plan...
Ping to Beirut on average should be in the 50s or 60s i believe.
andrew55 wrotePing to Beirut on average should be in the 50s or 60s i believe.
On a good day I get 120ms
4 days later
I've been with the same public IP since the upgrade, it's like I got a free static IP. Am I the only one?
Doesn't look shared to me. How can I make sure?

I remember when I had a shared IP, I would go to a HTTP website like whatismyipaddress.com and it would shoe an IP starting with 212 and it changes after every refresh strangely. That's not the case now.