Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu
dropped packets on fios
tcolden
Enthusiast

I have intermitent dropped packets all the time through fios / alternet backbone routers. is there anything that can be done? 

5 5 ms 6 ms 5 ms 0.so-7-3-0.XT1.LAX7.ALTER.NET [152.63.10.145]
6 6 ms 6 ms 6 ms 0.xe-7-0-0.XL3.LAX1.ALTER.NET [152.63.112.150]
7 7 ms 6 ms 5 ms 0.xe-8-0-0.GW2.LAX1.ALTER.NET [152.63.113.218]
8 244 ms 242 ms 242 ms customer.alter.net.customer.alter.net [152.179.1
3.2]
9 248 ms 247 ms 248 ms te-2-0-0-1-cr01.losangeles.ca.ibone.comcast.net
68.86.82.37]
10 243 ms 244 ms 248 ms pos-0-5-0-0-pe01.600wseventh.ca.ibone.comcast.ne
[68.86.88.194]
11 258 ms 263 ms 264 ms 66.208.228.94
12 250 ms 251 ms 251 ms crr02rvsdca-bue-3.rvsd.ca.charter.com [96.34.1.3
]

ping times also are bad.

Reply from 66.208.228.94: bytes=32 time=73ms TTL=251
Reply from 66.208.228.94: bytes=32 time=141ms TTL=251
Reply from 66.208.228.94: bytes=32 time=172ms TTL=251
Reply from 66.208.228.94: bytes=32 time=192ms TTL=251
Reply from 66.208.228.94: bytes=32 time=187ms TTL=251
Reply from 66.208.228.94: bytes=32 time=170ms TTL=251
Reply from 66.208.228.94: bytes=32 time=165ms TTL=251
Reply from 66.208.228.94: bytes=32 time=159ms TTL=251
Reply from 66.208.228.94: bytes=32 time=154ms TTL=251
Reply from 66.208.228.94: bytes=32 time=174ms TTL=251
Reply from 66.208.228.94: bytes=32 time=193ms TTL=251
Reply from 66.208.228.94: bytes=32 time=200ms TTL=251
Reply from 66.208.228.94: bytes=32 time=15ms TTL=251
Reply from 66.208.228.94: bytes=32 time=22ms TTL=251
Reply from 66.208.228.94: bytes=32 time=17ms TTL=251
Reply from 66.208.228.94: bytes=32 time=13ms TTL=251
Reply from 66.208.228.94: bytes=32 time=21ms TTL=251
Reply from 66.208.228.94: bytes=32 time=16ms TTL=251
Reply from 66.208.228.94: bytes=32 time=23ms TTL=251
Reply from 66.208.228.94: bytes=32 time=19ms TTL=251
Reply from 66.208.228.94: bytes=32 time=15ms TTL=251
Reply from 66.208.228.94: bytes=32 time=21ms TTL=251
Reply from 66.208.228.94: bytes=32 time=18ms TTL=251
Reply from 66.208.228.94: bytes=32 time=12ms TTL=251
Reply from 66.208.228.94: bytes=32 time=21ms TTL=251
Reply from 66.208.228.94: bytes=32 time=15ms TTL=251
Reply from 66.208.228.94: bytes=32 time=12ms TTL=251
Reply from 66.208.228.94: bytes=32 time=18ms TTL=251
Reply from 66.208.228.94: bytes=32 time=15ms TTL=251
Reply from 66.208.228.94: bytes=32 time=20ms TTL=251
Reply from 66.208.228.94: bytes=32 time=15ms TTL=251
Request timed out.
Reply from 66.208.228.94: bytes=32 time=22ms TTL=251
Reply from 66.208.228.94: bytes=32 time=17ms TTL=251
Reply from 66.208.228.94: bytes=32 time=12ms TTL=251
Request timed out.

Ping statistics for 66.208.228.94:
Packets: Sent = 851, Received = 803, Lost = 48 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 294ms, Average = 124ms

0 Likes
Re: dropped packets on fios
Namronorman
Contributor

It's not just you. I see a lot of packet loss throughout the day and especially in the evening - even to networks out of Cogent. Packet loss is awesome for VoIP by the way 🙂

A test from a few minutes ago to a server I rent which is usually fine. Loss was at the Alter.net (verizon owned) hop.

Ping statistics for 108.62.209.x:
Packets: Sent = 667, Received = 649, Lost = 18 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 73ms, Average = 43ms

0 Likes
Re: dropped packets on fios
tcolden
Enthusiast

28% dropped packets. i dont care how fast i am to other sites. i need the speed to be good where ever i browse. 

dropout happens in the altnet backbone routers. Is there anyone at verizon that can look at this? 

Pinging 24.205.2.26 with 32 bytes of data:
Reply from 24.205.2.26: bytes=32 time=58ms TTL=250
Request timed out.
Request timed out.
Reply from 24.205.2.26: bytes=32 time=56ms TTL=250
Reply from 24.205.2.26: bytes=32 time=64ms TTL=250
Request timed out.
Reply from 24.205.2.26: bytes=32 time=49ms TTL=250
Reply from 24.205.2.26: bytes=32 time=62ms TTL=250
Reply from 24.205.2.26: bytes=32 time=60ms TTL=250
Reply from 24.205.2.26: bytes=32 time=57ms TTL=250
Reply from 24.205.2.26: bytes=32 time=49ms TTL=250
Reply from 24.205.2.26: bytes=32 time=61ms TTL=250
Reply from 24.205.2.26: bytes=32 time=61ms TTL=250
Request timed out.
Request timed out.
Reply from 24.205.2.26: bytes=32 time=59ms TTL=250
Request timed out.
Request timed out.
Request timed out.
Reply from 24.205.2.26: bytes=32 time=60ms TTL=250
Reply from 24.205.2.26: bytes=32 time=62ms TTL=250
Reply from 24.205.2.26: bytes=32 time=62ms TTL=250
Reply from 24.205.2.26: bytes=32 time=65ms TTL=250
Reply from 24.205.2.26: bytes=32 time=63ms TTL=250
Reply from 24.205.2.26: bytes=32 time=63ms TTL=250
Reply from 24.205.2.26: bytes=32 time=64ms TTL=250
Reply from 24.205.2.26: bytes=32 time=58ms TTL=250
Reply from 24.205.2.26: bytes=32 time=56ms TTL=250

Ping statistics for 24.205.2.26:
Packets: Sent = 28, Received = 20, Lost = 8 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 65ms, Average = 59ms
Control-C

0 Likes