UUNET out of bandwidth ?

While generally satisfied with iBurst service I have of late seen a dramatic increase in latency to Telkom/Saix sites via iBurst.

By tracing the route packets take we see a rather SAD state of affairs:

traceroute www.telkom.co.za
1 wbs-196-2-120-1.wbs.co.za (196.2.120.1) 53 ms 63 ms 43 ms
2 192.168.0.97 (192.168.0.97) 77 ms ge0-2.gw10.jnb6.alter.net (66.8.42.21) 60 ms 192.168.0.97 (192.168.0.97) 43 ms
3 ge0-2.gw10.jnb6.alter.net (66.8.42.21) 48 ms 46 ms 43 ms
4 ge0-0.br1.jnb6.alter.net (196.30.156.41) 46 ms 46 ms 65 ms
5 other-side.atm6-0sub1.br1.jnb6.alter.net (196.31.39.53) 299 ms 286 ms 302 ms
6 rndf-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za (196.43.10.158) 378 ms 345 ms 290 ms
7 telkom-tienet-gw.telkom-ipnet.co.za (196.25.2.138) 360 ms 268 ms 271 ms

So, either their is a problem with the UUNET atm interface or it's simply congested ...

Anyone else seeing this !!??!!

Something at iBurst(or other places) is screwed!

traceroute www.telkom.co.za
traceroute to tcen-itx-epapp.telkom.co.za (198.54.207.130), 30 hops max, 38 byte
packets
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
1 WRT54G (172.16.14.2) 1.167 ms 0.823 ms 1.254 ms
2 wbs-196-2-120-1.wbs.co.za (196.2.120.1) 189.813 ms 45.390 ms 46.416 ms
3 192.168.0.97 (192.168.0.97) 44.819 ms ge0-2.gw10.jnb6.alter.net (66.8.42.21 ) 60.324 ms 102.483 ms
4 ge0-2.gw10.jnb6.alter.net (66.8.42.21) 85.812 ms 119.169 ms 39.919 ms
5 ge0-0.br1.jnb6.alter.net (196.30.156.41) 40.001 ms 45.257 ms 44.824 ms
6 other-side.atm6-0sub1.br1.jnb6.alter.net (196.31.39.53) 565.113 ms 295.102 ms 364.804 ms
7 rndf-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za (196.43.10.158) 251.023 ms 255.7 78 ms 299.343 ms
8 telkom-tienet-gw.telkom-ipnet.co.za (196.25.2.138) 339.911 ms 284.760 ms 425.020 ms
9 *Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
* *
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
10 *Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong
Icmp checksum is wrong


--- www.l.google.com ping statistics ---
34 packets transmitted, 22 received, 35% packet loss, time 32998ms
rtt min/avg/max/mdev = 374.400/448.521/686.298/62.781 ms, pipe 2

Related thread started by Clipse today:
http://www.mybroadband.co.za/vb/showthread.php?t=40247

Seems SAIX is experencing severe peering problems with IS and UUNET. The link between "other-side.atm6-0sub1.br1.jnb6.alter.net" and "telkom-ipnet.co.za" looks overloaded.

RegardTV:
5 other-side.atm6-0sub1.br1.jnb6.alter.net (196.31.39.53) 299 ms 286 ms 302 ms
6 rndf-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za (196.43.10.158) 378 ms 345 ms 290 ms
7 telkom-tienet-gw.telkom-ipnet.co.za (196.25.2.138) 360 ms 268 ms 271 ms

Clipse:
6. other-side.atm6-0sub1.br1.jnb6.alter.net 0.0% 4 253.9 243.5 234.7 253.9 8.0
7. wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za 0.0% 4 268.2 285.3 268.1 319.5 29.6
8. wblv-ip-www-1.telkom-ipnet.co.za 33.3% 3 267.6 264.8 262.0 267.6 4.0

Just called WBS they checking this now

Steam (SGS Servers = Sucky Ping)

Gr....

Its getting better: (But it spikes now and then like below)

ping -t saix.net

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=88ms TTL=246
Reply from 196.25.1.200: bytes=32 time=63ms TTL=246
Reply from 196.25.1.200: bytes=32 time=72ms TTL=246
Reply from 196.25.1.200: bytes=32 time=91ms TTL=246
Reply from 196.25.1.200: bytes=32 time=71ms TTL=246
Reply from 196.25.1.200: bytes=32 time=316ms TTL=246
Reply from 196.25.1.200: bytes=32 time=223ms TTL=246
Reply from 196.25.1.200: bytes=32 time=105ms TTL=246
Reply from 196.25.1.200: bytes=32 time=124ms TTL=246
Reply from 196.25.1.200: bytes=32 time=57ms TTL=246
Reply from 196.25.1.200: bytes=32 time=69ms TTL=246
Reply from 196.25.1.200: bytes=32 time=91ms TTL=246

To iburst.co.za its excellent, since this Honeydew tower

ping -t www.iburst.co.za

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=84ms TTL=124
Reply from 196.30.31.120: bytes=32 time=55ms TTL=124
Reply from 196.30.31.120: bytes=32 time=54ms TTL=124
Reply from 196.30.31.120: bytes=32 time=60ms TTL=124
Reply from 196.30.31.120: bytes=32 time=57ms TTL=124
Reply from 196.30.31.120: bytes=32 time=59ms TTL=124
Reply from 196.30.31.120: bytes=32 time=64ms TTL=124
Reply from 196.30.31.120: bytes=32 time=40ms TTL=124
Reply from 196.30.31.120: bytes=32 time=60ms TTL=124
Reply from 196.30.31.120: bytes=32 time=55ms TTL=124
Reply from 196.30.31.120: bytes=32 time=54ms TTL=124
Reply from 196.30.31.120: bytes=32 time=64ms TTL=124
Reply from 196.30.31.120: bytes=32 time=63ms TTL=124

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=36ms TTL=242
Reply from 196.25.1.200: bytes=32 time=35ms TTL=242
Reply from 196.25.1.200: bytes=32 time=34ms TTL=242
Reply from 196.25.1.200: bytes=32 time=35ms TTL=242

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 36ms, Average = 35ms

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=15ms TTL=116
Reply from 196.30.31.120: bytes=32 time=18ms TTL=116
Reply from 196.30.31.120: bytes=32 time=17ms TTL=116
Reply from 196.30.31.120: bytes=32 time=16ms TTL=116

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 18ms, Average = 16ms

Sorry I couldn't help myself....

That was completely uncalled for

It's failing again avg. 250ms ping..