My internet is extremely slow at night.

InternetSwag, where CT are you?

I had a similar issue to this a few years back, found out it was due to telkom routing all clareinch and rondebosch traffic through City Bowls exchange before hitting the back bone, some idiot engineer apparently caused this.

Best thing you can do, is try get hold of the technicians at your exchange, help desk is useless. Perhaps they can switch your port back to a legacy connection or try up it to 2Mbs and see what the ping looks like. You'll need to log an online fault on telkoms website. I know a friend has this issue in rondebosch now, I dont live there anymore, so i cant comment.
 
Hi There,
Congested exchanges are the cause of these problems. The tracert as asked for will show you the delays in the system. I would also do one about 8am in the morning for comparison. The first hop is your router and the second is the exchange. If the second one is much longer at night than in the day then the exchange is the source of the bottleneck.
Highlighting the issue to Telkoom is a good idea. If no one complains then they will not be keen to do anything to resolve it.

Regards

Tim
 
Latency OK, but :

2781904833.png
 
C:\Users\User>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=2088ms TTL=49
Reply from 212.58.244.68: bytes=32 time=2105ms TTL=49
Reply from 212.58.244.68: bytes=32 time=2041ms TTL=49
Request timed out.

Ping statistics for 212.58.244.68:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2041ms, Maximum = 2105ms, Average = 2078ms



C:\Users\User>ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=1443ms TTL=51
Reply from 41.203.21.137: bytes=32 time=1391ms TTL=51
Reply from 41.203.21.137: bytes=32 time=1445ms TTL=51
Reply from 41.203.21.137: bytes=32 time=1513ms TTL=51

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1391ms, Maximum = 1513ms, Average = 1448ms


Telkom 4 MbitAdsl + Afrihost 4 Mbit Uncapped Business ADSL
 
Last edited:
Hein_JHB said:
C:\Users\User>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=2088ms TTL=49
Reply from 212.58.244.68: bytes=32 time=2105ms TTL=49
Reply from 212.58.244.68: bytes=32 time=2041ms TTL=49
Request timed out.

Ping statistics for 212.58.244.68:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2041ms, Maximum = 2105ms, Average = 2078ms

Telkom 4 MbitAdsl + Afrihost 4 Mbit Uncapped Business ADSL
Click to expand...

Do a tracert rather? The first hop will tell us whether it's exchange congestion or plain throttling by your ISP.
 
C:\Users\user>tracert www.myadsl.co.za

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 2065 ms * * 105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6
.65]
3 1766 ms * 1603 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178
.41]
4 * 1725 ms 1791 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 1661 ms * 1626 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 1919 ms 1620 ms 1580 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 * 1598 ms 1637 ms 196.44.31.99
8 1652 ms 1568 ms 1936 ms 196.30.1.39
9 1367 ms 1417 ms 1333 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.n
et [196.31.220.21]
10 1518 ms 1384 ms 1361 ms tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.150]
11 1555 ms * * core-router1.jnb2.host-h.net [196.30.213.108]
12 2175 ms 1630 ms 1784 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
13 1834 ms 2021 ms 1759 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
Hein_JHB said:
C:\Users\user>tracert www.myadsl.co.za

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 2065 ms * * 105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6
.65]
3 1766 ms * 1603 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178
.41]
4 * 1725 ms 1791 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 1661 ms * 1626 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 1919 ms 1620 ms 1580 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 * 1598 ms 1637 ms 196.44.31.99
8 1652 ms 1568 ms 1936 ms 196.30.1.39
9 1367 ms 1417 ms 1333 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.n
et [196.31.220.21]
10 1518 ms 1384 ms 1361 ms tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.150]
11 1555 ms * * core-router1.jnb2.host-h.net [196.30.213.108]
12 2175 ms 1630 ms 1784 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
13 1834 ms 2021 ms 1759 ms mybroadband.co.za [41.203.21.137]

Trace complete.
Click to expand...

Yep, looks like you have a very bad case of exchange congestion, better start bugging Telkom.
 
Been having the same issue with 8ta, from 7pm i start feeling the laggggggg
 
There's NOTHING you can do about it. I've been on a congested exchange for over 8 months now - Stupid latencys every single evening for 8 months, this is hell.
Telkom refuse to even acknowledge there's a problem.
 
chun said:
Have had similar issues for the last couple of months here in Capetown.

Tracerouting during the day, my first hop is 9-20ms. After hours and weekends its 100-300ms !

After logging four calls, finally spoke to someone who seems to know what they are doing this morning. Informed them that my wife's line does not experience these issues so they are going to move me to her 'card' (?) to see if that helps.

Fingers crossed.
Click to expand...



