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

[AirWolf]

Internet apn died here too last night around 10:00pm for a while. Reconnected after a few 619 errors.

 

[vodacom3g]

DNS resolution issues again last night between 9 & 10PM. PPDB, unrestricted APN.

Can you send me a detailed mail to my VC addy with as much detail on these DNS issues you see?

I'll join you up with the relevant guys in the Cape, they can then trace or do something with you to catch this one.

 

[morkhans]

Can you send me a detailed mail to my VC addy with as much detail on these DNS issues you see?

I'll join you up with the relevant guys in the Cape, they can then trace or do something with you to catch this one.

Will do. I have got a case with the helpdesk and I have passed some info on to the techie I was speaking to last via email.

 

[morkhans]

Can you send me a detailed mail to my VC addy with as much detail on these DNS issues you see?

I'll join you up with the relevant guys in the Cape, they can then trace or do something with you to catch this one.

You have mail!

 

[ginggs]

Tried several times to connect on pre-paid now, tried both internet and internetvpn APNs, every time I would get an IP but have no connectivity, unable to even ping the DNS servers.
Posting this on MTN.

 

[Iam3G]

I'm struggling too. Can connect to 3G, but no throughput. It dies and comes back. From about 7:30pm. On the internetvpn APN.

 

[ginggs]

Tried again now, got IP address, can ping DNS server but can't resolve any names. Will fire off that mail.
Posting on MTN.

 

[pagel]

Oude Westhof, Bellville, CT. Unreliable and slow connection (prepaid with E620 in 3G Router). I have mentioned this a number of times to Vodacom3G, have contacted customer support, but not getting better. Each time that I want to access the internet and it actually works I am relieved!!! Should simply unlock my data card and try MTN I guess.

If you require a reliable internet connection, this is not it. If you can just as well download mail tomorrow too, Vodacom is good enough.
Regards
Willem

 

[Bedford]

Well at about 10:45pm my connection went awol:

Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=471ms TTL=237
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=459ms TTL=237
Reply from 74.125.39.147: bytes=32 time=469ms TTL=237
Reply from 74.125.39.147: bytes=32 time=458ms TTL=237
Reply from 74.125.39.147: bytes=32 time=458ms TTL=237
Reply from 74.125.39.147: bytes=32 time=457ms TTL=237
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=503ms TTL=237
Reply from 74.125.39.147: bytes=32 time=484ms TTL=237
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=472ms TTL=237
Reply from 74.125.39.147: bytes=32 time=471ms TTL=237
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=477ms TTL=237
Reply from 74.125.39.147: bytes=32 time=457ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=464ms TTL=237
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Reply from 74.125.39.147: bytes=32 time=473ms TTL=237
Reply from 74.125.39.147: bytes=32 time=460ms TTL=237
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Reply from 74.125.39.147: bytes=32 time=492ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Reply from 74.125.39.147: bytes=32 time=491ms TTL=237
Reply from 74.125.39.147: bytes=32 time=460ms TTL=237
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=476ms TTL=237
Reply from 74.125.39.147: bytes=32 time=513ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=463ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=474ms TTL=237
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=462ms TTL=237
Reply from 74.125.39.147: bytes=32 time=472ms TTL=237
Reply from 74.125.39.147: bytes=32 time=482ms TTL=237
Reply from 74.125.39.147: bytes=32 time=481ms TTL=237
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Reply from 74.125.39.147: bytes=32 time=476ms TTL=237
Reply from 74.125.39.147: bytes=32 time=467ms TTL=237
Reply from 74.125.39.147: bytes=32 time=463ms TTL=237
Request timed out.
Reply from 74.125.39.147: bytes=32 time=483ms TTL=237
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.39.147: bytes=32 time=461ms TTL=237
Reply from 74.125.39.147: bytes=32 time=500ms TTL=237
Reply from 74.125.39.147: bytes=32 time=458ms TTL=237
Reply from 74.125.39.147: bytes=32 time=476ms TTL=237
Reply from 74.125.39.147: bytes=32 time=455ms TTL=237
Reply from 74.125.39.147: bytes=32 time=453ms TTL=237
Request timed out.
Request timed out.

any1 else having this constant intermittent drop?

 

[AirWolf]

any1 else having this constant intermittent drop?

Mine also lost connectivity around 10:45pm, but I didn't bother to do any further investigations as I go to bed at 11pm anyway.

 

[morkhans]

Yup was seeing the same issues last night. Started with intermittent DNS resolution errors to zero throughput. Was also seeing packet loss when pinging on IP. Things started going wrong at 19:29 and I gave up at 21:21. Throughout all that I remained connected.

 

[MainMeat]

Same here last night (Pretoria East) from about 22:45 to 23:30. Get IP Address, but no DNS resolving or any internet access for that matter. This was ongoing throughout yesterday, and mostly the afternoon and last night. I am using PPDB, and the internet and unrestricted APNs.

 

[ginggs]

Things going wrong this morning for me, from around 07:00 to 09:00. Could connect no problem, but pings and name resolution were erratic.

 

[MrOoze]

Yeah, problems last night in Newlands.

Packet loss started slowly at 19:00 and degraded to no throughput around 19:45.

Am on prepaid. Swapped to my MTN sim and all was well.

 

[jenn]

Been having the same issues the last 4 or 5 days (in Prince Albert). I stay connected but 0kb in and out for extended periods of time, then my latency is fine for a few minutes before going belly up again. Trying to game with this is hopeless. GG vodacom :*(

 

[ginggs]

I've been getting quite a few of the following error messages while browsing today:

Network Error (tcp_error)

A communication error occurred: "Operation timed out"
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.

I don't recall seeing this message before, so I don't think it is coming from Firefox. I'm seeing it every time I try to go to slashdot.org and sourceforge.net, and intermittently when trying to go to other sites.
Anyone else seeing this?

Also had DNS issues at around 14:45, but they cleared up without me having to reconnect.

 

[jenn]

LoL I just got this too while I was waiting for this page to load. Not really very funny :/ The fact that it made me lol proves that I'm South African I guess, laughing at bad(understatement?) service levels :/

I've been getting quite a few of the following error messages while browsing today:

I don't recall seeing this message before, so I don't think it is coming from Firefox. I'm seeing it every time I try to go to slashdot.org and sourceforge.net, and intermittently when trying to go to other sites.
Anyone else seeing this?

Also had DNS issues at around 14:45, but they cleared up without me having to reconnect.

Edit: Connection was reset while posting this >.<

 

[morkhans]

Been having the same issues the last 4 or 5 days (in Prince Albert). I stay connected but 0kb in and out for extended periods of time, then my latency is fine for a few minutes before going belly up again. Trying to game with this is hopeless. GG vodacom :*(

Have you logged a fault by calling 155 from a Vodacom number?

 

[evolution]

very slow

Anybody else experiencing very slow speeds tonight?! geez several sites and i can barely get 10kb/s on HSDPA eek.

 

[kingrob]

Yep, there is definitely a problem with international web sites, local sites performs ok.

I'm also experimenting with the 'pipelining' feature in Firefox 3, so not sure if it's causing problems when loading web pages.