ping response for your ISP, how good is it!?

techead

techead

Honorary Master
Joined
Apr 11, 2008
Messages
12,185
Reaction score
48
Location
by the mountain
ping 209.85.147.104 and post your result with your ISP name and ADSL sync speed


Im trying to understand how there can be such significant differences in ping response for ISP's

I have an openweb uncapped line and my ping to EU is considerably higher when compared to these IS resold accounts. (axxess/afrihost/cybersmart)

Can someone please explain to me why? :confused:

Im on a 10mb line with good line health/stats, and my mate is on 384k line also healthy.

We were playing Hon and he was getting 220ms (cybersmart) and I was getting 330ms (openweb). That is a HUGE difference. I switch over to a prepaid axxess account and then mine also comes right down.

so why??? is it only the routing?? different undersea cables??
 
Yes the difference in ping is related to the routing used.

Rather do a tracert to the IP and you'll see the difference in the routing.

Mweb 4Mb Business Uncapped:

Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=225ms TTL=52
Reply from 209.85.147.104: bytes=32 time=225ms TTL=52
Reply from 209.85.147.104: bytes=32 time=229ms TTL=52
Reply from 209.85.147.104: bytes=32 time=224ms TTL=52

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

Tracert:

Tracing route to bru01m01-in-f104.1e100.net [209.85.147.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.1.3
2 1 ms 1 ms 1 ms 41-134-201-225.dsl.mweb.co.za [41.134.201.225]
3 22 ms 24 ms 23 ms 197-81-146-2.jhb.mweb.co.za [197.81.146.2]
4 14 ms 27 ms 18 ms 197-81-146-4.jhb.mweb.co.za [197.81.146.4]
5 51 ms 49 ms 54 ms TenGigE0-1-0-0.12.vic-up-2.mweb.co.za [196.22.16
9.242]
6 107 ms 87 ms 126 ms 197-84-4-34.cpt.mweb.co.za [197.84.4.34]
7 55 ms 55 ms 50 ms ge1-0-1.cpt-cinx-2.mweb.co.za [196.28.178.137]
8 51 ms 58 ms 44 ms google.cinx.net.za [196.223.22.41]
9 226 ms 222 ms 216 ms 209.85.248.215
10 226 ms 211 ms 211 ms 209.85.252.44
11 213 ms 212 ms 226 ms 209.85.253.92
12 218 ms 218 ms 218 ms 72.14.232.134
13 216 ms 218 ms 218 ms 209.85.252.83
14 221 ms 216 ms 235 ms 216.239.46.221
15 218 ms 219 ms 218 ms bru01m01-in-f104.1e100.net [209.85.147.104]

Trace complete.
 
Last edited:
so its nothing like IS are using SAT cable and openweb are using seacom??

ie. one cable is "slower" than the other?
 
I'm on 384kbps line with good line stats, Afrihost is my ISP.

Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=274ms TTL=49
Reply from 209.85.147.104: bytes=32 time=274ms TTL=49
Reply from 209.85.147.104: bytes=32 time=274ms TTL=49
Reply from 209.85.147.104: bytes=32 time=274ms TTL=49

Ping statistics for 209.85.147.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 274ms, Maximum = 274ms, Average = 274ms
 
4Mbps line, 4Mbps Home Uncapped Web Africa account.

Code: 
C:\Users\Tinuva>tracert 209.85.147.104

Tracing route to bru01m01-in-f104.1e100.net [209.85.147.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.heaven.za.net [10.0.0.1]
  2     7 ms     7 ms     7 ms  wblv-ip-esr-4.ipnet.wa.co.za [41.185.84.1]
  3    47 ms     8 ms    24 ms  wnls-ipc1-vl-108.wa.co.za [196.220.59.238]
  4    26 ms    15 ms    12 ms  wnls-cr2-vl-801.wa.co.za [41.185.0.66]
  5    10 ms    28 ms    17 ms  wbrs-csw1-vl-140.wa.co.za [41.185.1.5]
  6    12 ms    10 ms    10 ms  google.cinx.net.za [196.223.22.41]
  7   174 ms   179 ms   162 ms  209.85.248.215
  8   189 ms   162 ms   160 ms  209.85.252.44
  9   164 ms   162 ms   187 ms  209.85.253.92
 10   207 ms   189 ms   183 ms  66.249.95.173
 11   218 ms   167 ms   167 ms  209.85.251.231
 12   168 ms   196 ms   172 ms  216.239.46.253
 13   167 ms   168 ms   169 ms  bru01m01-in-f104.1e100.net [209.85.147.104]

Trace complete.
 
I used to get about 190ms to the UK with my Telkom account and about 230ms with my Mweb uncapped account but since Telkom went uncapped I get 350ms using them while my mweb has stayed at 230ms. Bit pissed at telkom as it used to be ideal for BF3 on console but no longer.
 
It depends where you are situated vs where your ISP is situated to an extent and then which cable they use, SAT3 is slightly shorter than Seacom so if you get routed through SAT3 your latency will be slightly lower.

Generally I've found that with WebAfrica I get the lowest international pings but not local as they are CPT based and I'm in PTA so all my traffic gets routed through CPT.
 
All on 384k line

WA Silver (RedAfrica): 216ms
AH capped: 256ms
Cybersmart: 276ms
Axxess Semi: 226ms

AH wins for local gaming by quite a bit(GP->GP servers), WA for international. Don't really use the Axxess a/c anymore & cybersmart cap I burn on some random downloads...not good for anything else. I think the Axxess a/c would perform the same as the AH for local gaming, but not particularly interested in testing that theory.

WA Silver (RedAfrica) said:
Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=227ms TTL=51
Reply from 209.85.147.104: bytes=32 time=203ms TTL=51
Reply from 209.85.147.104: bytes=32 time=229ms TTL=51
Reply from 209.85.147.104: bytes=32 time=205ms TTL=51

Ping statistics for 209.85.147.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 203ms, Maximum = 229ms, Average = 216ms
Click to expand...

Afrihost capped said:
Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=256ms TTL=49
Reply from 209.85.147.104: bytes=32 time=257ms TTL=49
Reply from 209.85.147.104: bytes=32 time=254ms TTL=49
Reply from 209.85.147.104: bytes=32 time=258ms TTL=49

Ping statistics for 209.85.147.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 254ms, Maximum = 258ms, Average = 256ms
Click to expand...

Cybersmart/IC voucher said:
Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=273ms TTL=48
Reply from 209.85.147.104: bytes=32 time=271ms TTL=48
Reply from 209.85.147.104: bytes=32 time=267ms TTL=48
Reply from 209.85.147.104: bytes=32 time=272ms TTL=48

Ping statistics for 209.85.147.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 273ms, Average = 270ms
Click to expand...

Axxess Semi said:
Pinging 209.85.147.104 with 32 bytes of data:
Reply from 209.85.147.104: bytes=32 time=227ms TTL=51
Reply from 209.85.147.104: bytes=32 time=228ms TTL=51
Reply from 209.85.147.104: bytes=32 time=225ms TTL=51
Reply from 209.85.147.104: bytes=32 time=226ms TTL=51

Ping statistics for 209.85.147.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 228ms, Average = 226ms
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X