Sloooow

Well, I did another tracert and this is what I started getting :

2 41 ms 43 ms 42 ms dsl-241-224-01.telkomadsl.co.za [41.241.224.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 47 ms 43 ms 44 ms 196.43.33.2
6 42 ms 41 ms 43 ms 196.43.33.5
7 205 ms 203 ms 203 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
8 * 364 ms * rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
9 523 ms 524 ms 524 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
10 684 ms 685 ms * rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
11 844 ms 843 ms 844 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
12 1003 ms 1004 ms 1004 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
13 * 1167 ms 1164 ms rrba-ip-lir-1-pos-6-1.telkom-ipnet.co.za [196.43.9.145]
14 ^C
Seems to me that that's where the break lies.

Edit : the noticeboard just added this :
etwork Faults latest
Call Reference ID : STT000000006751
Failure Type : Network Failure
Problem Description : line down from Barrack Street Core to Bellville ESr 4
Time Down : 31 Jan 2008, 13:20:00
Impact : Customers will experience slow connectivity
Site : Barrack Street Core
Services Affected : all customers
Updates :

31 Jan 2008, 21:18:59 kereterp
Techs busy attending

Cause of Failure : Unknown
Status : New
 
Last edited:
That's weird, I read about the cable break this morning and never experienced any problems, these problems only affected me this afternoon.
 
Last edited:
That's because it wasn't the cable break.

From what I can tell, one of SAIX's major routers decided that forwarding packets to itself was the fastest way to get rid of them.
 
That's because it wasn't the cable break.

From what I can tell, one of SAIX's major routers decided that forwarding packets to itself was the fastest way to get rid of them.

That explains why the net is working again (for me now anyway) so the cable break does not affect us then.
 
Top
Sign up to the MyBroadband newsletter
X