South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Heh, was told by support to reboot my router. I'll wait to see if there's any improvement tomorrow then, I guess.
I'm using default DNS as well.
Netflix is so well connected on the network that the likelihood of it being the symptom of anything on our end is incredibly slim. I suspect there may be something area specific going on here though looking at the location of the reports though.
When the guys ask you to reboot they often do so because they refresh the account and it will try to refresh the routing, so it's often a good idea to do so. Same applies to a power cycle if the guys ask you to do so. I know it's a pain but there are a plethora of issues that are often resolved with a reboot on your side and refresh on our side.
CW you spent sometime speaking to me yesterday regarding the Netflix performance on the Roku - and yet it works fine on other test accounts. Based on the other feedback tonight it's clear where the problem lies... You hogging the Netflix bandwidth on your test bench![]()
CW you spent sometime speaking to me yesterday regarding the Netflix performance on the Roku - and yet it works fine on other test accounts. Based on the other feedback tonight it's clear where the problem lies... You hogging the Netflix bandwidth on your test bench![]()
As per my discussion with support - After a test and indication that there was packet loss on my end, I am testing Path of Exile with an alternative ISP. It's perfect (consistently sub-200ms).
You guys are investigating the packet loss, as I gently chided support, this has been ongoing since late last year.
In any event, the takeaway is that the issue with the game is most assuredly not to do with infrastructure on my end. No biggie, just get it working as well as it usually does.
Thanks!
I'm running backup WA/Afrihost accounts just so I can play League of Legends. It's a little bit annoying because for a while it was running perfectly but the packet loss has been back for a few months, so I decided just to get a few gigs for my games. CW is my download/surfing account, AH/WA are my gaming accounts.
It's your exchange, man. At least that's the excuse they give all of us.![]()
No, we certainly don't. But as previously mentioned it's a catch-22. If we do identify exchange issues we are duty-bound to let you know so that it can be reported to Telkom to fix. It doesn't mean that we absolve ourselves of any responsibility at that point, whatsoever. I even posted earlier just a few before yours that gaming latency is one we're reporting to be investigated and resolved.
I realise that everyone hates to be told that there is a line or exchange fault/congestion, but the reality is that we'd be quite irresponsible if we saw it and ignored it, so we rather inform those who do experience these issues of the problem, we suggest a course of action, and we also don't absolve ourselves in general of anything at that point either, so it's unlikely that I'm going to change this way of doing things on support as I believe it to be the right way. If you can suggest better ways to do this we will always listen and look to be better.
If a CW account drops packets and a backup ISP account does not drop packets then it is my view that it is not an exchange problem. Simple logic, support should know this. I've heard the stories of it's because it's a new connection when you switch to the backup account or whatever, but even with extended testing of the backup account the packet loss does not return. Upon switching back to the CW account (hours later) it is instantly back. Any rational person can see the problem is not my exchange.
Judging by what Zolly and others say, support is doing the exact same thing to them.
A Telkom exchange exists long before our network. We don't have equipment at the exchanges, and we don't purchase capacity at exchanges. Our network starts at data centres for which the Telkom last mile and national network carry the data from your connection to those points. Those points are typically from the third of fourth hop on any trace depending on your network setup. You'll find that all ISPs have to deal with the accusation that somehow the exchange works differently on one account vs another (or one ISP vs another) but the only company who can answer why is Telkom. Just because it works differently on different ISPs does not mean it is the ISP who are to blame when the network itself that you are looking at is not the ISP's network. It also doesn't mean that everything is fine at the exchange - exchanges are huge in size with massive amounts of networking equipment - some may be 100% operational, and some may be experiencing difficulties at times. It's not possible for us to know - we don't own the equipment at the exchanges, and we cannot test that equipment either. Only Telkom can.
So while it is understandable that from a simplistic determination perspective it always appears to be the ISP at fault in this scenario, the reality is that it's not, and one has to contact Telkom to fix exchange related issues, and not the ISP unless the line is managed by the ISP, at which point we liaise with Telkom on your behalf.
Apologies to CW for my angry posts. My frustration levels with South African internet as a whole is just at an all time high.
Sorry![]()