Amobia Latency - Local, Singapore, Germany and London

[MDE]

I was requested by a forum member to do some tests for him.
Amobia 1MB Uncapped. CPT. 2kms from High Site. Clear Day.

If there is another IP one would like to test just PM and I'll get around to it and add to the list.

See below:

Ping - 203.116.155.134

Peak

C:\Users\Matt>ping 203.116.155.134

Pinging 203.116.155.134 with 32 bytes of data:
Reply from 203.116.155.134: bytes=32 time=554ms TTL=107
Reply from 203.116.155.134: bytes=32 time=578ms TTL=107
Reply from 203.116.155.134: bytes=32 time=564ms TTL=107
Reply from 203.116.155.134: bytes=32 time=544ms TTL=107

Ping statistics for 203.116.155.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 544ms, Maximum = 578ms, Average = 560ms

Off Peak

C:\Users\Matt>ping 203.116.155.134

Pinging 203.116.155.134 with 32 bytes of data:
Reply from 203.116.155.134: bytes=32 time=542ms TTL=107
Reply from 203.116.155.134: bytes=32 time=553ms TTL=107
Reply from 203.116.155.134: bytes=32 time=545ms TTL=107
Reply from 203.116.155.134: bytes=32 time=541ms TTL=107

Ping statistics for 203.116.155.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 541ms, Maximum = 553ms, Average = 545ms

Ping - 203.116.155.135

Peak

C:\Users\Matt>ping 203.116.155.135

Pinging 203.116.155.135 with 32 bytes of data:
Reply from 203.116.155.135: bytes=32 time=583ms TTL=106
Reply from 203.116.155.135: bytes=32 time=587ms TTL=106
Reply from 203.116.155.135: bytes=32 time=592ms TTL=106
Reply from 203.116.155.135: bytes=32 time=583ms TTL=106

Ping statistics for 203.116.155.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 583ms, Maximum = 592ms, Average = 586ms

Off Peak

C:\Users\Matt>ping 203.116.155.135

Pinging 203.116.155.135 with 32 bytes of data:
Reply from 203.116.155.135: bytes=32 time=566ms TTL=106
Reply from 203.116.155.135: bytes=32 time=561ms TTL=106
Reply from 203.116.155.135: bytes=32 time=586ms TTL=106
Reply from 203.116.155.135: bytes=32 time=591ms TTL=106

Ping statistics for 203.116.155.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 561ms, Maximum = 591ms, Average = 576ms

Ping - 173.199.105.7

Peak

C:\Users\Matt>ping 173.199.105.7

Pinging 173.199.105.7 with 32 bytes of data:
Reply from 173.199.105.7: bytes=32 time=223ms TTL=111
Reply from 173.199.105.7: bytes=32 time=194ms TTL=111
Reply from 173.199.105.7: bytes=32 time=190ms TTL=111
Reply from 173.199.105.7: bytes=32 time=345ms TTL=111

Ping statistics for 173.199.105.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 345ms, Average = 238ms

Off Peak

C:\Users\Matt>ping 173.199.105.7

Pinging 173.199.105.7 with 32 bytes of data:
Reply from 173.199.105.7: bytes=32 time=217ms TTL=111
Reply from 173.199.105.7: bytes=32 time=213ms TTL=111
Reply from 173.199.105.7: bytes=32 time=208ms TTL=111
Reply from 173.199.105.7: bytes=32 time=243ms TTL=111

Ping statistics for 173.199.105.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 208ms, Maximum = 243ms, Average = 220ms

Ping - 91.198.152.188

Peak

C:\Users\Matt>ping 91.198.152.188

Pinging 91.198.152.188 with 32 bytes of data:
Reply from 91.198.152.188: bytes=32 time=226ms TTL=115
Reply from 91.198.152.188: bytes=32 time=226ms TTL=115
Reply from 91.198.152.188: bytes=32 time=272ms TTL=115
Reply from 91.198.152.188: bytes=32 time=225ms TTL=115

Ping statistics for 91.198.152.188:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 272ms, Average = 237ms

Off Peak

C:\Users\Matt>ping 91.198.152.188

Pinging 91.198.152.188 with 32 bytes of data:
Reply from 91.198.152.188: bytes=32 time=278ms TTL=115
Reply from 91.198.152.188: bytes=32 time=236ms TTL=115
Reply from 91.198.152.188: bytes=32 time=237ms TTL=115
Reply from 91.198.152.188: bytes=32 time=218ms TTL=115

Ping statistics for 91.198.152.188:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 218ms, Maximum = 278ms, Average = 242ms

Ping - www.bing.com

C:\Users\Matt>ping www.bing.com

Pinging a134.lm.akamai.net [165.165.46.16] with 32 bytes of data:
Reply from 165.165.46.16: bytes=32 time=50ms TTL=52
Reply from 165.165.46.16: bytes=32 time=35ms TTL=52
Reply from 165.165.46.16: bytes=32 time=46ms TTL=52
Reply from 165.165.46.16: bytes=32 time=54ms TTL=52

