Telkom Slow International speed

RH360

Well-Known Member
Joined
Nov 14, 2006
Messages
200
Reaction score
5
Using Telkom ISP on Openserve. Since last weekend I have experienced slow international download speeds. It improved during the week and has again gone downhill this Friday. Is there a known issue with Telkom international capacity? Is this related to the Red Sea cable breaks? Testing with my Afrihost mobile data did not provide the same poor performance.
 
Using Telkom ISP on Openserve. Since last weekend I have experienced slow international download speeds. It improved during the week and has again gone downhill this Friday. Is there a known issue with Telkom international capacity? Is this related to the Red Sea cable breaks? Testing with my Afrihost mobile data did not provide the same poor performance.

It might be loss on your line, a little bit of loss will cause poor performance on high latency TCP based connections.

Also, Afrihost uses openserve/telkom for some of their international transit so Afrihost customers would have also noticed an issue if it was a telkom issue.

Try running pingplotter to queen.cisp.co.za or lon.hosted.co.za or whatever server you are seeing the bad speeds from.
 
Happy to pop you a test account to try, at least should give you an indication.

Just to clarify on the above Telkom buys from Openserve, even though Afrihost does as well. They also use Liquid to a higher extent typically.
 
It might be loss on your line, a little bit of loss will cause poor performance on high latency TCP based connections.

Also, Afrihost uses openserve/telkom for some of their international transit so Afrihost customers would have also noticed an issue if it was a telkom issue.

Try running pingplotter to queen.cisp.co.za or lon.hosted.co.za or whatever server you are seeing the bad speeds from.
During the week I had no issues with international services that I streamed. What I have noticed from all the speed test, it is only the download speed that's performing poor. The upload speed is always at the full line speed.
 
Happy to pop you a test account to try, at least should give you an indication.

Just to clarify on the above Telkom buys from Openserve, even though Afrihost does as well. They also use Liquid to a higher extent typically.
I would like to take you up on your offer of a test account. Was not aware that you can use other accounts on a fibre line. Used to be able to do that in the days of adsl.
 
I would like to take you up on your offer of a test account. Was not aware that you can use other accounts on a fibre line. Used to be able to do that in the days of adsl.
Sure thing, dropped you a PM.

Yeah you can switch accounts and ISPs on Openserves network.
 
It might be loss on your line, a little bit of loss will cause poor performance on high latency TCP based connections.

Also, Afrihost uses openserve/telkom for some of their international transit so Afrihost customers would have also noticed an issue if it was a telkom issue.

Try running pingplotter to queen.cisp.co.za or lon.hosted.co.za or whatever server you are seeing the bad speeds from.

The majority is Openserve as transit but there is a difference. Openserve is now offloading transit to 3rd parties for their customers like Afrihost which means it hops over to Openserve > Angola Cables and in some cases Angola Cables offloads to China Telecoms.

Openserve does not do this for Telkom. Telkom traffic strictly stays on Openserve network and if it needs to leave it goes via their Tier 1 transit.

You can see below the difference.

Some examples. Reverse from https://lg.nl.novoserve.com/
to 169.1.1.25

traceroute to 169.1.1.25 (169.1.1.25), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 185.147.12.31 (185.147.12.31) 1.416 ms 185.147.12.29 (185.147.12.29) 1.489 ms 1.437 ms
4 185.147.12.210 (185.147.12.210) 2.356 ms 2.257 ms 2.328 ms
5 angola-cables.telecity-hex67.nl-ix.net (193.239.119.54) 8.989 ms 8.937 ms 8.888 ms
6 185.148.115.246 (185.148.115.246) 9.953 ms 10.321 ms 10.204 ms
7 100.64.192.117 (100.64.192.117) 156.188 ms 155.997 ms 155.902 ms
8 102.130.69.4 (102.130.69.4) 155.674 ms 155.702 ms 155.919 ms
9 102.130.69.45 (102.130.69.45) 155.442 ms 155.433 ms 155.411 ms
10 rtdcj-os-cer-1-wan.osnet.co.za (196.25.153.41) 182.838 ms 180.935 ms rtdcj-os-cer-1-wan.osnet.co.za (196.25.199.141) 180.908 ms
11 * * *
12 100.127.0.182 (100.127.0.182) 175.913 ms 175.874 ms 175.888 ms
13 * * *
14 * * *
-- Traceroute timed out --

