Does someone know something, I dont?

[Clipse]

Im just curious with UUNET atm, great its uncapped and browsing works great but the latency's.. What are they doing, does anyone know if they still having problems and working on it?

This morning they reinstall IOS(afaik) and just after the 2hrs outtage, pings was back to normal. Then I wake up and check, its all back to screwed up.. 200+ ms to closes hop.

Anyone know what is going on?

 

[Clipse]

hmmm strange things happening.

Saix ADSL Connecting ::

C:\Documents and Settings\Clipse>ping saix.net

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

Reply from 196.25.1.200: bytes=32 time=18ms TTL=251
Reply from 196.25.1.200: bytes=32 time=19ms TTL=251
Reply from 196.25.1.200: bytes=32 time=19ms TTL=251
Reply from 196.25.1.200: bytes=32 time=19ms TTL=251

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

C:\Documents and Settings\Clipse>ping is.co.za

Pinging is.co.za [196.4.160.2] with 32 bytes of data:

Reply from 196.4.160.2: bytes=32 time=154ms TTL=249
Reply from 196.4.160.2: bytes=32 time=156ms TTL=249
Reply from 196.4.160.2: bytes=32 time=157ms TTL=249
Reply from 196.4.160.2: bytes=32 time=162ms TTL=249

Ping statistics for 196.4.160.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 162ms, Average = 157ms

C:\Documents and Settings\Clipse>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=189ms TTL=109
Reply from 196.2.63.110: bytes=32 time=183ms TTL=109
Reply from 196.2.63.110: bytes=32 time=180ms TTL=109
Reply from 196.2.63.110: bytes=32 time=182ms TTL=109

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 189ms, Average = 183ms


Similar results with uunet, low ping to uunet self but external local peers high ping.


South-Africa WTF is going on? Telkom did you put SA ADSL on the 56k BACKBONE!

 

[mancombseepgood]

Probably

making the "competition" look bad to increase sales.

 

[Clipse]

thing is, its happening both ways.. We have a seriously screwed up peering link somewhere that both uunet and saix use.

 

[Clipse]

Hmm some basic testing.


1.) Saix to outside network traceroute:

Tracing route to karoo.mweb.co.za [196.2.128.100]
over a maximum of 30 hops:

1 22 ms 17 ms 17 ms wblv-146-192-01.telkomadsl.co.za [165.146.192.1]
2 17 ms 17 ms 17 ms wblv-ip-er-1-fe-11-1-1-1.telkom-ipnet.co.za [196
.43.11.214]
3 40 ms 40 ms 39 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
4 229 ms 158 ms 211 ms 196.25.5.30
5 190 ms 153 ms 160 ms 168.209.86.165
6 153 ms 179 ms 186 ms core1a-rba-gi2-0-0.rtr.isnet.net [196.26.0.7]
7 218 ms 193 ms 177 ms 168.209.100.74
8 180 ms 213 ms 203 ms 168.209.0.190
9 181 ms 189 ms 194 ms 196.23.49.102
10 189 ms 179 ms 182 ms net-128-81.mweb.co.za [196.2.128.81]
11 184 ms 182 ms 181 ms toreador.mweb.co.za [196.2.128.100]

Trace complete.


2.) UUNET to outside network traceroute:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 186 ms 186 ms 180 ms 196.7.196.21
3 191 ms 193 ms 192 ms pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
4 181 ms 193 ms * ge0-0.br1.jnb6.alter.net [196.30.156.41]
5 * 191 ms 192 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31
.39.53]
6 205 ms 214 ms 212 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
7 215 ms 217 ms 215 ms wblv-ip-www-1.telkom-ipnet.co.za [196.25.1.200]


Trace complete.

 

[Clipse]

Seems to me, whatever is wrong.. Its saix related and uunet might be on same line thats why its also affected.

Network Faults latest
Call Reference ID : STT000000003985
Failure Type : Network Failure
Problem Description : Rosebank
Time Down : 26 Apr 2005, 13:30:00
Impact : Clients will experience slow responses to International Sites
Site : Rosebank
Services Affected : International
Cause of Failure : N/A
Status : New

 

[killadoob]

o just blame telkom couldnt be uunet's fault always saix

how do you know its saix related?

i thought uunet didnt use saix (might be a stupid comment)

 

[Clipse]

Anyone in ISADSL that could ping the dns/ip mentioned, plz post.

 

[Clipse]

If you read, SAIX NOTICEBOARD shows they have international peer down... So from that I figure that since SAIX do have a noticeboard post and uunet dont.. It is from SAIX side.

Do the maths please