Polymathic
Honorary Master
- Joined
- Mar 22, 2010
- Messages
- 33,669
- Reaction score
- 14,746
Comparing my Telkom account to my pre-paid Axxess voucher, the pings from Telkom are almost double. Why?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be subscribing to the new Disney+ R49 streaming package?
Why are telkom pings so high
- Thread starter Polymathic
- Start date
To SA servers I notice no difference between my IS and Telkom accounts (~35ms).
To EU and US servers Telkom shaped accounts will get awful ping ~350ms.
The ping to US servers is always about this though, regardless of ISP.
To SEA servers Telkom will get great ping ~200ms
I don't know if the route to EU servers is SA -> SEA -> EU, but I think the more probable reason is that the route via SAFE is unshaped and the route via SAT-3 is heavily shaped.
To EU and US servers Telkom shaped accounts will get awful ping ~350ms.
The ping to US servers is always about this though, regardless of ISP.
To SEA servers Telkom will get great ping ~200ms
I don't know if the route to EU servers is SA -> SEA -> EU, but I think the more probable reason is that the route via SAFE is unshaped and the route via SAT-3 is heavily shaped.
My own experience is the same as yours
My Axxess / Afrihost (170-230ms) IS -> Seacom Fibre
Telkom do1 (380-450ms) Telkom/SAIX -> SAT-3 Fibre
Telkom is a very bad choice for gaming that is why I was amazed to hear when my one friend said he doesn't play international games online because of the ping (ofc he was using Telkom).
He didn't believe me that its possible to game INTERNATIONALLY with a good ISP until I went and bought him a 1 gig account at Afrihost.
Personally I don't like gaming with South Africans too much.. Its usually one sided since our servers are based in JHB/CT the guys who live there tend to have superior pings(20-30) whereas we in the middle will have 60-80, I'd just as well play internationally and have a blast than trying to compete seriously locally.
My Axxess / Afrihost (170-230ms) IS -> Seacom Fibre
Telkom do1 (380-450ms) Telkom/SAIX -> SAT-3 Fibre
Telkom is a very bad choice for gaming that is why I was amazed to hear when my one friend said he doesn't play international games online because of the ping (ofc he was using Telkom).
He didn't believe me that its possible to game INTERNATIONALLY with a good ISP until I went and bought him a 1 gig account at Afrihost.
Personally I don't like gaming with South Africans too much.. Its usually one sided since our servers are based in JHB/CT the guys who live there tend to have superior pings(20-30) whereas we in the middle will have 60-80, I'd just as well play internationally and have a blast than trying to compete seriously locally.
Last edited:
HavocXphere
Honorary Master
IS local pings are always lower than other kinds of cap. No idea why. Usually causes ~50ms difference.
davemc
Executive Member
This is why ISP's should be forced to reveal their landing points for the particular product that you are purchasing.
I think you'll find the best latency to New York and London on most SIAX based products, and that living in Cape-Town gives you the best low-latency.
Whereas Seacom based products could end up landing anywhere from Egypt or China or France, and have the lowest local latency if you live in Gauteng.
It's not really trade-secret information neither.
But, ask any ISP about their landing points and they get defensive and even aggressive about the information.
I think you'll find the best latency to New York and London on most SIAX based products, and that living in Cape-Town gives you the best low-latency.
Whereas Seacom based products could end up landing anywhere from Egypt or China or France, and have the lowest local latency if you live in Gauteng.
It's not really trade-secret information neither.
But, ask any ISP about their landing points and they get defensive and even aggressive about the information.
here is my ping test result. i got it from here whoisxy
Pinging cooltamil.com [64.64.4.118] with 32 bytes of data:
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Reply from 64.64.4.118: bytes=32 time=53ms TTL=52
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Ping statistics for 64.64.4.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 53ms, Average = 51ms
Pinging cooltamil.com [64.64.4.118] with 32 bytes of data:
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Reply from 64.64.4.118: bytes=32 time=53ms TTL=52
Reply from 64.64.4.118: bytes=32 time=51ms TTL=52
Ping statistics for 64.64.4.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 53ms, Average = 51ms