Vodacom and Nashua Mobile

Sparky_za

Expert Member
Joined
May 30, 2005
Messages
1,179
Reaction score
31
Location
Cape Town
My supposedly stable and high speed connection supplied by Nashua Mobile - Nothing but a rant thread because I get no joy trying to report this to either NM or Voda...

And this is not a once off thing, this is what I get every single day without fail between 15:00 and 21:00

>ping www.google.co.za -t

Pinging www.l.google.com [165.165.38.147] with 32 bytes of data:
Reply from 165.165.38.147: bytes=32 time=1013ms TTL=55
Reply from 165.165.38.147: bytes=32 time=998ms TTL=55
Reply from 165.165.38.147: bytes=32 time=975ms TTL=55
Reply from 165.165.38.147: bytes=32 time=986ms TTL=55
Reply from 165.165.38.147: bytes=32 time=988ms TTL=55
Reply from 165.165.38.147: bytes=32 time=990ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1002ms TTL=55
Reply from 165.165.38.147: bytes=32 time=996ms TTL=55
Reply from 165.165.38.147: bytes=32 time=989ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1409ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1218ms TTL=55
Reply from 165.165.38.147: bytes=32 time=678ms TTL=55
Reply from 165.165.38.147: bytes=32 time=210ms TTL=55
Reply from 165.165.38.147: bytes=32 time=371ms TTL=55
Reply from 165.165.38.147: bytes=32 time=358ms TTL=55
Reply from 165.165.38.147: bytes=32 time=343ms TTL=55
Reply from 165.165.38.147: bytes=32 time=340ms TTL=55
Reply from 165.165.38.147: bytes=32 time=341ms TTL=55
Reply from 165.165.38.147: bytes=32 time=2338ms TTL=55
Reply from 165.165.38.147: bytes=32 time=998ms TTL=55
Reply from 165.165.38.147: bytes=32 time=984ms TTL=55
Reply from 165.165.38.147: bytes=32 time=979ms TTL=55
Reply from 165.165.38.147: bytes=32 time=971ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1983ms TTL=55
Reply from 165.165.38.147: bytes=32 time=3000ms TTL=55
Reply from 165.165.38.147: bytes=32 time=2008ms TTL=55
Request timed out.
Reply from 165.165.38.147: bytes=32 time=59ms TTL=55
Reply from 165.165.38.147: bytes=32 time=2230ms TTL=55
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 165.165.38.147: bytes=32 time=376ms TTL=55
Reply from 165.165.38.147: bytes=32 time=398ms TTL=55
Reply from 165.165.38.147: bytes=32 time=389ms TTL=55
Reply from 165.165.38.147: bytes=32 time=375ms TTL=55
Reply from 165.165.38.147: bytes=32 time=361ms TTL=55
Reply from 165.165.38.147: bytes=32 time=363ms TTL=55
Reply from 165.165.38.147: bytes=32 time=375ms TTL=55
Reply from 165.165.38.147: bytes=32 time=360ms TTL=55
Reply from 165.165.38.147: bytes=32 time=366ms TTL=55
Reply from 165.165.38.147: bytes=32 time=398ms TTL=55
Request timed out.
Reply from 165.165.38.147: bytes=32 time=1424ms TTL=55
Reply from 165.165.38.147: bytes=32 time=997ms TTL=55
Reply from 165.165.38.147: bytes=32 time=991ms TTL=55
Request timed out.
Reply from 165.165.38.147: bytes=32 time=1452ms TTL=55
Reply from 165.165.38.147: bytes=32 time=997ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1007ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1177ms TTL=55
Reply from 165.165.38.147: bytes=32 time=2819ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 165.165.38.147: bytes=32 time=2488ms TTL=55
Reply from 165.165.38.147: bytes=32 time=2349ms TTL=55
Reply from 165.165.38.147: bytes=32 time=58ms TTL=55
Reply from 165.165.38.147: bytes=32 time=1637ms TTL=55
Reply from 165.165.38.147: bytes=32 time=3008ms TTL=55
 
Did you receive any ref numbers when you reported it?
 
Did you receive any ref numbers when you reported it?

I have logged 3 previous calls with Nashua. Each time they are closed saying NM cannot assist as its a network issue. When trying to log a call with VC I am told thats not possible and I need to log it with my SP.

I'm quite happy to try and log another call, but whats the point when each time I am told the same thing?

Usually the issue only happens in the evenings, but today its going on all the time.

Request timed out.
Request timed out.
Request timed out.
Reply from 165.165.38.19: bytes=32 time=396ms TTL=55
Reply from 165.165.38.19: bytes=32 time=404ms TTL=55
Reply from 165.165.38.19: bytes=32 time=412ms TTL=55
Reply from 165.165.38.19: bytes=32 time=1440ms TTL=55
Reply from 165.165.38.19: bytes=32 time=1057ms TTL=55
Reply from 165.165.38.19: bytes=32 time=2000ms TTL=55
Reply from 165.165.38.19: bytes=32 time=1897ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Top
Sign up to the MyBroadband newsletter
X