dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1090
share rss forum feed

slavaluk

join:2000-01-26
Los Angeles, CA

SUDDENLY High latency an packet loss to gateway

Everything had been fine until about 30 minutes ago. Now getting high latency and packet loss to gateway. Is there a an outage or maintenance going on? Hollywood area...

ping 66.218.33.1 -t

Pinging 66.218.33.1 with 32 bytes of data:
Request timed out.
Reply from 66.218.33.1: bytes=32 time=263ms TTL=63
Reply from 66.218.33.1: bytes=32 time=257ms TTL=63
Reply from 66.218.33.1: bytes=32 time=253ms TTL=63
Reply from 66.218.33.1: bytes=32 time=243ms TTL=63
Reply from 66.218.33.1: bytes=32 time=243ms TTL=63
Reply from 66.218.33.1: bytes=32 time=246ms TTL=63
Request timed out.
Reply from 66.218.33.1: bytes=32 time=249ms TTL=63
Reply from 66.218.33.1: bytes=32 time=244ms TTL=63
Reply from 66.218.33.1: bytes=32 time=262ms TTL=63
Reply from 66.218.33.1: bytes=32 time=251ms TTL=63
Reply from 66.218.33.1: bytes=32 time=256ms TTL=63
Reply from 66.218.33.1: bytes=32 time=239ms TTL=63
Reply from 66.218.33.1: bytes=32 time=246ms TTL=63
Reply from 66.218.33.1: bytes=32 time=250ms TTL=63
Reply from 66.218.33.1: bytes=32 time=241ms TTL=63
Reply from 66.218.33.1: bytes=32 time=258ms TTL=63
Reply from 66.218.33.1: bytes=32 time=260ms TTL=63
Reply from 66.218.33.1: bytes=32 time=255ms TTL=63
Request timed out.

Ping statistics for 66.218.33.1:
Packets: Sent = 21, Received = 18, Lost = 3 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 263ms, Average = 250ms


slavaluk

join:2000-01-26
Los Angeles, CA

I did power cycle both the modem and the router - nothing changed.


slavaluk

join:2000-01-26
Los Angeles, CA
reply to slavaluk

Now bypassed the router - still the same.

Any DSLX techs online?


slavaluk

join:2000-01-26
Los Angeles, CA
reply to slavaluk

Chat support escalated to Tier 2 for a callback within 24 hours.

Hopefully someone here can take a look sooner.

Thanks!


slavaluk

join:2000-01-26
Los Angeles, CA
reply to slavaluk

Thought there was a glimmer of hope there, but it went back to bad pretty quickly:

ping 66.218.33.1 -t

