South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Tracing route to xxx [196.36.239.xxx]
over a maximum of 30 hops:
1 55 ms 18 ms 17 ms dsl-146-64-01.telkomadsl.co.za [165.146.64.1]
2 17 ms 17 ms 16 ms rrba-ip-er-1-fe-8-0-0-1.telkom-ipnet.co.za [196.43.11.146]
3 339 ms 354 ms 339 ms lon-ip-dir-telecity-pos-5-0.telkom-ipnet.co.za [196.43.9.50]
4 340 ms 340 ms 339 ms ge9-16.br02.ldn01.pccwbtn.net [63.218.13.13]
5 342 ms 340 ms 340 ms POS4-2.BR1.LND9.ALTER.NET [146.188.69.205]
6 341 ms 344 ms 341 ms so-0-2-0.TR1.LND9.ALTER.NET [146.188.7.241]
7 342 ms 342 ms 343 ms so-6-1-0.TR1.LND2.ALTER.NET [146.188.4.81]
8 345 ms 345 ms 353 ms so-5-0-0.XR1.LND2.ALTER.NET [146.188.7.221]
9 348 ms 341 ms 401 ms POS3-0.CR1.LND5.alter.net [158.43.233.241]
10 385 ms 339 ms 339 ms fe0-0-0.gw13.lnd5.gbb.uk.uu.net [158.43.157.13]
11 342 ms 340 ms 345 ms Internet-Solutions-gw.customer.ALTER.NET [146.188.58.162]
12 341 ms 340 ms 340 ms 168.209.247.147
13 342 ms 343 ms 340 ms 168.209.246.1
14 341 ms 339 ms 342 ms 168.209.247.147
AND
Tracing route to kalahari.mweb.co.za [196.2.33.21]
over a maximum of 30 hops:
1 17 ms 17 ms 17 ms dsl-146-64-01.telkomadsl.co.za [165.146.64.1]
2 144 ms 299 ms 267 ms rrba-ip-er-1-fe-8-0-0-1.telkom-ipnet.co.za [196.43.11.146]
3 342 ms 344 ms 342 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [196.43.9.146]
4 341 ms 345 ms 344 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
5 208.173.52.81 reports: Destination net unreachable.
Tracing route to kalahari.mweb.co.za [196.2.33.21]
over a maximum of 30 hops:
1 17 ms 17 ms 17 ms dsl-146-64-01.telkomadsl.co.za [165.146.64.1]
2 18 ms 18 ms 18 ms rrba-ip-er-1-fe-8-0-0-1.telkom-ipnet.co.za [196.43.11.146]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
According to my traces, it's just being routed internationally... not quite "Back" :/Glipsie said:Wohoo. Its back!
Yes you are correct. But at least its back. Before even the international route was down!fragtion_ said:According to my traces, it's just being routed internationally... not quite "Back" :/
this is insane. 650 total round-trip latency to a south african host (IS) from SAIX. jeez i wonder what's gone wrong. Some major peering router seems to have died and they're routing on a backup international link. Surely they should have some kind of local backup routing scheme? Jeez why must all our local bandwidth be routed overseas that makes 0% logic. Welcome to SA.Glipsie said:Yes you are correct. But at least its back. Before even the international route was down!