IS - SAIX peering problems again?

mystic007

Well-Known Member
Joined
Dec 1, 2003
Messages
492
Reaction score
34
Location
Sandton
Since yesterday accessing any address on SAIX from my IS/OpenWeb account results in a minimum latency of 400ms:

1 <1 ms <1 ms <1 ms ipcop.localdomain [192.168.0.1]
2 27 ms 26 ms 26 ms c1-1-1.tpr.isadsl.co.za [196.209.80.1]
3 28 ms 27 ms 29 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]
4 30 ms 32 ms 30 ms curp3-rba-gi2.isdsl.net [196.38.73.222]
5 31 ms 31 ms 31 ms 196.38.73.117
6 32 ms 31 ms 32 ms 196.26.96.203
7 34 ms 33 ms 33 ms 196.26.0.250
8 33 ms 32 ms 34 ms 168.209.86.166
9 31 ms 30 ms 28 ms 196.25.239.253
10 411 ms 414 ms 410 ms 196.43.23.221
11 409 ms 409 ms 409 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
12 415 ms 415 ms 415 ms rrba-dns2.saix.net [196.43.1.11]

Doing a tracert from SAIX to IS from my PC at work shows the traffic being routed internationally. Can anyone (MrBeep perhaps) confirm if there are any problems with the peering link between IS and SAIX?
 
Last edited:
Hey Bro,

I unfortunately cannot confirm that it is a Peering problem, but I can indeed confirm there is a problem.

Could I kindly request all OpenWeb clients that are experiencing a problem with SAIX - IS to kindly email me the following:

1. A tracert to: www.saix.co.za
2. A tracert to: www.telkom.co.za

Secondly, please include the telephone number your ADSL line is installed on.

I have launched an investigation with IS, and the more evidence we can get, the better.

Kind regards
MrBEEP

mystic007 said:
Since yesterday accessing any address on SAIX from my IS/OpenWeb account results in a minimum lactency of 400ms:

1 <1 ms <1 ms <1 ms ipcop.localdomain [192.168.0.1]
2 27 ms 26 ms 26 ms c1-1-1.tpr.isadsl.co.za [196.209.80.1]
3 28 ms 27 ms 29 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]
4 30 ms 32 ms 30 ms curp3-rba-gi2.isdsl.net [196.38.73.222]
5 31 ms 31 ms 31 ms 196.38.73.117
6 32 ms 31 ms 32 ms 196.26.96.203
7 34 ms 33 ms 33 ms 196.26.0.250
8 33 ms 32 ms 34 ms 168.209.86.166
9 31 ms 30 ms 28 ms 196.25.239.253
10 411 ms 414 ms 410 ms 196.43.23.221
11 409 ms 409 ms 409 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
12 415 ms 415 ms 415 ms rrba-dns2.saix.net [196.43.1.11]

Doing a tracert from SAIX to IS from my PC at work shows the traffic being routed internationally. Can anyone (MrBeep perhaps) confirm if there are any problems with the peering link between IS and SAIX?
 
Not Openweb, but Cheetah IS....Exact same problem, Durban-Gillitts *sigh*

Happend since Monday for me
 
Thank you to all the folks that have sent me the tracert's.

I have forwarded these on to IS, and they are currently doing an investigation. Lets hope this is sorted out today!

Kind regards
MrBEEP
 
Would this explain the terrible pings to the SGS servers for BF2? Noticed a lot of high pings around recently.. talking 500+
 
Yes. You will get the same result no matter what SAIX IP address you try. I get similar pings to the Call of Duty 2 servers. It is where I first noticed the problem. I hope they get this problem sorted soon.

schitz011 said:
Would this explain the terrible pings to the SGS servers for BF2? Noticed a lot of high pings around recently.. talking 500+
 
I am getting reports on problems from SAIX/Telkom to IS as well.
 
schitz011 said:
Would this explain the terrible pings to the SGS servers for BF2? Noticed a lot of high pings around recently.. talking 500+

Was wondering the same thing, this would also imply that this has been going on for at least a week.
 
When I did a tracert yesterday afternoon from our SAIX leased line at work to an IS IP address I saw that the traffic was routed internationally. I know that this normally happens when the local peering link between IS and SAIX is congested or down.

I remember reading on the forum last year about a dispute between IS and SAIX over the upgrading of the peering link - SAIX refusing to pay for half of the cost of the upgrade as is normally the case when two ISPs upgrade a peering link between them. Does anyone know what became of this dispute?

Moederloos said:
I am getting reports on problems from SAIX/Telkom to IS as well.
 
Last edited:
I hope they cap new users soon again. AFAIK they did not recceive the amount of peering links they wanted back in March.
 
Yes, the only good thing to come out of this is that I was forced to play commander and picked up my Staff Officer ribbon! :) Such is life..

Really hope they sort it out soon (MrBeep is on the case :) )
 
MrBeep

Any feedback from IS about the investigation yet?


MrBEEP said:
Thank you to all the folks that have sent me the tracert's.

I have forwarded these on to IS, and they are currently doing an investigation. Lets hope this is sorted out today!

Kind regards
MrBEEP
 
