LATENCY!!!

Anybody else on Clareinch getting horrendous 3rd hop latency today (midday Mon 8th)?

I'm getting 350ms 3rd hop, and 650ms to mybroadband.co.za. Totally unusable...
 
Gordon_R said:
Anybody else on Clareinch getting horrendous 3rd hop latency today (midday Mon 8th)?

I'm getting 350ms 3rd hop, and 650ms to mybroadband.co.za. Totally unusable...
Click to expand...
nope
traceroute to mybroadband.co.za (41.203.21.137), 64 hops max, 40 byte packets
1 10.0.0.2 (10.0.0.2) 1.753 ms 1.114 ms 2.857 ms
2 dsl-242-172-01.telkomadsl.co.za (41.242.172.1) 7.430 ms 8.024 ms 7.229 ms
3 196.43.11.218 (196.43.11.218) 8.415 ms 7.624 ms 8.459 ms
4 196.43.25.206 (196.43.25.206) 7.821 ms 8.276 ms 7.722 ms
5 ge0-3.br2.cpt1.za.mtnbusiness.net (196.7.8.206) 9.606 ms 8.870 ms 9.120 ms
6 196.30.1.21 (196.30.1.21) 42.982 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 37.341 ms 196.30.1.21 (196.30.1.21) 38.059 ms
7 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 39.037 ms 37.362 ms 37.324 ms
8 196.30.213.108 (196.30.213.108) 38.232 ms 37.582 ms 38.412 ms
9 firewall1.jnb2.host-h.net (196.7.216.173) 37.037 ms 38.474 ms 37.971 ms
10 mybroadband.co.za (41.203.21.137) 43.117 ms 44.500 ms 43.186 ms
 
_Jack_ said:
nope
traceroute to mybroadband.co.za (41.203.21.137), 64 hops max, 40 byte packets
1 10.0.0.2 (10.0.0.2) 1.753 ms 1.114 ms 2.857 ms
2 dsl-242-172-01.telkomadsl.co.za (41.242.172.1) 7.430 ms 8.024 ms 7.229 ms
3 196.43.11.218 (196.43.11.218) 8.415 ms 7.624 ms 8.459 ms
Click to expand...

Thanks, but I think you're on a totally different DSLAM/ESR/route.

Code: 
Tracing route to tenet.cinx.net.za [198.32.214.33]
over a maximum of 30 hops:

   1   <10 ms   <10 ms     1 ms  home.gateway [192.168.1.254]
   2     6 ms     7 ms     6 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3   366 ms   362 ms   367 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
   4   317 ms   318 ms   321 ms  196-28-178-133.adsl.mweb.co.za [196.28.178.133]
   5   319 ms   328 ms   343 ms  tenet.cinx.net.za [198.32.214.33]

Trace complete.

Edit: I sincerely hoped I wouldn't have to run PingPlotter again, but this isn't funny...

http://www.imagehost.co.za/image-2F64_4CD7D39D.gif
 
Last edited:
I'm on a rondebosch exchange and using mweb and my pings are above 300ms too.

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

1 7 ms 6 ms 6 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
2 290 ms 295 ms 302 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
3 317 ms 338 ms 306 ms 196.41.144.36
4 312 ms 308 ms 314 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
peTerp00n said:
I'm on a rondebosch exchange and using mweb and my pings are above 300ms too.

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

1 7 ms 6 ms 6 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
2 290 ms 295 ms 302 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
Trace complete.
Click to expand...

Thanks! Different DSLAM, same 2nd/3rd hop/ESR.

FFS, how long is it going to last this time???
 
you guys sure the issue has returned?

Gordon im on the clareinch 8 exchange at home so cant quite test there just yet, but its been fine lately.
At work right now and seems fine, also on the clareinch exchange, we are in the Villagers rugby grounds area. Stats to follow:

Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=30ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=32ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=30ms TTL=249
Reply from 196.43.22.222: bytes=32 time=30ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=32ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=32ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249
Reply from 196.43.22.222: bytes=32 time=31ms TTL=249

