Bad Vodacom Pings

P

Pilgrim

Wugger
Joined
Jul 5, 2006
Messages
3,100
Reaction score
57
Location
Silligong Valley
Time= 18:52 16-11-2007
Code: 
c:\>ping www.google.com -n 100

Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=962ms TTL=239
Reply from 64.233.183.99: bytes=32 time=542ms TTL=239
Request timed out.
Reply from 64.233.183.99: bytes=32 time=2641ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=640ms TTL=239
Reply from 64.233.183.99: bytes=32 time=559ms TTL=239
Reply from 64.233.183.99: bytes=32 time=554ms TTL=239
Reply from 64.233.183.99: bytes=32 time=644ms TTL=239
Reply from 64.233.183.99: bytes=32 time=550ms TTL=239
Reply from 64.233.183.99: bytes=32 time=527ms TTL=239
Reply from 64.233.183.99: bytes=32 time=583ms TTL=239
Reply from 64.233.183.99: bytes=32 time=560ms TTL=239
Reply from 64.233.183.99: bytes=32 time=538ms TTL=239
Reply from 64.233.183.99: bytes=32 time=1003ms TTL=239
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 64.233.183.99: bytes=32 time=3321ms TTL=239
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=2860ms TTL=239
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 64.233.183.99: bytes=32 time=3290ms TTL=239
Reply from 64.233.183.99: bytes=32 time=1226ms TTL=239
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=1549ms TTL=239
Request timed out.
Reply from 64.233.183.99: bytes=32 time=829ms TTL=239
Reply from 64.233.183.99: bytes=32 time=606ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=2051ms TTL=239
Reply from 64.233.183.99: bytes=32 time=677ms TTL=239
Request timed out.
Reply from 64.233.183.99: bytes=32 time=940ms TTL=239
Reply from 64.233.183.99: bytes=32 time=657ms TTL=239
Reply from 64.233.183.99: bytes=32 time=3345ms TTL=239
Reply from 64.233.183.99: bytes=32 time=737ms TTL=239
Reply from 64.233.183.99: bytes=32 time=2425ms TTL=239
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.
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 64.233.183.99: bytes=32 time=2259ms TTL=239
Reply from 64.233.183.99: bytes=32 time=1400ms TTL=239
Reply from 64.233.183.99: bytes=32 time=638ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.233.183.99:
    Packets: Sent = 100, Received = 30, Lost = 70 (70% loss),
Approximate round trip times in milli-seconds:
    Minimum = 527ms, Maximum = 3345ms, Average = 1303ms


Time= 18:57 16-11-2007
Code: 
c:\>ping www.google.com -n 100

Pinging www.l.google.com [66.249.93.104] with 32 bytes of data:

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.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.93.104: bytes=32 time=789ms TTL=239
Reply from 66.249.93.104: bytes=32 time=870ms TTL=239
Reply from 66.249.93.104: bytes=32 time=879ms TTL=239
Reply from 66.249.93.104: bytes=32 time=541ms TTL=239
Reply from 66.249.93.104: bytes=32 time=597ms TTL=239
Reply from 66.249.93.104: bytes=32 time=555ms TTL=239
Reply from 66.249.93.104: bytes=32 time=894ms TTL=239
Reply from 66.249.93.104: bytes=32 time=550ms TTL=239
Reply from 66.249.93.104: bytes=32 time=988ms TTL=239
Reply from 66.249.93.104: bytes=32 time=545ms TTL=239
Reply from 66.249.93.104: bytes=32 time=549ms TTL=239
Reply from 66.249.93.104: bytes=32 time=556ms TTL=239
Reply from 66.249.93.104: bytes=32 time=544ms TTL=239
Reply from 66.249.93.104: bytes=32 time=541ms TTL=239
Reply from 66.249.93.104: bytes=32 time=894ms TTL=239
Reply from 66.249.93.104: bytes=32 time=558ms TTL=239
Reply from 66.249.93.104: bytes=32 time=1103ms TTL=239
Reply from 66.249.93.104: bytes=32 time=538ms TTL=239
Reply from 66.249.93.104: bytes=32 time=568ms TTL=239
Reply from 66.249.93.104: bytes=32 time=564ms TTL=239
Reply from 66.249.93.104: bytes=32 time=560ms TTL=239
Reply from 66.249.93.104: bytes=32 time=523ms TTL=239
Reply from 66.249.93.104: bytes=32 time=561ms TTL=239
Reply from 66.249.93.104: bytes=32 time=576ms TTL=239
Reply from 66.249.93.104: bytes=32 time=528ms TTL=239
Reply from 66.249.93.104: bytes=32 time=579ms TTL=239
Reply from 66.249.93.104: bytes=32 time=1045ms TTL=239
Request timed out.
Request timed out.
Reply from 66.249.93.104: bytes=32 time=1538ms TTL=239
Reply from 66.249.93.104: bytes=32 time=2298ms TTL=239
Reply from 66.249.93.104: bytes=32 time=677ms TTL=239
Reply from 66.249.93.104: bytes=32 time=1116ms TTL=239
Reply from 66.249.93.104: bytes=32 time=556ms TTL=239
Reply from 66.249.93.104: bytes=32 time=555ms TTL=239
Reply from 66.249.93.104: bytes=32 time=553ms TTL=239
Reply from 66.249.93.104: bytes=32 time=570ms TTL=239
Reply from 66.249.93.104: bytes=32 time=526ms TTL=239
Reply from 66.249.93.104: bytes=32 time=2725ms TTL=239
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.
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.
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.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.249.93.104:
    Packets: Sent = 100, Received = 37, Lost = 63 (63% loss),
