Ahoy
I have been expiriencing gateway timeout error pages from telkom's cache servers on random sites alot..
one example is http://www.bsdnews.org
been a week now and still cant access
traceroute is fine:
1 27 ms 27 ms 28 ms dsl-146-192-01.telkomadsl.co.za [165.146.192.1]
2 29 ms 29 ms 30 ms wblv-ip-er-1-fe-11-1-0-1.telkom-ipnet.co.za [196.43.10.138]
3 396 ms 370 ms 363 ms ny-ip-dir-globalc-pos-7-0.telkom-ipnet.co.za [196.43.9.149]
4 373 ms 366 ms 375 ms g0-2.na01.b001105-24.jfk02.atlas.cogentco.com [38.112.18.41]
5 370 ms 355 ms 360 ms g10-2-104.core01.jfk02.atlas.cogentco.com [38.112.38.169]
6 417 ms 423 ms 418 ms p12-0.core01.mci01.atlas.cogentco.com [154.54.3.202]
7 459 ms 465 ms 488 ms p10-0.core02.sfo01.atlas.cogentco.com [66.28.4.209]
8 518 ms 508 ms 540 ms isc.sfo01.atlas.cogentco.com [154.54.11.179]
9 464 ms 485 ms 493 ms r3.r2.sfo2.isc.org [192.5.4.234]
10 496 ms 502 ms 482 ms r2-sfo2.r1.sql1.isc.org [192.5.4.248]
11 453 ms 446 ms 442 ms ithildin.daemonnews.org [204.152.186.46]
I have been expiriencing gateway timeout error pages from telkom's cache servers on random sites alot..
one example is http://www.bsdnews.org
been a week now and still cant access
traceroute is fine:
1 27 ms 27 ms 28 ms dsl-146-192-01.telkomadsl.co.za [165.146.192.1]
2 29 ms 29 ms 30 ms wblv-ip-er-1-fe-11-1-0-1.telkom-ipnet.co.za [196.43.10.138]
3 396 ms 370 ms 363 ms ny-ip-dir-globalc-pos-7-0.telkom-ipnet.co.za [196.43.9.149]
4 373 ms 366 ms 375 ms g0-2.na01.b001105-24.jfk02.atlas.cogentco.com [38.112.18.41]
5 370 ms 355 ms 360 ms g10-2-104.core01.jfk02.atlas.cogentco.com [38.112.38.169]
6 417 ms 423 ms 418 ms p12-0.core01.mci01.atlas.cogentco.com [154.54.3.202]
7 459 ms 465 ms 488 ms p10-0.core02.sfo01.atlas.cogentco.com [66.28.4.209]
8 518 ms 508 ms 540 ms isc.sfo01.atlas.cogentco.com [154.54.11.179]
9 464 ms 485 ms 493 ms r3.r2.sfo2.isc.org [192.5.4.234]
10 496 ms 502 ms 482 ms r2-sfo2.r1.sql1.isc.org [192.5.4.248]
11 453 ms 446 ms 442 ms ithildin.daemonnews.org [204.152.186.46]