Ping statistics for 165.165.46.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 54ms, Average = 46ms

UPDATE - 01 Nov 2012

Ping - 196.4.79.82 - Request Timed Out.

Ping - 41.185.60.19
C:\Users\Matt>ping 41.185.60.19

Pinging 41.185.60.19 with 32 bytes of data:
Reply from 41.185.60.19: bytes=32 time=155ms TTL=119
Reply from 41.185.60.19: bytes=32 time=157ms TTL=119
Reply from 41.185.60.19: bytes=32 time=162ms TTL=119
Reply from 41.185.60.19: bytes=32 time=192ms TTL=119

Ping statistics for 41.185.60.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 192ms, Average = 166ms

Ping - 152.111.192.230
C:\Users\Matt>ping 152.111.192.230

Pinging 152.111.192.230 with 32 bytes of data:
Reply from 152.111.192.230: bytes=32 time=13ms TTL=122
Reply from 152.111.192.230: bytes=32 time=137ms TTL=122
Reply from 152.111.192.230: bytes=32 time=143ms TTL=122
Reply from 152.111.192.230: bytes=32 time=130ms TTL=122

Ping statistics for 152.111.192.230:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 143ms, Average = 105ms

Speedtest - Local (CPT)
Peak http://www.speedtest.net/result/1989472459.png
Off Peak http://www.speedtest.net/result/1989993860.png

Speedtest - Local (JHB)
Peak http://www.speedtest.net/result/1989477781.png
Off Peak http://www.speedtest.net/result/1989995743.png

Speedtest - London
Peak http://www.speedtest.net/result/1989469719.png
Off Peak http://www.speedtest.net/result/1989997329.png ( very surprised by this one )

Speedtest - Frankfurt, Germany
Peak http://www.speedtest.net/result/1989448386.png
Off Peak http://www.speedtest.net/result/1989999692.png

Speedtest - Singapore
Peak http://www.speedtest.net/result/1989467166.png
Off Peak http://www.speedtest.net/result/1990004563.png

 

[vavyn]

Just want to ask , does the distance from your house to the access point will influence the speed and latency?

 

[MDE]

It shouldn't as they should fine tune it on site. Apparently they can also do it from the control room :erm: Anyway just put it in incase someone wants to know.

 

[Franna]

Can you please ping www.bing.com to test if they redirect to a local Akamai Edge CDN server.

 

[MDE]

Can you please ping www.bing.com to test if they redirect to a local Akamai Edge CDN server.

Done. added to OP

 

[vavyn]

Got another request. Could you retest the ping again like at 9pm or so just want to see the difference in latency between peak and off peak.

 

[MDE]

will do.

 

[vavyn]

Thanks for the update!

 

[KickTheBucket]

I got Amobia yesterday. So far I'm overjoyed with it compared to my iBurst. I'm in Kyalami.

Johannesburg (Saturday Morning):
http://www.speedtest.net/result/1999035210.png

London (Saturday Morning):
http://www.speedtest.net/result/1999089236.png

 

[MDE]

welcome to the good life.

 

[Haterade]

Can you please do latency tests to (at any time of the day):

41.185.60.19
196.4.79.82
152.111.192.230

These are IPs are from WAGE, SGS and gmz Respectively. The place I'll be staying at uses Amobia (They don't allow you to get Telkom lines) and I'm really curious about the latency for gamers.

 

[MDE]

Updated - Check the first post.

Regards MDE

Can you please do latency tests to (at any time of the day):

41.185.60.19
196.4.79.82
152.111.192.230

These are IPs are from WAGE, SGS and gmz Respectively. The place I'll be staying at uses Amobia (They don't allow you to get Telkom lines) and I'm really curious about the latency for gamers.

 

[YangZA]

Try Using "tracert -d <ip/hostname>" rather than ping,

it will indicate where the latency is generated.

also, phone the Callcentre and have them fix your link, your latencies are terrible.

 

[MDE]

Try Using "tracert -d " rather than ping,

it will indicate where the latency is generated.

also, phone the Callcentre and have them fix your link, your latencies are terrible.

Thanks for the tip. During the day I achieved a 20ms ping at night between 7-9 its 100ms more. When signing an uncapped account with Amobia they ask what you'll be using it for. If you play games which I don't they suggest you take a capped product. The latencies aren't a big problem for me.

PS. Seems they have changed from Mweb to Altech for there accounts. Maybe issues on Altechs systems?

PPS. Okay now i'm confused. the IP range when doing a Speedtest shows that its Mweb but when doing a whoisip it says it Autopage Cellular?

 

[Haterade]

So the Capped packages don't have shaping at any time of the day?

 

[MDE]

They have higher priority over the uncapped products. Because they cost a hellava lot more per gig. Not sure on shaping.

 

[vamsi77]

Have anybody tried voip or skype calls on amobia? how is the latency and call quality?