Approximate round trip times in milli-seconds:
    Minimum = 523ms, Maximum = 2725ms, Average = 786ms
 
(19:02 16-11-2007)
Code: 
c:>ping www.google.com -n 100

Pinging www.l.google.com [66.249.93.147] with 32 bytes of data:

Reply from 66.249.93.147: bytes=32 time=1048ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1340ms TTL=239
Reply from 66.249.93.147: bytes=32 time=592ms TTL=239
Reply from 66.249.93.147: bytes=32 time=590ms TTL=239
Reply from 66.249.93.147: bytes=32 time=548ms TTL=239
Reply from 66.249.93.147: bytes=32 time=543ms TTL=239
Reply from 66.249.93.147: bytes=32 time=971ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=1712ms TTL=239
Reply from 66.249.93.147: bytes=32 time=676ms TTL=239
Reply from 66.249.93.147: bytes=32 time=515ms TTL=239
Reply from 66.249.93.147: bytes=32 time=3013ms TTL=239
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=1144ms TTL=239
Reply from 66.249.93.147: bytes=32 time=816ms TTL=239
Reply from 66.249.93.147: bytes=32 time=953ms TTL=239
Reply from 66.249.93.147: bytes=32 time=2241ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1098ms TTL=239
Reply from 66.249.93.147: bytes=32 time=797ms TTL=239
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=1912ms TTL=239
Reply from 66.249.93.147: bytes=32 time=3136ms TTL=239
Reply from 66.249.93.147: bytes=32 time=637ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1656ms TTL=239
Reply from 66.249.93.147: bytes=32 time=576ms TTL=239
Reply from 66.249.93.147: bytes=32 time=2094ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1916ms TTL=239
Reply from 66.249.93.147: bytes=32 time=3339ms TTL=239
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 66.249.93.147: bytes=32 time=756ms TTL=239
Reply from 66.249.93.147: bytes=32 time=821ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1020ms TTL=239
Reply from 66.249.93.147: bytes=32 time=668ms TTL=239
Reply from 66.249.93.147: bytes=32 time=530ms TTL=239
Reply from 66.249.93.147: bytes=32 time=527ms TTL=239
Reply from 66.249.93.147: bytes=32 time=542ms TTL=239
Reply from 66.249.93.147: bytes=32 time=531ms TTL=239
Reply from 66.249.93.147: bytes=32 time=558ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1285ms TTL=239
Reply from 66.249.93.147: bytes=32 time=517ms TTL=239
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=671ms TTL=239
Reply from 66.249.93.147: bytes=32 time=746ms TTL=239
Reply from 66.249.93.147: bytes=32 time=624ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=3632ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=1011ms TTL=239
Reply from 66.249.93.147: bytes=32 time=580ms TTL=239
Reply from 66.249.93.147: bytes=32 time=760ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1094ms TTL=239
Reply from 66.249.93.147: bytes=32 time=940ms TTL=239
Reply from 66.249.93.147: bytes=32 time=894ms TTL=239
Reply from 66.249.93.147: bytes=32 time=561ms TTL=239
Reply from 66.249.93.147: bytes=32 time=523ms TTL=239
Reply from 66.249.93.147: bytes=32 time=541ms TTL=239
Reply from 66.249.93.147: bytes=32 time=549ms TTL=239
Reply from 66.249.93.147: bytes=32 time=513ms TTL=239
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=1872ms TTL=239
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 66.249.93.147: bytes=32 time=1111ms TTL=239
Reply from 66.249.93.147: bytes=32 time=1019ms TTL=239
Reply from 66.249.93.147: bytes=32 time=578ms TTL=239
Reply from 66.249.93.147: bytes=32 time=761ms TTL=239
Reply from 66.249.93.147: bytes=32 time=814ms TTL=239
Reply from 66.249.93.147: bytes=32 time=532ms TTL=239
Reply from 66.249.93.147: bytes=32 time=715ms TTL=239
Reply from 66.249.93.147: bytes=32 time=527ms TTL=239
Reply from 66.249.93.147: bytes=32 time=745ms TTL=239
Request timed out.