Pinging 66.218.33.1 with 32 bytes of data:
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=35ms TTL=64
Reply from 66.218.33.1: bytes=32 time=119ms TTL=64
Reply from 66.218.33.1: bytes=32 time=190ms TTL=64
Reply from 66.218.33.1: bytes=32 time=216ms TTL=64
Reply from 66.218.33.1: bytes=32 time=208ms TTL=64
Reply from 66.218.33.1: bytes=32 time=201ms TTL=64
Reply from 66.218.33.1: bytes=32 time=191ms TTL=64
Reply from 66.218.33.1: bytes=32 time=206ms TTL=64
Reply from 66.218.33.1: bytes=32 time=198ms TTL=64
Request timed out.
Reply from 66.218.33.1: bytes=32 time=208ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=9ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=12ms TTL=64
Reply from 66.218.33.1: bytes=32 time=9ms TTL=64
Reply from 66.218.33.1: bytes=32 time=12ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=25ms TTL=64
Reply from 66.218.33.1: bytes=32 time=45ms TTL=64
Reply from 66.218.33.1: bytes=32 time=46ms TTL=64
Reply from 66.218.33.1: bytes=32 time=20ms TTL=64
Reply from 66.218.33.1: bytes=32 time=152ms TTL=64
Reply from 66.218.33.1: bytes=32 time=200ms TTL=64
Reply from 66.218.33.1: bytes=32 time=208ms TTL=64
Reply from 66.218.33.1: bytes=32 time=220ms TTL=64
Request timed out.
Request timed out.
Reply from 66.218.33.1: bytes=32 time=232ms TTL=64
Reply from 66.218.33.1: bytes=32 time=224ms TTL=64
Reply from 66.218.33.1: bytes=32 time=242ms TTL=64
Reply from 66.218.33.1: bytes=32 time=216ms TTL=64
Reply from 66.218.33.1: bytes=32 time=231ms TTL=64
Reply from 66.218.33.1: bytes=32 time=231ms TTL=64
Reply from 66.218.33.1: bytes=32 time=216ms TTL=64
Reply from 66.218.33.1: bytes=32 time=227ms TTL=64
Reply from 66.218.33.1: bytes=32 time=209ms TTL=64
Reply from 66.218.33.1: bytes=32 time=203ms TTL=64
Reply from 66.218.33.1: bytes=32 time=233ms TTL=64
Request timed out.
Reply from 66.218.33.1: bytes=32 time=224ms TTL=64
Reply from 66.218.33.1: bytes=32 time=211ms TTL=64
Reply from 66.218.33.1: bytes=32 time=213ms TTL=64
Reply from 66.218.33.1: bytes=32 time=247ms TTL=64
Reply from 66.218.33.1: bytes=32 time=227ms TTL=64
Reply from 66.218.33.1: bytes=32 time=218ms TTL=64
Reply from 66.218.33.1: bytes=32 time=207ms TTL=64
Request timed out.
Reply from 66.218.33.1: bytes=32 time=219ms TTL=64
Reply from 66.218.33.1: bytes=32 time=231ms TTL=64
Reply from 66.218.33.1: bytes=32 time=228ms TTL=64
Reply from 66.218.33.1: bytes=32 time=220ms TTL=64
Request timed out.
Reply from 66.218.33.1: bytes=32 time=213ms TTL=64
Reply from 66.218.33.1: bytes=32 time=220ms TTL=64
Reply from 66.218.33.1: bytes=32 time=225ms TTL=64
Reply from 66.218.33.1: bytes=32 time=252ms TTL=64
Reply from 66.218.33.1: bytes=32 time=217ms TTL=64
Reply from 66.218.33.1: bytes=32 time=216ms TTL=64
Reply from 66.218.33.1: bytes=32 time=207ms TTL=64
Reply from 66.218.33.1: bytes=32 time=225ms TTL=64
Reply from 66.218.33.1: bytes=32 time=217ms TTL=64
Request timed out.
Reply from 66.218.33.1: bytes=32 time=208ms TTL=64
Reply from 66.218.33.1: bytes=32 time=212ms TTL=64
Reply from 66.218.33.1: bytes=32 time=233ms TTL=64
Reply from 66.218.33.1: bytes=32 time=226ms TTL=64
Reply from 66.218.33.1: bytes=32 time=213ms TTL=64
Reply from 66.218.33.1: bytes=32 time=228ms TTL=64
Reply from 66.218.33.1: bytes=32 time=245ms TTL=64
Reply from 66.218.33.1: bytes=32 time=230ms TTL=64
Reply from 66.218.33.1: bytes=32 time=236ms TTL=64
Reply from 66.218.33.1: bytes=32 time=243ms TTL=64
Reply from 66.218.33.1: bytes=32 time=273ms TTL=64
Reply from 66.218.33.1: bytes=32 time=212ms TTL=64
Reply from 66.218.33.1: bytes=32 time=231ms TTL=64
Reply from 66.218.33.1: bytes=32 time=232ms TTL=64
Reply from 66.218.33.1: bytes=32 time=233ms TTL=64
Reply from 66.218.33.1: bytes=32 time=234ms TTL=64
Request timed out.

Ping statistics for 66.218.33.1:
Packets: Sent = 99, Received = 91, Lost = 8 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 273ms, Average = 147ms


slavaluk

join:2000-01-26
Los Angeles, CA
reply to slavaluk

Seems to be resolved now. Knocking on wood...

ping 66.218.33.1 -t

Pinging 66.218.33.1 with 32 bytes of data:
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=7ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64
Reply from 66.218.33.1: bytes=32 time=6ms TTL=64

Ping statistics for 66.218.33.1:
Packets: Sent = 46, Received = 46, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms



dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:27

Hey, sorry I'm just getting to this today; I'm usually not in the office on Fridays. Sent you a PM; take a look when you can.