South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Super duper slow for me here too today in Cape Town city bowl.
Yup slow here as well. I have logged a fault with 155 you should do the same.
I think there's a huge fugging problem on Vodacom's HSDPA network.
It's so.....slow.![]()
Where in Cape Town are you based?
I think there's a huge fugging problem on Vodacom's HSDPA network.
It's so.....slow.
And here's the REALLY funny bit : I updated to the 7.2Mbps firmware for my E220 modem. After I got this horrible performance, I thought it might be my firmware and 'downgraded' to 3.6Mbps firmware again. Argghhhh!!!![]()
Just received a call from data support. They confirmed that there was a problem in the Western Cape that was resolved late last night/early this morning.
I will only be able to test again this evening.
Network Error (tcp_error)
A communication error occurred: ""
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
For assistance, contact your network support team.
>ping 196.207.40.165
Pinging 196.207.40.165 with 32 bytes of data:
Reply from 196.207.40.165: bytes=32 time=382ms TTL=61
Reply from 196.207.40.165: bytes=32 time=114ms TTL=61
Request timed out.
Request timed out.
Ping statistics for 196.207.40.165:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 382ms, Average = 248ms
>ping 196.207.40.165
Pinging 196.207.40.165 with 32 bytes of data:
Request timed out.
Reply from 196.207.40.165: bytes=32 time=109ms TTL=61
Request timed out.
Reply from 196.207.40.165: bytes=32 time=588ms TTL=61
Ping statistics for 196.207.40.165:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 588ms, Average = 348ms