Clareinch (Claremont Exchange) Congested

[jeanres]

Anyone else having some serious connectivity issues?

 

[Anthro]

Had a regional manager and ops manager with a few techies in my CT offices this morning - they are working on the exchange to resolve my issues.. lets see

 

[sybawoods]

Anyone else having some serious connectivity issues?

Things went to hell for me for about 10mins early yesterday evening (high pings and packet loss). I powered down my modem for 10mins and everything was fine again. I'm putting it down to a tiny glitch in the matrix - connectivity has pretty much been perfect since Wed / Thur last week.

 

[jeanres]

Things went to hell for me for about 10mins early yesterday evening (high pings and packet loss). I powered down my modem for 10mins and everything was fine again. I'm putting it down to a tiny glitch in the matrix - connectivity has pretty much been perfect since Wed / Thur last week.

I can't even open FNB's site

 

[jeanres]

traceroute: Warning: google.com has multiple addresses; using 74.125.233.39
traceroute to google.com (74.125.233.39), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.216 ms 0.941 ms 0.801 ms
2 * * *
3 196.41.29.165 (196.41.29.165) 10.119 ms 7.556 ms 6.860 ms
4 196.41.29.166 (196.41.29.166) 7.747 ms 7.045 ms 6.981 ms
5 196.41.29.233 (196.41.29.233) 7.976 ms 8.710 ms 8.132 ms
6 41.193.119.6 (41.193.119.6) 477.662 ms 738.749 ms 614.351 ms

 

[zolly]

traceroute: Warning: google.com has multiple addresses; using 74.125.233.39
traceroute to google.com (74.125.233.39), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.216 ms 0.941 ms 0.801 ms
2 * * *
3 196.41.29.165 (196.41.29.165) 10.119 ms 7.556 ms 6.860 ms
4 196.41.29.166 (196.41.29.166) 7.747 ms 7.045 ms 6.981 ms
5 196.41.29.233 (196.41.29.233) 7.976 ms 8.710 ms 8.132 ms
6 41.193.119.6 (41.193.119.6) 477.662 ms 738.749 ms 614.351 ms

Ping to the 74.125.233.39 sitting about 52 ms, but I was getting 50% packet loss to that IP. Games however are running fine.

Maybe something wrong with your ISP?

 

[jeanres]

Ping to the 74.125.233.39 sitting about 52 ms, but I was getting 50% packet loss to that IP. Games however are running fine.

Maybe something wrong with your ISP?

~ ❯ ping 74.125.233.39
PING 74.125.233.39 (74.125.233.39): 56 data bytes
64 bytes from 74.125.233.39: icmp_seq=0 ttl=53 time=326.190 ms
64 bytes from 74.125.233.39: icmp_seq=1 ttl=53 time=252.645 ms
64 bytes from 74.125.233.39: icmp_seq=2 ttl=53 time=466.160 ms
64 bytes from 74.125.233.39: icmp_seq=3 ttl=53 time=521.655 ms
Request timeout for icmp_seq 4
64 bytes from 74.125.233.39: icmp_seq=5 ttl=53 time=290.900 ms
64 bytes from 74.125.233.39: icmp_seq=6 ttl=53 time=327.956 ms
64 bytes from 74.125.233.39: icmp_seq=7 ttl=53 time=320.048 ms

 

[zolly]

~ ❯ ping 74.125.233.39
PING 74.125.233.39 (74.125.233.39): 56 data bytes
64 bytes from 74.125.233.39: icmp_seq=0 ttl=53 time=326.190 ms
64 bytes from 74.125.233.39: icmp_seq=1 ttl=53 time=252.645 ms
64 bytes from 74.125.233.39: icmp_seq=2 ttl=53 time=466.160 ms
64 bytes from 74.125.233.39: icmp_seq=3 ttl=53 time=521.655 ms
Request timeout for icmp_seq 4
64 bytes from 74.125.233.39: icmp_seq=5 ttl=53 time=290.900 ms
64 bytes from 74.125.233.39: icmp_seq=6 ttl=53 time=327.956 ms
64 bytes from 74.125.233.39: icmp_seq=7 ttl=53 time=320.048 ms