Reverse from https://lg.nl.novoserve.com/
to 165.165.119.177

traceroute to 165.165.119.177 (165.165.119.177), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 185.147.12.31 (185.147.12.31) 1.576 ms 1.212 ms 1.217 ms
4 185.147.12.210 (185.147.12.210) 2.488 ms 2.366 ms 2.362 ms
5 openserve.equinix-fra4.nl-ix.net (193.239.118.189) 8.462 ms 8.403 ms 8.354 ms
6 * * *
7 * * *
-- Traceroute timed out --
 
The majority is Openserve as transit but there is a difference. Openserve is now offloading transit to 3rd parties for their customers like Afrihost which means it hops over to Openserve > Angola Cables and in some cases Angola Cables offloads to China Telecoms.

Openserve does not do this for Telkom. Telkom traffic strictly stays on Openserve network and if it needs to leave it goes via their Tier 1 transit.

You can see below the difference.

Some examples. Reverse from https://lg.nl.novoserve.com/
to 169.1.1.25

traceroute to 169.1.1.25 (169.1.1.25), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 185.147.12.31 (185.147.12.31) 1.416 ms 185.147.12.29 (185.147.12.29) 1.489 ms 1.437 ms
4 185.147.12.210 (185.147.12.210) 2.356 ms 2.257 ms 2.328 ms
5 angola-cables.telecity-hex67.nl-ix.net (193.239.119.54) 8.989 ms 8.937 ms 8.888 ms
6 185.148.115.246 (185.148.115.246) 9.953 ms 10.321 ms 10.204 ms
7 100.64.192.117 (100.64.192.117) 156.188 ms 155.997 ms 155.902 ms
8 102.130.69.4 (102.130.69.4) 155.674 ms 155.702 ms 155.919 ms
9 102.130.69.45 (102.130.69.45) 155.442 ms 155.433 ms 155.411 ms
10 rtdcj-os-cer-1-wan.osnet.co.za (196.25.153.41) 182.838 ms 180.935 ms rtdcj-os-cer-1-wan.osnet.co.za (196.25.199.141) 180.908 ms
11 * * *
12 100.127.0.182 (100.127.0.182) 175.913 ms 175.874 ms 175.888 ms
13 * * *
14 * * *
-- Traceroute timed out --

Reverse from https://lg.nl.novoserve.com/
to 165.165.119.177

traceroute to 165.165.119.177 (165.165.119.177), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 185.147.12.31 (185.147.12.31) 1.576 ms 1.212 ms 1.217 ms
4 185.147.12.210 (185.147.12.210) 2.488 ms 2.366 ms 2.362 ms
5 openserve.equinix-fra4.nl-ix.net (193.239.118.189) 8.462 ms 8.403 ms 8.354 ms
6 * * *
7 * * *
-- Traceroute timed out --
Honestly I think Openserve is doing this because its too expensive to upgrade their pops vs just leveraging someone like Angola. I wouldnt be surprised if they migrate more traffic that way over time.


Those aren't major ports sizes for the modern era.
 
Last edited:
Honestly I think Openserve is doing this because its too expensive to upgrade their pops vs just leveraging someone like Angola. I wouldnt be surprised if they migrate more traffic that way over time.


Those aren't major ports sizes for the modern era.

That is exactly what it looks like. They probably got a sweet deal from Angola.

The problem is if you complain to them they just say but your traffic is carried without loss to and from the destination. They never guaranteed that the traffic will be exclusively on their AS. Their supported communities also doesn't allow you to prevent this. They can offload your traffic on cheap transit at their discretion.
 
That is exactly what it looks like. They probably got a sweet deal from Angola.

The problem is if you complain to them they just say but your traffic is carried without loss to and from the destination. They never guaranteed that the traffic will be exclusively on their AS. Their supported communities also doesn't allow you to prevent this. They can offload your traffic on cheap transit at their discretion.
Look as a transit provider this is very much the norm, they would still buy transit somewhere as they did before.

And it is still via their "AS"

These are unfortunately the restrictions in using local transit providers, your only choice is to try work with them. If you cant get to a point where you are happy then you need to go shopping for an alternative provider.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X