MWeb Trace - Giant delay in local hops

[Reelix]

I recently did a trace to www.adobe.com today out of curiosity, and saw a rather large jump between two local hops:

  5    24 ms    24 ms    22 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210]
  6   245 ms   245 ms   245 ms  pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]

Wondering if this was a one-time discrepency, I tried pinging:

C:\>ping -t 196.22.169.210

Pinging 196.22.169.210 with 32 bytes of data:
Reply from 196.22.169.210: bytes=32 time=23ms TTL=251
Reply from 196.22.169.210: bytes=32 time=23ms TTL=251
Reply from 196.22.169.210: bytes=32 time=22ms TTL=251
Reply from 196.22.169.210: bytes=32 time=22ms TTL=251
Reply from 196.22.169.210: bytes=32 time=22ms TTL=251

Ping statistics for 196.22.169.210:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 23ms, Average = 22ms

C:\>ping -t 196.22.163.230

Pinging 196.22.163.230 with 32 bytes of data:
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250
Reply from 196.22.163.230: bytes=32 time=244ms TTL=250

Ping statistics for 196.22.163.230:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 244ms, Maximum = 244ms, Average = 244ms

Since a location-lookup shows they're both SA Based (It might be wrong) - Can anyone account for the giant delay between these two hops?

 

[grim]

tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210] is in South Africa
pos-1-2-0.LON-up-1.mweb.co.za [196.22.163.230] is in London

Hence the jump in latency.

 

[freematrix]

Here is IS's hop internationally to adobe.com.
4 core2b-rba-te2-0-0.ip.isnet.net (196.26.0.182) 10.812 ms 11.566 ms 11.565 ms
5 mi-za-rba-p6-gi3-0-2-106.ip.isnet.net (168.209.164.77) 211.290 ms 211.106 ms 211.520 ms
6 mi-uk-dock-p2-po2-3.ip.isnet.net (168.209.161.91) 210.766 ms 211.792 ms 210.749 ms

 

[Reelix]

tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210] is in South Africa
pos-1-2-0.LON-up-1.mweb.co.za [196.22.163.230] is in London

Hence the jump in latency.

Aaah, thanks!

I tried three different IP-To-Location sites, and all of them showed 196.22.163.230 was in South Africa... Weird :|

 

[grim]

That IP address belongs to MWeb which is why it lists it as being in South Africa, those services don't physically determine where the IP is located. They check the registration details for that IP.

So if you're on a WebAfrica ADSL account and you check the IP your router gets it'll list it in Cape Town, even if you live in Pretoria.