ADSL - Cape Town General

At about 8.30am things suddenly came right.
I don't know if it is going to hold up or a fluke.

I had even very high latency on my 2nd Hop- the exchange since last week, now suddenly drop back to its normal 5ms it used to be for years.

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

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 5 ms 6 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 6 ms 5 ms 5 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 7 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 7 ms 6 ms 196.44.31.106
7 11 ms 6 ms 6 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 7 ms 7 ms 7 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 9 ms 10 ms 11 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 22 ms 19 ms 23 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 19 ms 19 ms 21 ms 196.28.178.66
12 9 ms 8 ms 7 ms cte-core-sw2.vwol.net [196.41.144.35]
13 26 ms 26 ms 31 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
At about 9.30am things suddenly came right.
I don't know if it is going to hold up or a fluke.

I had even very high latency on my 2Hop- the exchange since last week, now suddenly drop back to its normal 5ms it used to be for years.

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

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 5 ms 6 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 6 ms 5 ms 5 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 7 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 7 ms 6 ms 196.44.31.106
7 11 ms 6 ms 6 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 7 ms 7 ms 7 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 9 ms 10 ms 11 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 22 ms 19 ms 23 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 19 ms 19 ms 21 ms 196.28.178.66
12 9 ms 8 ms 7 ms cte-core-sw2.vwol.net [196.41.144.35]
13 26 ms 26 ms 31 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Seems I spoke to soon!

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

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 6 ms 6 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 43 ms 33 ms 29 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 30 ms 30 ms 24 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 7 ms 7 ms 196.44.31.106
7 27 ms 34 ms 37 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 24 ms 29 ms 28 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 53 ms 49 ms 50 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 58 ms 55 ms 52 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 87 ms 78 ms 74 ms 196.28.178.66
12 36 ms 35 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
13 9 ms 10 ms 9 ms www.mweb.co.za [196.2.63.110]

Trace complete.

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

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 47 ms 48 ms 46 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 35 ms 29 ms 32 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 134 ms 89 ms 82 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 107 ms 115 ms 109 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 103 ms 116 ms 117 ms 196.44.31.106
7 139 ms 132 ms 136 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 128 ms 131 ms 131 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 106 ms 97 ms 91 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 71 ms 64 ms 58 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 65 ms 62 ms 64 ms 196.28.178.66
12 74 ms 67 ms 72 ms cte-core-sw2.vwol.net [196.41.144.35]
13 81 ms 81 ms 67 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
My internet weekend was just sucky, Friday night it was useless, Saturday was mostly useless with latency going up and down randomly. Sunday was good up until 9pm, then there was no internet,couldn't even connect.

Rather odd as I never use to have any problems up until the last 3 weeks.

Something must be cooking.
 
As per usual latency at night is still useless, tested using 3 different ISP's with the same result.

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

1 <1 ms 1 ms <1 ms 192.168.1.254
2 345 ms 345 ms 337 ms 224-80-1.dsl.subscriber.telkomsa.net [105.224.80
.1]
3 329 ms 347 ms 340 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 310 ms 297 ms 315 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 338 ms 318 ms 327 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 321 ms 302 ms 331 ms 196.43.52.42
7 325 ms 358 ms 368 ms 196.43.25.138
8 370 ms 361 ms 333 ms gigabitethernet1-1-2.vic-pr-1.mweb.co.za [197.80
.4.118]
9 372 ms 341 ms 359 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]

10 357 ms 366 ms 346 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 331 ms 322 ms 332 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

12 367 ms 365 ms 350 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 351 ms 366 ms 345 ms 196.28.178.66
14 311 ms 331 ms 356 ms cte-core-sw2.vwol.net [196.41.144.35]
15 366 ms 364 ms 345 ms www.mweb.co.za [196.2.63.110]

Trace complete.

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

1 <1 ms 1 ms 1 ms 192.168.1.254
2 311 ms 320 ms 338 ms 196-210-146-129.dynamic.isadsl.co.za [196.210.14
6.129]
3 314 ms 298 ms 300 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 334 ms 316 ms 283 ms 196.35.115.128
5 342 ms 316 ms 315 ms core2a-ctn-gi0-2.ip.isnet.net [168.209.6.6]
6 338 ms 311 ms 309 ms 168.209.2.131
7 246 ms 236 ms 256 ms mweb-2.cinx.net.za [196.223.22.25]
8 334 ms 351 ms 340 ms 197-84-4-224.cpt.mweb.co.za [197.84.4.224]
9 335 ms 323 ms 330 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
10 338 ms 325 ms 325 ms 196.28.178.66
11 329 ms 329 ms 330 ms cte-core-sw2.vwol.net [196.41.144.35]
12 348 ms 319 ms 302 ms www.mweb.co.za [196.2.63.110]

Trace complete.

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

1 <1 ms 1 ms 1 ms 192.168.1.254
2 321 ms 337 ms 346 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.
4.193]
3 318 ms 349 ms 357 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 335 ms 315 ms 405 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 322 ms 298 ms 283 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 331 ms 332 ms 319 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 341 ms 323 ms 304 ms 196.44.0.74
8 324 ms 311 ms 303 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