Ping statistics for 196.43.22.222:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 32ms, Average = 31ms


Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 6 ms 6 ms 6 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
3 26 ms 26 ms 26 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
4 27 ms 27 ms 26 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
5 31 ms 31 ms 29 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
6 31 ms 38 ms 31 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
Surv0 said:
you guys sure the issue has returned?

Gordon im on the clareinch 8 exchange at home so cant quite test there just yet, but its been fine lately.
At work right now and seems fine, also on the clareinch exchange, we are in the Villagers rugby grounds area. Stats to follow:
Click to expand...

It may just be one or two DSLAMs, but mine is definitely f****d. Two other users agree (so far).

I PMd Will@MWeb. It would be interesting to hear what he has to say!

P.S. I will be out for the next 2 hours (but will keep PingPlotter running...)
 
my two tests to cinx seemed to fall over:

Tracing route to tenet.cinx.net.za [198.32.214.33]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 5 ms 5 ms 5 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 27 ms 26 ms 196.43.10.130
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Ian>tracert tenet.cinx.net.za

Tracing route to tenet.cinx.net.za [198.32.214.33]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 6 ms 6 ms 5 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 5 ms 7 ms 5 ms 196.43.33.65
4 14 ms 6 ms 6 ms 196.43.33.65
5 33 ms 30 ms 37 ms 196.43.10.130
6 196.43.33.5 reports: Destination host unreachable.

Trace complete.
 
Surv0 said:
my two tests to cinx seemed to fall over:

Tracing route to tenet.cinx.net.za [198.32.214.33]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 5 ms 5 ms 5 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 27 ms 27 ms 26 ms 196.43.10.130
Click to expand...

If you are a SAIX customer then tracert to tenet.cinx.net.za may not be very relevant (particularly if peering routes have changed). In any case if you don't have a latency problem, then your posts won't help those of us who do have a problem...

Edit: PingPlotter indicates that my latency abruptly returned to normal at 13h45. No transition period, just a sharp dropoff. Weird...

Edit #2: PingPlotter indicates that latency increased sharply to 200ms at 13h48 (was 300ms for over an hour). Looks like someone is randomly unplugging wires....

http://www.imagehost.co.za/image-EFA9_4CD7E479.gif
 
Last edited:
Gordon_R said:
If you are a SAIX customer then tracert to tenet.cinx.net.za may not be very relevant (particularly if peering routes have changed). In any case if you don't have a latency problem, then your posts won't help those of us who do have a problem...

Edit: PingPlotter indicates that my latency abruptly returned to normal at 13h45. No transition period, just a sharp dropoff. Weird...

Edit #2: PingPlotter indicates that latency increased sharply to 200ms at 13h48 (was 300ms for over an hour). Looks like someone is randomly unplugging wires....

http://www.imagehost.co.za/image-EFA9_4CD7E479.gif
Click to expand...

we could be on a saix based account which would explain the above.

and i was only trying to help you reduce possibilities by informing that the latency issue isnt global in the same area. ill refrain from contributing if im not experiencing a problem in the future. You can do the guess work...
 
peTerp00n,

IS and MWEB still peer with each other and as far as I've read around the place, it should stay in place for a while still.
I believe its because some MWEB customers are still on the IS network.
 
My web is not usable at all today.

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

1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 7 ms 7 ms 7 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 658 ms 658 ms 658 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 636 ms 631 ms 634 ms 196.41.144.36
5 173 ms 180 ms 189 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Hi guys

Apologies for the delayed post. We are running at reduced capacity in Cape Town today as one of our IPC links is down. This is the most likely cause of the current latency you're seeing.

Kind Regards
Will
 