Ping statistics for 66.249.93.147:
    Packets: Sent = 100, Received = 61, Lost = 39 (39% loss),
Approximate round trip times in milli-seconds:
    Minimum = 513ms, Maximum = 3632ms, Average = 1048ms

(19:08 16-11-2007)

Code: 
c:>ping www.google.com -n 100

Pinging www.l.google.com [209.85.139.9] with 32 bytes of data:

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 209.85.139.9: bytes=32 time=3717ms TTL=234
Reply from 209.85.139.9: bytes=32 time=1559ms TTL=234
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 209.85.139.9: bytes=32 time=1017ms TTL=234
Reply from 209.85.139.9: bytes=32 time=717ms TTL=234
Reply from 209.85.139.9: bytes=32 time=665ms TTL=234
Reply from 209.85.139.9: bytes=32 time=785ms TTL=234
Request timed out.
Reply from 209.85.139.9: bytes=32 time=2977ms TTL=234
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=1117ms TTL=234
Reply from 209.85.139.9: bytes=32 time=968ms TTL=234
Reply from 209.85.139.9: bytes=32 time=867ms TTL=234
Reply from 209.85.139.9: bytes=32 time=2732ms TTL=234
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=3278ms TTL=233
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=3618ms TTL=233
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 209.85.139.9: bytes=32 time=676ms TTL=233
Reply from 209.85.139.9: bytes=32 time=768ms TTL=233
Reply from 209.85.139.9: bytes=32 time=658ms TTL=233
Reply from 209.85.139.9: bytes=32 time=757ms TTL=233
Reply from 209.85.139.9: bytes=32 time=676ms TTL=233
Reply from 209.85.139.9: bytes=32 time=696ms TTL=233
Reply from 209.85.139.9: bytes=32 time=656ms TTL=233
Reply from 209.85.139.9: bytes=32 time=1342ms TTL=233
Reply from 209.85.139.9: bytes=32 time=936ms TTL=233
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=716ms TTL=233
Reply from 209.85.139.9: bytes=32 time=678ms TTL=233
Reply from 209.85.139.9: bytes=32 time=729ms TTL=233
Reply from 209.85.139.9: bytes=32 time=1647ms TTL=233
Reply from 209.85.139.9: bytes=32 time=978ms TTL=233
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=2301ms TTL=233
Reply from 209.85.139.9: bytes=32 time=3230ms TTL=233
Request timed out.
Reply from 209.85.139.9: bytes=32 time=681ms TTL=233
Reply from 209.85.139.9: bytes=32 time=1055ms TTL=233
Reply from 209.85.139.9: bytes=32 time=978ms TTL=233
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=2363ms TTL=233
Reply from 209.85.139.9: bytes=32 time=2678ms TTL=233
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=3403ms TTL=233
Reply from 209.85.139.9: bytes=32 time=1083ms TTL=233
Reply from 209.85.139.9: bytes=32 time=3303ms TTL=233
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=2317ms TTL=233
Request timed out.
Request timed out.
Reply from 209.85.139.9: bytes=32 time=2097ms TTL=233

