Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:
1 25 ms 5 ms 1 ms 192.168.10.2
2 * * * Request timed out.
3 293 ms 291 ms 289 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 * * * Request timed out.
5 300 ms 298 ms 298 ms 196.26.0.61
6 288 ms 292 ms 293 ms core2a-bry-ge1-1-0.isnet.net [168.209.100.242]
7 307 ms 329 ms 344 ms 168.209.218.22
8 309 ms 299 ms 304 ms strike.isgaming.co.za [196.38.180.25]
Trace complete.
That's to a local IS Gaming server, the first hop, represented by those *'s, is a TelkomADSL one which typically has a ~30ms ping, and the next hop over will usually add another 25ms onto that.
Various international and local sites are inaccessible, and I'm confident this is not an issue with IS/Openweb, as this issue has come up multiple times in the past few months.
For a period of roughly two weeks, recently, I got an extra 120ms added onto the hop from the TelkomADSL hop to the IS network from exactly 7am on weekdays till 5:30pm on weekdays. This behaviour was also seen at some point during 2009, during which time I had to bother MrBEEP with an endless stream of mails in order to try and figure out where the problem was. In all calls made to Telkom, they deny any and all responsibility, claiming their network is running perfectly and that the only maintenance being done anywhere would not affect the connection between my line, the exchange I'm connecting to and the handover onto the other network(s) that I tested.
Telkom are messing around with something and they're not letting anyone know what, and it's starting to !@#$ me off.