High Latency on Cable

Forums › Vodafone New Zealand › High Latency on Cable

Chrizvi

295 posts

Ultimate Geek

# 177916 19-Aug-2015 09:13

can you please advise if it is just me having high latency pinging voda cable dns.
here's sample
Reply from 203.97.78.43: bytes=32 time=107ms TTL=60
Reply from 203.97.78.43: bytes=32 time=89ms TTL=60
Reply from 203.97.78.43: bytes=32 time=330ms TTL=60
Reply from 203.97.78.43: bytes=32 time=101ms TTL=60
Reply from 203.97.78.43: bytes=32 time=80ms TTL=60
Reply from 203.97.78.43: bytes=32 time=51ms TTL=60
Reply from 203.97.78.43: bytes=32 time=98ms TTL=60
Reply from 203.97.78.43: bytes=32 time=141ms TTL=60
Reply from 203.97.78.43: bytes=32 time=53ms TTL=60
Reply from 203.97.78.43: bytes=32 time=378ms TTL=60
Reply from 203.97.78.43: bytes=32 time=182ms TTL=60
Reply from 203.97.78.43: bytes=32 time=59ms TTL=60
Reply from 203.97.78.43: bytes=32 time=38ms TTL=60
Reply from 203.97.78.43: bytes=32 time=67ms TTL=60
Reply from 203.97.78.43: bytes=32 time=1481ms TTL=60
Reply from 203.97.78.43: bytes=32 time=40ms TTL=60
Reply from 203.97.78.43: bytes=32 time=47ms TTL=60

I've checked status on voda site and there was issue from yesterday but not today..
I connected directly on modem and via ethernet..

johnr

19282 posts

Uber Geek
Inactive user

# 1369057 19-Aug-2015 09:19

Would help to add approx what location you are in

Chrizvi

295 posts

Ultimate Geek

# 1369065 19-Aug-2015 09:28

oppss sorry, location is Brooklyn Wellington.
getting worst atm.

Reply from 203.97.78.43: bytes=32 time=2140ms TTL=60
Reply from 203.97.78.43: bytes=32 time=2076ms TTL=60
Request timed out.
Request timed out.
Reply from 203.97.78.43: bytes=32 time=3904ms TTL=60
Request timed out.
Reply from 203.97.78.43: bytes=32 time=1425ms TTL=60
Reply from 203.97.78.43: bytes=32 time=518ms TTL=60
Reply from 203.97.78.43: bytes=32 time=21ms TTL=60
Request timed out.
Request timed out.
Reply from 203.97.78.43: bytes=32 time=2586ms TTL=60
Reply from 203.97.78.43: bytes=32 time=2454ms TTL=60
Reply from 203.97.78.43: bytes=32 time=1290ms TTL=60
Reply from 203.97.78.43: bytes=32 time=424ms TTL=60
Reply from 203.97.78.43: bytes=32 time=1096ms TTL=60
Request timed out.
Reply from 203.97.78.43: bytes=32 time=3506ms TTL=60
Reply from 203.97.78.43: bytes=32 time=2925ms TTL=60
Reply from 203.97.78.43: bytes=32 time=2095ms TTL=60
Reply from 203.97.78.43: bytes=32 time=1393ms TTL=60

Chrizvi

295 posts

Ultimate Geek

# 1369070 19-Aug-2015 09:33

and seems to be better now..

Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=28ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=18ms TTL=60
Reply from 203.97.78.43: bytes=32 time=20ms TTL=60
Reply from 203.97.78.43: bytes=32 time=19ms TTL=60
Reply from 203.97.78.43: bytes=32 time=18ms TTL=60
Reply from 203.97.78.43: bytes=32 time=18ms TTL=60
Reply from 203.97.78.43: bytes=32 time=18ms TTL=60