Sure.
Code:C:\Users\Tinuva>tracert 196.30.66.46 Tracing route to 196.30.66.46 over a maximum of 30 hops 1 4 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1] 2 7 ms 6 ms 18 ms 196-209-37-1.dynamic.isadsl.co.za [196.209.37.1] 3 7 ms 18 ms 6 ms 196.38.72.125 4 18 ms 8 ms 18 ms 196.35.115.136 5 9 ms 24 ms 9 ms core2a-ctn-gi0-1.ip.isnet.net [168.209.2.6] 6 7 ms 16 ms 8 ms 168.209.2.130 7 7 ms 21 ms 6 ms 41-208-29-210.mtnns.net [41.208.29.210] 8 7 ms 7 ms 15 ms 196.44.0.75 9 45 ms 59 ms 59 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250] 10 38 ms 42 ms 39 ms 196.44.31.97 11 37 ms 63 ms 49 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12] 12 40 ms 51 ms 51 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25] 13 37 ms 48 ms 36 ms tengigabitethernet5-1.hr10.jnb6.za.mtnbusiness.n et [196.31.63.154] 14 38 ms 47 ms 37 ms 196.30.66.46 Trace complete.
The trace on the other account still looks the same, just looks like the IS account now is back to what it used to be before what I experienced yesterday (Saterday).
Was odd to see 90-100ms in online games, when it used to be around 30-50ms.
Thanks for this. Up to 168.209.2.130 IS have control over where-after it jumps over the (private) peering link to MTN. I just wanted to compare the first five traces ito latency.