9 293 ms 308 ms 307 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]

10 376 ms 374 ms 322 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 264 ms 280 ms 308 ms 196.28.178.66
12 318 ms 295 ms 286 ms cte-core-sw2.vwol.net [196.41.144.35]
13 312 ms 344 ms * www.mweb.co.za [196.2.63.110]
14 322 ms 310 ms 324 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
A friend of mine who lives less than 2 kilometers away is using Afrihost capped account and having absolutely no issues. I on the other hand am using OpenWeb Gamers account and I am having the same endless issues as listed by many of the users posted before on this thread. Internet is fine all day and morning, but goes to **** in the evenings. These past couple of days my pings have started to be affected as well, which strangely was always fine while my download speeds were only at about a 1mb out of 4mb.

Could it be that the MTN routing is helping the Afrihost capped accounts that my buddy is not affected?? I'm gonna trial a 1GB free from Afrihost and see how things go. Will post again tonight once done.
 
I very much doubt it's ISP related as I have 3 different ones that perform exactly the same. The problem IMO lies with telkom maintenance,upgrading,exchange congestion, with the latter more than likely being the issue as pretty much everyone now has uncapped and hammering away :(

For the first time in many weeks my internet was back to normal last night, I could actually play games without lagging my hears off...... just hope it lasts.
 
Yeah spot on man. Afrihost gets more stable and better pings, but speeds are still limited. Here's to hoping that Telkom can get this under wraps quickly. Cause to have to pay for 4mb line and get 1mb speeds suck.
 
Well this is just getting ridiculous now. Since I checked again last night I'm getting pings as high as 3000ms locally! Pingtest can barely even finish it takes so long. I emailed Cybersmart about it, now to see if they do anything. I've never even heard of 3000ms pings...
 
Ive been having insane issues the past few weeks, I heard theres something wrong with the undersea cable from friends but not 100% sure. These are my speedtest results from 5 minutes ago, Its a 2mb line with a premium 10gb telkom internet account. Test conducted on 13 April 2013 11:14:12 AM

Download Speed: 225 kbps (28.1 KB/sec transfer rate)

Upload Speed: 388 kbps (48.5 KB/sec transfer rate)

Latency: 301 ms
 
Telkom guy came today. Was far more useless than expected. Showed him the outrageous pingtests I'd captured in the evenings and he seemed to think nothing of them! 1200ms yeah that's totally all right -.- As far as he's concerned the speed is fine so there's nothing wrong!
 
Fresh From The Grave said:
Telkom guy came today. Was far more useless than expected. Showed him the outrageous pingtests I'd captured in the evenings and he seemed to think nothing of them! 1200ms yeah that's totally all right -.- As far as he's concerned the speed is fine so there's nothing wrong!
Click to expand...

Same shyte my best team player gets. As long as you can open a web page, they reckon nothing wrong...
 
Something going wrong here in Table view also. Our office has been dropping connection every day so far this month, put together a nice graph to find the trend.

OK is ADSL up and able to resolve addresses.
FAILOVER is 3G and able to resolve addresses.
OFFLINE is either one where dns resolution is not possible.

3g_failover.jpg
 
Fresh From The Grave said:
Telkom guy came today. Was far more useless than expected. Showed him the outrageous pingtests I'd captured in the evenings and he seemed to think nothing of them! 1200ms yeah that's totally all right -.- As far as he's concerned the speed is fine so there's nothing wrong!
Click to expand...

Telkom technician is not trained to sort out you latency afik.
If the wiring is good and doesn't find any other line or equipment issues, his work is done.
Escalate the problem with Telkom if you think it is not ISP related. Eventually they will assign a Network expert to the problem.
 
Fresh From The Grave said:
Telkom guy came today. Was far more useless than expected. Showed him the outrageous pingtests I'd captured in the evenings and he seemed to think nothing of them! 1200ms yeah that's totally all right -.- As far as he's concerned the speed is fine so there's nothing wrong!
Click to expand...

Get them to change your port at the exchange. The same thing happened to me when they apparently "upgraded" me to a newer port. Just get them to switch you back to the old circuit if they have.
 
I had a issue about a month+ ago.
I kept a full log of all my trace routes done on 3 ISP accounts and also the Telkom Guest account to show that it is a exchange problem.

The Telkom techy tested my line and all showed up perfect.
He then made a call to a Network Specialist who looked at other things, like the over all performance of the exchange and also the DSLAM I was connected too.
He noticed that around 7pm - 12pm my DSLAM was hitting its max peak.
That was the times my line went for a ball of poop.

He (network specialist) then re-assigned my number/line to a another DSLAM, 30min later the line was re-patched to the new DSLAM at the exchange and since then all problems solved.

"Touch wood" been more then a month now.

So it just matters if you get a techy who knows what you talking about, and knows who to call to help him.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X