Pinging saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=906ms TTL=239
Reply from 196.25.1.200: bytes=32 time=885ms TTL=239
Reply from 196.25.1.200: bytes=32 time=1010ms TTL=239
Reply from 196.25.1.200: bytes=32 time=1015ms TTL=239


Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=821ms TTL=51
Reply from 41.203.21.137: bytes=32 time=838ms TTL=51
Reply from 41.203.21.137: bytes=32 time=759ms TTL=51
Reply from 41.203.21.137: bytes=32 time=747ms TTL=51


Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=406ms TTL=122
Reply from 196.2.63.110: bytes=32 time=670ms TTL=122
Reply from 196.2.63.110: bytes=32 time=397ms TTL=122
Reply from 196.2.63.110: bytes=32 time=446ms TTL=122


Terrible in Cape Town as you can see, close to unusable. Any ETA on how long this will take to fix.. I would consider it critical.
 
Last edited:
Will@MWEB said:
Hi guys

Apologies for the delayed post. We are running at reduced capacity in Cape Town today as one of our IPC links is down. This is the most likely cause of the current latency you're seeing.

Kind Regards
Will
Click to expand...

Ok well good to know! But can you say when it is going to be fixed!???
 
Surv0 said:
we could be on a saix based account which would explain the above.

and i was only trying to help you reduce possibilities by informing that the latency issue isnt global in the same area. ill refrain from contributing if im not experiencing a problem in the future. You can do the guess work...
Click to expand...

Sorry, I was a bit grouchy earlier. I didn't mean that your post wasn't useful, but that all those pings didn't provide any more information than 'mine is OK on SAIX'.

Will: Thanks for the feedback, but that's seriously bad congestion! Presumably the Cape Town IPC can't 'shape' traffic priority separately from MWeb's Jhb based P2P load-balancing?

I'm getting some weird spikes and dips in the chart, but almost all of the latency is way outside of usable limits.

http://www.imagehost.co.za/image-A78B_4CD81EAE.gif

Alestorm said:
Pinging saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=906ms TTL=239

<<snip>>

Terrible in Cape Town as you can see, close to unusable. Any ETA on how long this will take to fix.. I would consider it critical.
Click to expand...

The first 2 ping destinations include routing via London, which does not help(!), but the basic problem is the hop2/3 stage.

Edit: The MWeb Nework Notices status page doesn't indicate anything:
http://www.mweb.co.za/helpcentre/NetworkStatusNotices/tabid/1765/Default.aspx
Does this mean that losing half your IPC capacity in CT doesn't count as a significant event??
 
Last edited:
i can confirm that my ping is still ****ed on mweb, but its completely fine on webafrica.

Will@MWEB said:
Hi guys

Apologies for the delayed post. We are running at reduced capacity in Cape Town today as one of our IPC links is down. This is the most likely cause of the current latency you're seeing.

Kind Regards
Will
Click to expand...


see this is what i HATE about mweb...

1) a lot more issues and performance related problems - much more than all the "normal" ISPs
2) a lack of information regarding said issues and poor performance. we only know because will made a post about it, but mweb should have sent a mail to EVERYONE affected about this.

paying for a service and getting less than what you pay for is terrible. getting less than what you pay for, but a full explaination and as much detail as possible is forgivable. i see loads of people posting on facebook that they have issues and the response is always "pm me your account details and we will look into it". that just pisses me off. take responsibility for your ****ups. keep your clients informed if you cant keep them satisfied. we would appreciate that.
 
http://www.mweb.co.za/helpcentre/NetworkStatusNotices.aspx

Why is there nothing on this page about it?

I mean, it's a pretty large failure, I am betting quite a large portion of your userbase doesn't know about MyBB or the Facebook page, whereas the direct link on the website which is intended for the purpose of communicating failures on a mass scale would be the first place most people would look (besides the ones who phone and have to wait on hold).

Once again, appreciate the communication here but that MWEB page is a potentially useful mouth piece. Use it!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X