Ping statistics for 209.85.139.9:
    Packets: Sent = 100, Received = 39, Lost = 61 (61% loss),
Approximate round trip times in milli-seconds:
    Minimum = 656ms, Maximum = 3717ms, Average = 1574ms
 
Summary:

Code: 
Ping statistics for 64.233.183.99:
    Packets: Sent = 100, Received = 30, Lost = 70 (70% loss),
Approximate round trip times in milli-seconds:
    Minimum = 527ms, Maximum = 3345ms, Average = 1303ms


Ping statistics for 66.249.93.104:
    Packets: Sent = 100, Received = 37, Lost = 63 (63% loss),
Approximate round trip times in milli-seconds:
    Minimum = 523ms, Maximum = 2725ms, Average = 786ms


Ping statistics for 66.249.93.147:
    Packets: Sent = 100, Received = 61, Lost = 39 (39% loss),
Approximate round trip times in milli-seconds:
    Minimum = 513ms, Maximum = 3632ms, Average = 1048ms


Ping statistics for 209.85.139.9:
    Packets: Sent = 100, Received = 39, Lost = 61 (61% loss),
Approximate round trip times in milli-seconds:
    Minimum = 656ms, Maximum = 3717ms, Average = 1574ms

Now my question is this: "What is going on with vodacom?"

Nothing has changed my side. What is going on on their side.

Location: Wynberg, Cape Town.
 
Code: 
c:>tracert www.google.com

Tracing route to www.l.google.com [64.233.183.104]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2   428 ms     *        *     10.113.96.2
  3   781 ms     *     1436 ms  10.113.96.2
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   587 ms   579 ms   559 ms  nf-in-f104.google.com [64.233.183.104]

Trace complete.

c:>tracert www.google.com

Tracing route to www.l.google.com [64.233.183.104]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2  1248 ms   460 ms     *     10.113.96.2
  3  2086 ms     *      911 ms  10.113.96.2
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   544 ms   561 ms   579 ms  nf-in-f104.google.com [64.233.183.104]

Trace complete.
 
I have found that pings are intermittent across Vodacom 3G, even when internet performance has been good. Not when I first start using the service, but in the past couple of months definitely.

I have a theory that ICMP traffic is prioritised very low, so a ping is quite likely to be discarded when a given link or router is busy. Vodacom3G, any truth in this?
 
SecretCode said:
I have a theory that ICMP traffic is prioritised very low, so a ping is quite likely to be discarded when a given link or router is busy. Vodacom3G, any truth in this?
Click to expand...
Considering that Vodacom does not shape or prioritize traffic according to port or protocol, the answer is obviously NO there is no truth to your theory, of course one should consider that Telkodemonopolies-SAIX is the upstream bandwidth supplier and can do whatever it wants to limit the competition that Vodacom's HSDPA poses to Telkodemonopolies' ADSL.
 
SecretCode said:
I have found that pings are intermittent across Vodacom 3G, even when internet performance has been good. Not when I first start using the service, but in the past couple of months definitely.

I have a theory that ICMP traffic is prioritised very low, so a ping is quite likely to be discarded when a given link or router is busy. Vodacom3G, any truth in this?
Click to expand...

Yup, quite correct. It's pretty standard practice in IP networks.

/Added/

Just saw ic's post above; To clarify, there is no shaping on the network, but ICMP (as a non-user protocol, i.e. you don't actually do any 'real work' with ICMP) sits at the bottom of the priority stack.

You're obviously right that any upstream provider could shape.
 
Last edited:
(a) Vodacom could make that claim in regard to "application layer" protocols and still overlook icmp ...
in fact (b) it's occurred to me that by design ICMP is not a guaranteed-delivery service ... although this would kind of make its use for diagnositcs a bit futile
(c) Telkom don't provide routing to Vc surely? Just bandwidth. They couldn't interfere with specific packets or protocols. ... Could they?
 
SecretCode said:
(c) Telkom don't provide routing to Vc surely? Just bandwidth. They couldn't interfere with specific packets or protocols. ... Could they?
Click to expand...
Routers exist wherever networks interconnect with one another, so yes Telkodemonopolies-SAIX can interfere as much as it wants to.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X