Welcome to the
Telkom Community

Get involved. Problem solved.
Showing results for 
Search instead for 
Do you mean 
Reply
Established Member
Posts: 6

Congestion in Douglasdale, Johannesburg

My 4 Mbps ADSL line gets a maximum of 0.5 Mbps on www.speedtest.com, yet when I download files using torrents or a download manager, I'm able to use the FULL line speed - I have seen it downloading at 400kb/s. This implies that there is congestion on the exchange.

 

The problem used to be limited to peak times, but now it's happening any time of day. I have complained to the helpdesk for over a year. When is this problem going to be resolved?

 

My phone number starts with 011 462, if this helps identify which exchange I'm connected to.

Highlighted
Regular Contributor
Posts: 498

Re: Congestion in Douglasdale, Johannesburg

@KamikazeHamster the fact that your line can get full 400kbps indicates that the exchange is not congested then? If the highway is backed up with traffic, no car can come screaming through at 200km/h...

Established Member
Posts: 6

Re: Congestion in Douglasdale, Johannesburg

Your assumption is that Telkom is managing the entire highway and giving preference to the whole line. When I run a speed test, I get between 0.25 and 0.5Mbps, which is NOT the full 4 Mbps. So that means that each page loads extremely slowly.

 

What a download manager/torrent client do is make HUNDREDS of different streams and split the file up into tiny little parts. That means that when there are 1000 TCP packets being sent and received, each single packet is getting a share of the priority. If I download a torrent and my neighbour downloads a torrent, that means that I get 1000 packets shared evenly with their 1000 packets. But if I visit Google's website, I get 3 or 4 packets and my neighbour gets 1000 packets. So I only get a tiny bit of priority in comparison. That's why visiting Facebook is EXTREMELY slow while downloading a file is very fast.

 

That's why it implies congestion on the exchange.

Regular Contributor
Posts: 498

Re: Congestion in Douglasdale, Johannesburg

@KamikazeHamster again, the fact that you get 400kbps shows that your Telkom line and exchange is able to deliver full line speed. Usually torrent as a P2P protocol will be managed to give preference to more mainstream protocols like http. There might be something else wrong. Have you reported this to your ISP, as they have their own network and IPC connection. I was aware that over the weekend MTN had some network issues. Check who your ISP uses for their backhaul. If that checks out, log a fault with Telkom

Established Member
Posts: 6

Re: Congestion in Douglasdale, Johannesburg

You are not listening. This problem has been happening for over a year. I have complained to Telkom. I have complained to my ISP. I have spoken to countless people about this. I've complained all over MyBroadband and they ALL agree that it's congestion.

Established Member
Posts: 6

Re: Congestion in Douglasdale, Johannesburg

Zertop's LineTool Results
Date/Time: Wed Feb 17 15:30:50 CAT 2016

Basic Report:

Your packet loss was 20%.
Your average ping was 35ms.
Your maximum ping was 43ms.

You seem to have some packet loss. This indicates an issue on the line.

Detailed Report:

Pinging 169.0.12.1 with 32 bytes of data:
Request timed out.
Reply from 169.0.12.1: bytes=32 time=27ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=43ms TTL=254
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=35ms TTL=254
Reply from 169.0.12.1: bytes=32 time=37ms TTL=254
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=40ms TTL=254
Reply from 169.0.12.1: bytes=32 time=38ms TTL=254
Reply from 169.0.12.1: bytes=32 time=39ms TTL=254
Reply from 169.0.12.1: bytes=32 time=31ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=42ms TTL=254
Reply from 169.0.12.1: bytes=32 time=39ms TTL=254
Reply from 169.0.12.1: bytes=32 time=38ms TTL=254
Reply from 169.0.12.1: bytes=32 time=41ms TTL=254
Reply from 169.0.12.1: bytes=32 time=42ms TTL=254
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Reply from 169.0.12.1: bytes=32 time=32ms TTL=254
Reply from 169.0.12.1: bytes=32 time=41ms TTL=254
Reply from 169.0.12.1: bytes=32 time=28ms TTL=254
Reply from 169.0.12.1: bytes=32 time=34ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=36ms TTL=254

Ping statistics for 169.0.12.1:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 43ms, Average = 35ms

 

Frequent Contributor
Posts: 326

Re: Congestion in Douglasdale, Johannesburg

A ping test doesn't say anything about congestion.  Can we see a trace route that shows the exchange congestion?  

 

BTW no-one is saying you are wrong, we are all simply peers trying to see if we can help - some of us are laymen, others have pretty good experience and qualifications in the relevant fields ....  your choice whether you want us to try to help or not

Found the answer to your question? Don't forget to Accept the Solution! 

Did you like someone's contribution? Give Kudos where Kudos are due!

Just because something doesn’t do what you planned it to do doesn’t mean it’s useless. – Thomas Edison (Inventor)
Established Member
Posts: 6

Re: Congestion in Douglasdale, Johannesburg

Here's the tracert during the day. It's k@k slow right now, so maybe it's a port issue? Is it worth getting a Telkom guy out here? Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.0.0.2 2 28 ms 32 ms 36 ms 169-0-12-1.ip.afrihost.co.za [169.0.12.1] 3 * 42 ms 43 ms jhb-up1.ip.adsl.co.za [169.1.5.5] 4 30 ms 36 ms 53 ms jhb-rx1.ip.adsl.co.za [169.1.5.18] 5 30 ms 44 ms 28 ms jhb-up8b.ip.adsl.co.za [169.1.5.56] 6 61 ms 96 ms 80 ms google.jb1.napafrica.net [196.46.25.166] 7 44 ms * 34 ms 72.14.239.53 8 34 ms 34 ms 36 ms google-public-dns-a.google.com [8.8.8.8] Trace complete.
About This Post
  • 7 replies
  • 1969 views
  • 1 kudo
  • 3 Contributors