Just an update for those interested. A techie arrived at my gate yesterday and after a chat about the problem, drove off to the exchange. Half an hour later my line had been moved to one of the ADSL2 cards and my line bumped to 10 meg. Also pings have been normal since.
 
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Michael>tracert www.bbc.co.uk

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

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 8 ms 8 ms 7 ms 224-252-1.dsl.subscriber.telkomsa.net [105.224.2
52.1]
3 10 ms 9 ms 8 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 9 ms 8 ms 8 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 10 ms 10 ms 9 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 153 ms 154 ms 156 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 183 ms 184 ms 184 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 * * * Request timed out.
9 * * * Request timed out.
10 203 ms 196 ms 189 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 197 ms 198 ms 197 ms 132.185.255.149
12 188 ms 189 ms 189 ms bbc-vip113.telhc.bbc.co.uk [212.58.244.68]

Trace complete.

C:\Users\Michael>
 
I'm having serious latency problems here even though the technician came out in 10 minutes, he says he can do nothing but escalate the problem as it lays at the UMC. So now I have to wait until they fix the UMC and how long will that take since they told me I'm not going to get upgraded soon. :mad: syncing at 409500 but UMC is served with ATM backhaul on a ADSL2+ UMC

http://speedof.me/show.php?img=130625003236-11415.png on 4 Mbps
 
Last edited:
Just phoned telkom, my latency is 2300 today.

NO ONE OF THEM UNDERSTAND ONLINE GAMING.

THEY HAD ME DELETE MY COOKIES TO IMPROVE MY PING IN WOW FFS

Then twice they stop talking and the phone goes dead these pieces of **** are hanging up on me BECAUSE THEY CANNOT HELP ME
 
Last edited by a moderator:
InternetSwag said:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Michael>tracert www.bbc.co.uk

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

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 8 ms 8 ms 7 ms 224-252-1.dsl.subscriber.telkomsa.net [105.224.2
52.1]
3 10 ms 9 ms 8 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 9 ms 8 ms 8 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 10 ms 10 ms 9 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 153 ms 154 ms 156 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 183 ms 184 ms 184 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 * * * Request timed out.
9 * * * Request timed out.
10 203 ms 196 ms 189 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 197 ms 198 ms 197 ms 132.185.255.149
12 188 ms 189 ms 189 ms bbc-vip113.telhc.bbc.co.uk [212.58.244.68]

Trace complete.

C:\Users\Michael>
Click to expand...

That doesn't look like congestion at all, Michael :p. Was this tracert done during the slowdown?
 
Code: 
traceroute to www.l.google.com (197.80.128.55), 30 hops max, 65000 byte packets
 1  Billion.400G (10.0.0.2)  1.788 ms F=1500  1.757 ms  1.727 ms
 2  41-132-76-1.dsl.mweb.co.za (41.132.76.1)  36.970 ms F=1492  37.565 ms  36.834 ms
 3  197-80-4-82.jhb.mweb.co.za (197.80.4.82)  498.726 ms  525.253 ms  528.174 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  520.607 ms  486.437 ms  504.794 ms
 5  tengig0-0-0-2.11.vic-p-1.mweb.co.za (196.22.169.225)  523.976 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za (196.22.169.241)  522.679 ms  524.642 ms
 6  tengig0-1-0-0.vic-pe-11.mweb.co.za (197.80.4.125)  523.720 ms  528.936 ms  524.577 ms
 7  * * *
 8  * * *
 9  * * *

This is getting out of hand now.
 
:mad:

@linuxmint ~ $ traceroute www.facebook.com
traceroute to www.facebook.com (31.13.72.17), 30 hops max, 60 byte packets
1 Billion.400G (10.0.0.2) 1.232 ms 2.442 ms 2.397 ms
2 41-132-76-1.dsl.mweb.co.za (41.132.76.1) 34.814 ms 34.814 ms 34.803 ms
3 197-80-4-106.jhb.mweb.co.za (197.80.4.106) 499.906 ms 503.572 ms 505.475 ms
4 vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 509.094 ms vl-92.vic-hscore-1.mweb.co.za (196.22.189.2) 511.621 ms 514.046 ms
5 tengig0-0-0-2.11.vic-p-2.mweb.co.za (196.22.169.226) 702.814 ms 702.814 ms 705.704 ms
6 pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7) 710.325 ms pos0-3-0-0.lon-up-1.mweb.co.za (197.80.5.9) 681.769 ms pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7) 687.353 ms
7 176.67.177.131 (176.67.177.131) 685.662 ms 693.420 ms 688.440 ms
8 176.67.177.228 (176.67.177.228) 693.384 ms 176.67.177.133 (176.67.177.133) 660.558 ms 176.67.177.228 (176.67.177.228) 665.470 ms
9 195.66.237.69 (195.66.237.69) 685.738 ms 195.66.237.121 (195.66.237.121) 663.494 ms 195.66.237.69 (195.66.237.69) 685.712 ms
10 ae1.bb02.lhr2.tfbnw.net (31.13.30.198) 676.238 ms 679.058 ms 677.355 ms
11 * ae0.pr02.lhr2.tfbnw.net (31.13.30.197) 702.413 ms 693.968 ms
12 po126.msw01.04.lhr2.tfbnw.net (31.13.25.157) 691.895 ms 694.566 ms *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X