It just gets better !!

tracert games.saix.net

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

1 * * * Request timed out.
2 1360 ms 1535 ms 732 ms c1-1-1.rrba.isadsl.co.za [196.209.48.1]
3 * * 1909 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]
4 3204 ms 1988 ms 2795 ms curp3-rba-gi2.isdsl.net [196.38.73.222]
5 1498 ms 1109 ms 475 ms 196.38.73.117
6 1227 ms 1254 ms 953 ms 196.26.96.203
7 973 ms 1005 ms 1196 ms 196.26.0.250
8 1202 ms 1142 ms 377 ms 168.209.86.166
9 721 ms 712 ms 668 ms 196.25.239.253
10 999 ms 1387 ms 1425 ms 196.43.23.221
11 1998 ms 2037 ms 2109 ms 196.43.23.130
12 1163 ms 1498 ms 1523 ms tpr-ip-er-1-fe-1-0-0-1.telkom-ipnet.co.za [196.43.10.174]
13 1459 ms 1401 ms 2035 ms ppr-cache1-vif1.saix.net [198.54.202.66]

Trace complete.
---------------------------
tracert www.saix.net

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

1 * * * Request timed out.
2 1110 ms 1180 ms 1424 ms c1-1-1.rrba.isadsl.co.za [196.209.48.1]
3 2708 ms 2053 ms 3180 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]
4 * * 1730 ms curp3-rba-gi2.isdsl.net [196.38.73.222]
5 1443 ms 1152 ms 1527 ms 196.38.73.117
6 610 ms 907 ms 843 ms 196.26.96.203
7 1003 ms 1574 ms 1203 ms 196.26.0.250
8 774 ms 1289 ms 938 ms 168.209.86.166
9 806 ms 1287 ms 1428 ms 196.25.5.29
10 1175 ms 989 ms 1128 ms 196.43.23.221
11 581 ms 721 ms 548 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
12 931 ms 908 ms 781 ms wblv-ip-www-1.telkom-ipnet.co.za [196.25.1.200]

Trace complete.
---------------------
tracert www.telkom.co.za

Tracing route to tcen-itx-epapp.telkom.co.za [198.54.207.130]
over a maximum of 30 hops:

1 * * * Request timed out.
2 46 ms 58 ms 75 ms c1-1-1.rrba.isadsl.co.za [196.209.48.1]
3 1696 ms 1784 ms 1621 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]

4 1817 ms 1496 ms * curp3-rba-gi2.isdsl.net [196.38.73.222]
5 346 ms 405 ms 148 ms 196.38.73.117
6 312 ms 147 ms 87 ms 196.26.96.203
7 1098 ms 1073 ms 604 ms 196.26.0.250
8 84 ms 137 ms 209 ms 168.209.86.166
9 448 ms 58 ms 115 ms 196.25.239.253
10 436 ms 451 ms 606 ms 196.43.23.221
11 514 ms 472 ms 462 ms rndf-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.10.158]
12 * * * Request timed out.
13 telkom-tienet-gw.telkom-ipnet.co.za [196.25.2.138] reports: Destination ne
t unreachable.

Trace complete.
 
Got the following e-mail from OpenWeb this morning:

URGENT Notice: SAIX fault causing high IS pings

Dear Friends,

SAIX has done it again. They have a major fault on their link that is affecting many IS, and SAIX users alike. All clients that play on the SGS servers will experience unusually high pings of up to 500+.

SAIX deny that there is a problem, however IS are currently trying to work with the to resolve.

I apologise for any inconvenience caused.

We hope this problem is resolved asap.
 
I do love the part in that letter where it is mentioned that SAIX denies any problems ...
Heck you show them the proof, you can see the proof, they can even test the system themselves and the responce ... "No, No, No ... all is well, it is just your imagination, a ping of 100000 is normal "

Bah !
 
Legal action

Is there no possible way to take legal action?
Because surely this is affecting ppl who have bought local accounts from IS?

:mad:
 
Well I see the latency of my IS account is still not back to normal and is still between 500-800ms.

I wonder when this problem is going to be fixed?
This has been going on for 2 weeks now and it still persists!!!

My is account is now useless for local gaming :mad:

I just wish we actually knew what is going on.
Commin IS why is it taking so long to fix this?
 
Yes, I'd also like to know why it is taking so long for IS to resolve this issue.
From what I understand from MrBeeps communications it is a joint issue between Saix and IS.

I am getting very annoyed with the whole situation and feel that unless it is resloved soon I may very well go round to IS's head office and key some cars.

Come on IS and Saix, sort your issues out! We pay good money for this service and to have these sorts of pings on LOCAL gaming sites is unacceptable. Actually to have these sorts of pings to any local site is unacceptable.

Sort your service out!
 
Hey Friends,

This indeed has now become a major problem, and I myself am extremely upset at the amount of time it has taken to resolve.

I am on the phone daily to IS, trying to get this issued repaired ASAP.

I would once again like to apologise for the inconvenience, and WILL keep everyone updated.

Kind regards
MrBEEP
 
Top
Sign up to the MyBroadband newsletter
X