Better EDGE latency

[km2]

Has anyone else still stuck on EDGE noticed that over the past few days ping times have dropped quite nicely on MTN? I used to be getting a minimum of 850ms to US sites, but recently it's dropped down to 500ms. That's not that far away from dialup!

I know that in the US they were improving performance of EDGE networks to help the iPhone, and maybe some of those improvements filtered down to us. Or maybe it's just wishful thinking on my part.

Of course it will still be nicer if MTN rolled out HSDPA to Welcome Glen...

 

[km2]

More details

Just to follow up on that post with some numbers, I tried pinging mybroadband.co.za while on Vodacom and MTN (both under EDGE with an HTC TyTN):

MTN EDGE:

Pinging 196.40.97.13 with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=232ms TTL=241
Reply from 196.40.97.13: bytes=32 time=310ms TTL=241
Reply from 196.40.97.13: bytes=32 time=237ms TTL=241
Reply from 196.40.97.13: bytes=32 time=297ms TTL=241

Ping statistics for 196.40.97.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 310ms, Average = 269ms

Vodacom EDGE:

Pinging 196.40.97.13 with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=749ms TTL=243
Reply from 196.40.97.13: bytes=32 time=630ms TTL=243
Reply from 196.40.97.13: bytes=32 time=729ms TTL=243
Reply from 196.40.97.13: bytes=32 time=608ms TTL=243

Ping statistics for 196.40.97.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 608ms, Maximum = 749ms, Average = 679ms

All I can say is well done MTN/Ericsson! Now if you can just fix your DNS servers so I don't have to keep refreshing to get my pages to load, I'll be happy!

 

[redarrow]

Hmm... you appear to be right..

I hadn't noticed.. but I tried it out now and I'm defintely getting better pings than usual.. on HSDPA btw..

Local:

PING www.myadsl.co.za (196.40.97.13) 56(84) bytes of data.
64 bytes from 196.40.97.13: icmp_seq=1 ttl=242 time=177 ms
64 bytes from 196.40.97.13: icmp_seq=2 ttl=242 time=130 ms
64 bytes from 196.40.97.13: icmp_seq=3 ttl=242 time=120 ms
64 bytes from 196.40.97.13: icmp_seq=4 ttl=242 time=157 ms

--- www.myadsl.co.za ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 120.276/146.380/177.666/22.569 ms

International:

PING www.l.google.com (216.239.59.104) 56(84) bytes of data.
64 bytes from gv-in-f104.google.com (216.239.59.104): icmp_seq=1 ttl=243 time=287 ms
64 bytes from gv-in-f104.google.com (216.239.59.104): icmp_seq=2 ttl=243 time=284 ms
64 bytes from gv-in-f104.google.com (216.239.59.104): icmp_seq=3 ttl=243 time=284 ms
64 bytes from gv-in-f104.google.com (216.239.59.104): icmp_seq=4 ttl=243 time=284 ms

--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 284.222/285.371/287.614/1.425 ms

Not so bad at all..

 

[Sselmrah]

Same here. on MTN 3G

Pinging www.l.google.com [209.85.135.104] with 16 bytes of data every 10 ms:

Reply[1] from 209.85.135.104: bytes=16 time=341.7 ms TTL=240
Reply[2] from 209.85.135.104: bytes=16 time=298.9 ms TTL=240
Reply[3] from 209.85.135.104: bytes=16 time=296.4 ms TTL=240
Reply[4] from 209.85.135.104: bytes=16 time=319.6 ms TTL=240
Reply[5] from 209.85.135.104: bytes=16 time=291.5 ms TTL=240
Reply[6] from 209.85.135.104: bytes=16 time=304.6 ms TTL=240
Reply[7] from 209.85.135.104: bytes=16 time=322.1 ms TTL=240
Reply[8] from 209.85.135.104: bytes=16 time=304.0 ms TTL=240
Reply[9] from 209.85.135.104: bytes=16 time=301.5 ms TTL=240

Ping statistics for 209.85.135.104:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 291.5 ms, Maximum = 341.7 ms, Average = 309 ms