Clareinch (Claremont Exchange) Congested

[ichigo]

Well it's been ages since it's been this good (touch wood) so we'll see if they've fixed it or not.

I hope it is being fixed for you guys

Gone for a ball of **** now

How bad now?

 

[jeanres]

traceroute: Warning: www.google.com has multiple addresses; using 74.125.233.82
traceroute to www.google.com (74.125.233.82), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.919 ms 0.888 ms 0.829 ms
2 dsl-197-245-24-1.voxdsl.co.za (197.245.24.1) 119.954 ms 118.645 ms 125.046 ms
3 196.41.29.166 (196.41.29.166) 147.546 ms 134.714 ms 134.733 ms
4 196.41.29.233 (196.41.29.233) 132.353 ms 153.710 ms 137.297 ms

 

[image132]

Yep I've hit 140 now. 10PM is peak time.

07 August 2014 10:02PM

Tracing route to google.co.za [74.125.230.87]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 135 ms 133 ms 132 ms 105-236-6-1-esr-lo.mtnbusiness.co.za [105.236.6.1]
3 130 ms 133 ms 133 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 133 ms 132 ms 136 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 142 ms 176 ms 149 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 266 ms 290 ms 275 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 309 ms 282 ms 279 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
8 282 ms 280 ms 281 ms rb-ad-1--glgix-bloemf-1-a.mtnns.net [209.212.99.13]
9 * 293 ms 290 ms 209.85.255.76
10 280 ms 265 ms 266 ms 72.14.238.21
11 289 ms 291 ms 288 ms lhr14s23-in-f23.1e100.net [74.125.230.87]

Trace complete.

Still congested. The balancing didn't work :/

 

[jeanres]

Anyone else just have a internet disconnect?

 

[zll]

Not at home and don't have a remote connection set up so can't confirm. Are you still offline on your ADSL?

 

[Anthro]

I am in process of contacting regional managers to get this resolved.

Telkom needs to come to the party asap with this

 

[zll]

Anyone else just have a internet disconnect?

My internet has been up for 22 hours so no looks like my line was online. However, I don't remember my line disconnecting yesterday evening -_-

 

[jeanres]

I am in process of contacting regional managers to get this resolved.

Telkom needs to come to the party asap with this

Let me know how I can help

 

[zll]

8.10 and speeds are actually reasonable for a change. I guess Telkom is doing something to try and sort this out, even if it's just some kind of better load balancing.

 

[jeanres]

Warning: google.com has multiple addresses; using 74.125.233.73
traceroute to google.com (74.125.233.73) , 5 relative hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 5.516 ms 16.881 ms 25.024 ms
2 dsl-197-245-24-1.voxdsl.co.za (197.245.24.1) 84.091 ms 812.547 ms 815.328 ms
3 196.41.29.166 (196.41.29.166) 82.914 ms 724.322 ms 727.352 ms

 

[zll]

I can confirm that performance over the weekend was better. Pings would be fine till about 8 PM and then peak between 9 and 10 PM. Speeds would return to normal not too long after 11 PM. I guess Telkom has done some kind of load balancing or moved people around to distribute the bandwidth usage.

 

[Anthro]

Let me know how I can help

Thanks for the willingness,
We have an "account manager" who is getting commission from all the monthly Telkom "subscriptions" we get.

Threatening his salary and bonus seems to have the desired effect when it comes to escalating problems.
Will keep you in the loop as well ^

 

[jeanres]

Thanks for the willingness,
We have an "account manager" who is getting commission from all the monthly Telkom "subscriptions" we get.

Threatening his salary and bonus seems to have the desired effect when it comes to escalating problems.
Will keep you in the loop as well ^

Legend!

 

[jeanres]

Its completely ****ed tonight.

 

[ajan]

Pinging www.mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=113ms TTL=51
Reply from 197.242.89.170: bytes=32 time=102ms TTL=51
Reply from 197.242.89.170: bytes=32 time=94ms TTL=51
Reply from 197.242.89.170: bytes=32 time=103ms 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 = 94ms, Maximum = 113ms, Average = 103ms

Moved in this weekend, nothing has gone correctly with Telkom so far. Guess no need to complain as I'm sure Telkom is working their hardest on fixing this problem :erm:

 

[ChrisJ]

I'm going to see what our corporate account manager has to say. Mine hasn't been too bad a past few nights but trying to work tonight is a nightmare.

Tracing route to mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms home.home [10.9.8.2]
2 125 ms 128 ms 128 ms 105-236-6-1-esr-lo.mtnbusiness.co.za [105.236.6.1]
3 254 ms 134 ms 136 ms 41.181.51.182
4 258 ms 205 ms 147 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 170 ms 204 ms 205 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 228 ms 204 ms 204 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 146 ms 156 ms 140 ms 196.44.0.74
8 148 ms 175 ms 146 ms africainx.cinx.net.za [196.223.22.47]
9 172 ms 179 ms 172 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.10G.za [41.84.13.66]
10 246 ms 204 ms 204 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.246]
11 170 ms 204 ms 157 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
12 169 ms 169 ms 204 ms row-access-switch1-row3-4.jnb1.host-h.net [197.189.193.36]
13 163 ms 200 ms 154 ms 197.242.89.170

Trace complete.

 

[ajan]

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=230ms TTL=47
Reply from 212.58.244.18: bytes=32 time=227ms TTL=47
Reply from 212.58.244.18: bytes=32 time=235ms TTL=47
Reply from 212.58.244.18: bytes=32 time=237ms TTL=47

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

Someone, please explain why ping to the UK is almost unaffected compared to local pings.

 

[jeanres]

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=230ms TTL=47
Reply from 212.58.244.18: bytes=32 time=227ms TTL=47
Reply from 212.58.244.18: bytes=32 time=235ms TTL=47
Reply from 212.58.244.18: bytes=32 time=237ms TTL=47

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

Someone, please explain why ping to the UK is almost unaffected compared to local pings.

do a traceroute

 

[ajan]

tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 130 ms 133 ms 131 ms 41-133-112-1.dsl.mweb.co.za
3 131 ms 130 ms 134 ms 197-84-96-210.cpt.mweb.co.za [197.84.96.210]
4 131 ms 125 ms 123 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 263 ms 258 ms 252 ms tengig-0-0-0-2-11-cpt-p-2.mweb.co.za [197.84.5.2
6]
6 257 ms 258 ms 257 ms tengig-0-7-0-0-cpt-p-1.mweb.co.za [197.84.4.33]

7 265 ms 265 ms 256 ms 197-84-4-201.cpt.mweb.co.za [197.84.4.201]
8 262 ms 259 ms 254 ms be-8-778-thd-p-1.mweb.co.za [176.67.177.145]
9 273 ms 272 ms 269 ms be-3-779-thd-up-1.mweb.co.za [176.67.177.227]
10 259 ms 250 ms 251 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
]
11 244 ms 247 ms 245 ms vl-3503-ve-117.csw1.London1.Level3.net [4.69.166
137]
12 262 ms 257 ms 266 ms ae-119-3505.edge4.London1.Level3.net [4.69.166.1

13 249 ms 244 ms 247 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
222]
14 * * * Request timed out.
15 * * * Request timed out.
16 256 ms 259 ms 265 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
17 257 ms 266 ms 261 ms 132.185.255.165
18 246 ms 254 ms 248 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

trace complete.

 

[jeanres]

Fine again this morning!