I'm assuming you've tried another ISP?

Also, it may be necessary to force a reset on your current connection. To do that you have to turn off you're router for 30 minutes. Easiest way to confirm that your connection has been reset is if you have a different IP after you've left your router off for a while.

 

[jeanres]

I'm assuming you've tried another ISP?

Also, it may be necessary to force a reset on your current connection. To do that you have to turn off you're router for 30 minutes. Easiest way to confirm that your connection has been reset is if you have a different IP after you've left your router off for a while.

Works on another ISP, but why do I still have hope 2 timing out on a trace route?

 

[zolly]

Works on another ISP, but why do I still have hope 2 timing out on a trace route?

Ok. Well, if it's timing out on all your ISPs, I guess there's some kind of problem (what kind I don't know). I would still do the router reset and leave it off for a while so that the exchange kills all the connections you currently have active (a friend of mine who does network engineering actually explained to me that exchanges are design to keep your connection active so that if there's small blips that cause you to drop you will reconnect as fast as possible, the only way to get around this is to power down for at least 30 minutes).

If the problem still occurs, call Telkom and ask them to do a port reset.

If the problem still occurs, it's something that Telkom will need to look at.

Oh yeah, I'm guessing this problem occurs all the time right? Not just in the evenings or mornings or whatever?

 

[jeanres]

I think my card in the dslam is fuuucked

 

[image132]

And things have gotten worse again. Sigh

 

[ajan]

Pinging www.mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=35ms TTL=51
Reply from 197.242.89.170: bytes=32 time=29ms TTL=51
Reply from 197.242.89.170: bytes=32 time=29ms TTL=51
Reply from 197.242.89.170: bytes=32 time=29ms TTL=51

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

Every thing is fine for me

 

[image132]

It's only 9 on a friday (night when everyone goes out) and I've hit ~60

Pinging mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=60ms TTL=49
Reply from 197.242.89.170: bytes=32 time=57ms TTL=49
Reply from 197.242.89.170: bytes=32 time=56ms TTL=49
Reply from 197.242.89.170: bytes=32 time=60ms TTL=49

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

 

[ajan]

first MSAN units in Claremont going live end of October

From Charls himself.

Currently, I'm inbetween the fiber roll out in Bishopscourt and the VDSL rollout in Claremont. So unlucky.

 

[zolly]

first MSAN units in Claremont going live end of October

From Charls himself.

Currently, I'm inbetween the fiber roll out in Bishopscourt and the VDSL rollout in Claremont. So unlucky.

Bummer. I'm not really interested in VDSL unless I can get at least 2-3 meg upload speeds on the line. Hell, I would run a 10 meg account on the line if I could just get the upload speed boost.

 

[image132]

Agreed. The upload speed cap from telkom is quite severe :/

Could someone please ask Charl if everyone automatically gets connected to the MSAN or if only the people who get VDSL get connected to it and the rest of us get stuck on the old DSLAM.

 

[ajan]

Everyone that is 2.7km or less away will most likely get connected. Anything after 2.7km will not make a difference.

Charl, said I'm more likely to get fiber than VDSL. Any way time to wait.

 

[image132]

Everyone that is 2.7km or less away will most likely get connected. Anything after 2.7km will not make a difference.

Charl, said I'm more likely to get fiber than VDSL. Any way time to wait.

Ah. I didn't know it was a distance only situation. I just want the stability that comes with being connected to a MSAN, VDSL is kind of a secondary thing.

Also if you get fiber you're going to have like 2ms to CSGO servers. I'll be jelly

 

[ajan]

Still mixed feelings about the MSAN situation. Stability yes, but remember everyone will most probably want a higher speed now. And you know what that means.