Vanderbijlpark SE3 ADSL problems

[M10]

- High latency/slow speed

- 016 932 xxxx

- ADSL Line speed 4Mbps

-MWEB uncapped

- 5pm to 12pm weekdays and all throughout weekends

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

1 <1 ms <1 ms 1 ms 192.168.0.254
2 1114 ms 1016 ms 919 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 840 ms 865 ms 910 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 1000 ms 1103 ms 1104 ms 197-80-2-2.jhb.mweb.co.za [197.80.2.2]
5 887 ms 766 ms 779 ms 197-80-5-241.jhb.mweb.co.za [197.80.5.241]
6 825 ms 925 ms 841 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 868 ms 905 ms 1010 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 1089 ms 1130 ms 1238 ms 196.43.25.137
9 979 ms 1043 ms 981 ms 196.43.39.166
10 957 ms 889 ms 820 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 791 ms 757 ms 771 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
12 742 ms 860 ms 771 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

- Line sync speed: Downstream 4096 Kbps Upstream 512 Kbps

- Line attenuation stats
Attenuation: Downstream 39.5 dB Upstream 23.5 dB
Noise Margin: Downstream 13.3 dB Upstream 12.0 dB

 

[grubsner]

Hi M10,

I'm surprised that you have issues on the Eligwa Park exchange. I have one adsl line on this exchange and one adsl line on the Golf Estate UMC (fed via fiber from this exchange) and both lines have good latency and speeds. I will post a trace route when I get home tonight as comparison.

I do know that Telkom did some maintenance work on this exchange over the weekend up until Tuesday (6/8/13). Might be related to the high latency.

The only issue I have with Eligwa Park is that the exchange is still on ATM links and the maximum speed available is 4 Mbps. All the surrounding exchanges have Metro Ethernet...it's high time this exchange and supported UMCs are upgraded. Telkom argument against this is that the exchange is not congested.

EDIT: on second thoughts, you might be connected to one of the UMC's located in SE3. You might be connected to the one located on the corner of Beefwood and Koorsboom? This UMC might be congested. Log a complaint with 10210 and report it. You can also drop TelkomZA a PM...

Good luck!

 

[M10]

The problem started 22 July, line was still fine and working perfectly the previous night. Normally I'd get an average 20ms on every hop to local sites regardless of the time of day.

Also have reported the issue twice already to telkom but so far nothing has come of this.

I live on Jakaranda street, I have no idea how the area's line are being connected but possible I guess that I'm linking up with the UMC at Beefwood/Koorsboom

 

[grubsner]

If you are in Jakaranda Str you are more than likely connected directly to the Eligwa Park Exchange. The Koorsboom UMC only serves South of Beefwood. I will do a trace route tonight and post the results.

Speak to Telkom ZA for assistance.

HTH

 

[grubsner]

M10,

Ok it seems that Eligwa Park is congested; ISP TelkomSA on 1 Mb line:

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

1 23 ms 33 ms 74 ms 192.168.1.6
2 507 ms 515 ms 580 ms ti-224-148-01.telkomadsl.co.za [105.224.148.1]
3 685 ms 689 ms 626 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 576 ms 480 ms 461 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 522 ms 479 ms 476 ms 165.165.216.221
6 414 ms 423 ms 446 ms 196.43.39.166
7 380 ms 404 ms 364 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 461 ms 399 ms 388 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 352 ms 370 ms 347 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

In comparison on the other line on Golf Estate UMC, 4 Mb line TelkomSA:

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

1 <1 ms <1 ms <1 ms 192.168.1.3
2 9 ms 9 ms 9 ms ti-224-148-01.telkomadsl.co.za [105.224.148.1]
3 12 ms 12 ms 12 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 12 ms 12 ms 12 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 13 ms 13 ms 13 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 13 ms 13 ms 12 ms 196.43.39.166
7 13 ms 13 ms 13 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 15 ms 15 ms 15 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 15 ms 15 ms 15 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

I guess I will have to chase this up with TelkomZA...

 

[NetDude]

Hi,

I know how painful what you are experiencing is!!!

I lived with a similar pain for two weeks. I also live SE3. I also only struggled during the hours you mentioned. It's painful to run speedtest at 5:30 and ping is 26ms... Only to get 800ms after 18:00.

So, I'm gonna try to summarize what eventually helped. It took almost two weeks to resolve, so I really can't give a detailed account. Feel free to ask specific questions and I'll be happy to elaborate.

I called my ISP (Afrihost) every evening to complain. It soon became obvious that Telkom was fault. Three faults were logged with Telkom, the first two were closed without any resolution. Telkom informed me that everything was fine. The first week I made a mistake by calling in the evenings. Afrihost promised that they would escalate. But, I think it's best to call during the day and put pressure on your ISP to speak to Telkom while you hold.

Eventually I realized that it was best to call Telkom (10219) directly. Things started moving a bit but not as fast as I had hoped. I also took the matter to Twitter and Afrihost's response was instant. So, whoever was responding to my tweets put pressure on Telkom. I also called 10219 directly to put the pressure at the same time. At some point Telkom just said the exchange was congested and they were not planning to upgrade. I was a few days away from getting a mobile router to go 3G.

I though that I'd try Telkom one more time and plead/beg. To this day, I'm still not sure what happened, or what they did... The last call I made to Telkom they informed me that a techie was gonna go try something at the exchange. I received an SMS informing me that the issue had been resolved and I should test after 18:00. I got home that evening and all was well..

I'm not sure if this is gonna be of any help to you. I hope that your issue gets resolved. All I can say, be a pest... Call almost every 3 hours, I know it's crazy. Be patient and appeal to people you talk to... It's so easy to lose your cool. But I've learnt that that approach hardly gets people on your side. All the best!!!

 

[grubsner]

NetDude, thanks for the feedback. Can you remember the date your issues were resolved? I have escalated this to TelkomZA. I know that the Vanderbijlpark CBD exchange is on 10 Mb and not congested but there seems to be a link issue from Eligwa back to the CBD exchange.

I will start phoning on Monday to get this **** sorted out. Something at the exchange was changed recently. We never had any issue since a few days ago.

We might be able to sort this out. I have been talking to some Telkom managers in Vereeniging when our UMC UPS batteries needed replacement. I'll most definitely will phone these guys on Monday.

 

[NetDude]

@grubsner, my issue started on July 22nd and was resolved on August 5th!

Please do report back... My line is only capable of 4mbps. What about yours before the issue?

 

[M10]

My issue started Monday the 22nd of July. Was working fine all day/night the Sunday (usual ~20ms local and 200ms international) and after work on Monday both local and international was +500ms and its been that ever since.

 

[grubsner]

@grubsner, my issue started on July 22nd and was resolved on August 5th!

Please do report back... My line is only capable of 4mbps. What about yours before the issue?

I have a 1 Mbps line, the downloads still get through but the latency is very bad. Currently at 1000ms plus to local sites (Sunday evening)

 

[Devastat0r36]

Vanderbijlpark SE6 Area is having the same problem

 

[NetDude]

Vanderbijlpark SE6 Area is having the same problem

@Devastat0r36, check this thread out on what to do. . . If you haven't done so already?

 

[Devastat0r36]

The problem was resolved for about four weeks now in SE6 but has started again 2013-09-07
but this time the latency is around 500ms and it about same day and night.