South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I got about the same last night, but had so many disconnects that I decided to spare myself the frustration and go to bed.
@ zerofocus:
Please provide me with your Neotel service number, name and contact details.
PS. I have requested the above previouls but have had no response - I am unable to assist you if that is the case.
I need to get your Neotel service number to resolve the disconnect issue that you are currently experiencing (your case and a few others are exceptions) - I cannot do that if I do not know those details.
As I understand it the towers in Cape Town hasn't received the fix for the speed degradation issue. My speeds was nice yesterday at 5h but as soon as everyone started coming online I also started experiencing the same speeds as you. I am working from home today and the speeds is still the same. No improvement.B
I was under the impression that I'd see some 'improvements' but the only improvement was that it wasn't disconnecting - and from 40/50kb/s it was doing 20kb/s.
As I understand it the towers in Cape Town hasn't received the fix for the speed degradation issue. My speeds was nice yesterday at 5h but as soon as everyone started coming online I also started experiencing the same speeds as you. I am working from home today and the speeds is still the same. No improvement.
@ clof: May I have your Neotel service number, name and contact details please.
Is anyone else experiencing intermittent timeouts and latency spikes? I first noticed this behaviour in Paulshof. Web pages were not loading properly and download speeds were erratic.
I am currenlty using my Neotel Prime device in the Germiston area and I sometimes get a 'connection reset' error when trying to load web pages. I've also noticed that download speeds jump wildly from 0kB/s to 160kB/s and back again.
I've been running pings for a while now and I've noticed regular timeout responses which are preceeded by an increase in latency (from 400ms to over 3000ms). I could live with this behaviour before, but it's getting worse and is now really annoying.
Edit: This problem was first noticed this morning.