Vodacom Problems: Slow Throughput, trying to Connect, DNS, High Latency

Status
Not open for further replies.
Worse!!!!!

Wow, I can't believe this!
Speedtests done at 21h30

Vodacom speedtest:

D/L : 2764kbs
U/L : 1157kbs

Speedtest:(Jhb - 50km)

How bad can things get?:eek:
At this speed we will need 12 months rollover.
 
2nd time this week for me in Broadacres/Fourways

Pinging www.iol.co.za [196.30.168.79] with 32 bytes of dat

Reply from 196.30.168.79: bytes=32 time=1935ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1870ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1909ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1891ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1949ms TTL=52
Reply from 196.30.168.79: bytes=32 time=2038ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1851ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1868ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1889ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1929ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1919ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1950ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1899ms TTL=52
Reply from 196.30.168.79: bytes=32 time=2021ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1900ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1959ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1947ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1919ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1860ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1899ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1920ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1948ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1902ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1858ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1878ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1850ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1929ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1979ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1961ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1898ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1901ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1927ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1962ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1957ms TTL=52
Reply from 196.30.168.79: bytes=32 time=1909ms TTL=52

Ping statistics for 196.30.168.79:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1850ms, Maximum = 2038ms, Average = 1919ms
 
Although Basil beats me, I'm not impressed.



No gaming tonite.

Edit: Pinging smtp.vodacom.co.za is quite normal @ around 150ms. So not a tower prob or anything like that.
 
Improvement, but not there yet!

I ran a test at 12h55. This seem to be improving. But this also was the pattern yesterday.
Improvement during the day but all fall down in the evening.

 
Problem not quite resolved as yet

Hi just as a matter of interest.

The speeds are improving but the latency is still double what it was before the recent network problems.



I hope VC will make an announcement when all is resolved as phoning 155 is a lost cause. ( unless you suffer from low blood pressure - in that case you get cured as well):rolleyes:
 
Vodacom, has the crisis in Gauteng been resolved?

I am getting a good ping reading (73ms) but the speeds are far from good.
I am connected on the standard 3.6 but since our crash of last week, the data through-put is much slower than before.

The Vodacom test:
D/L: 3719kbs
U/L: 719 kbs

Must be Telkom:eek:
 
I agree to that finding Basilrsa.

Ever since that incident last week, its been 10x more unstable. And when it is stable, the speeds are iffy at best.
 
Well, I was having a couple of issues as well, very similar to the posts above...

But something else that might be worth mentioning - I got a message yesterday from Vodacom saying that my 3.6 profile is no longer active... I wonder why they decided to stop my free 3.6 profile??? speedtests seem to reflect this, but now I don't actually know whether the results are skewed because of the issues with Vodacom, or because they actually did deactivate the 3.6...

:rolleyes:
 
DNS malfunctioning

I am busy doing web development on 2 servers at Hetzner (JHB). I can see everything via fixed IPs but cannot see certain domains. E.g. myserver.co.za is down but www.mybroadband.co.za is working. Same with Google. www.google.com is not working but www.google.co.za is.

I have checked the domains from the 2 different servers and from Hetzner's side it is working OK.

Diagnosis. Vodacom DNS is not working properly.

VMS
 
wishblade said:
Well, I was having a couple of issues as well, very similar to the posts above...

But something else that might be worth mentioning - I got a message yesterday from Vodacom saying that my 3.6 profile is no longer active... I wonder why they decided to stop my free 3.6 profile??? speedtests seem to reflect this, but now I don't actually know whether the results are skewed because of the issues with Vodacom, or because they actually did deactivate the 3.6...

:rolleyes:
Click to expand...

If you are subscribed to their standard HSDPA offering then how can they turf you off the 3.6 profile.:confused:
The announcement was that all their HSDPA customers would automatically qualify for 3.6 and HSUPA.
Phone them and ask them to check your status.
Good luck on the call to 155 though.:eek:
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X