Accessibility Resource Center Skip to main content
Get it fast with In-store & curbside pickup or same day delivery.

High packet loss

Reply
Contributor
Contributor
Posts: 3
Registered: ‎02-19-2013

High packet loss

Message 1 of 3
(1,220 Views)

Hi everyone, I've been noticing some very high packet loss recently (my online gaming started to judder to a halt, losing signal and commands, 30ms up to 15k ms latency and total connection loss etc.) I've ran tracerts that appear to show packet loss near verizon addresses as well as some unknown locations ??? with 100% loss.  Also pingtest.net alternated from 7% loss at the lowest end to 26%!!

 

[URL=http://www.pingtest.net][IMG]http://www.pingtest.net/result/77376292.png[/IMG][/URL]

 

This is ridiculous, it started after Nemo and I'm wondering if anyone else in the area has experienced this (or if anyone at verizon knows what's going on here?)

2 REPLIES 2
Platinum Contributor III
Platinum Contributor III
Posts: 5,881
Registered: ‎07-22-2009

Re: High packet loss

Message 2 of 3
(1,193 Views)

where's your game server, and are you wired or wireless when running that test?

 

have you done any traceroutes that you can post? 

Contributor
Contributor
Posts: 3
Registered: ‎02-19-2013

Re: High packet loss

Message 3 of 3
(1,152 Views)

I'm running wireless but it literally only started a few days ago.  I've tried changing channels, releasing ips etc.  the usual stuff and finally just returning the router to default but nothing.  It dropped to 3% loss last night and is back up to 26% at the time of writing.

 

Here are a couple of tracerts, I'm assuming the * are dropped packets or non replies.

 

DSL Reports 

 

Tracing route to www.dslreports.com [209.123.109.175] with TTL of 32:

1 0ms 0ms 0ms Wireless_Broadband_Router.home [192.168.1.1]
2 6ms 8ms 8ms L100.BSTNMA-VFTTP-87.verizon-gni.net [98.118.119.1]
3 9ms * 37ms G0-10-2-6.BSTNMA-LCR-22.verizon-gni.net [130.81.189.186]
4 *  * 8ms ae0-0.BOS-BB-RTR2.verizon-gni.net [130.81.209.94]
5 24ms 20ms 36ms 0.xe-8-0-0.BR3.NYC4.ALTER.NET [152.63.23.241]
6 41ms 41ms 40ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
7 41ms * 40ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8 41ms * 43ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
9 41ms 42ms 43ms ae-2-2.ebr1.Newark1.Level3.net [4.69.132.98]
10 89ms 194ms 45ms ae-11-51.car1.Newark1.Level3.net [4.69.156.5]
11 19ms 21ms 20ms NETCCESS.car1.Newark1.Level3.net [4.26.16.190]
12 22ms 17ms 18ms 0.e3-3.tbr2.mmu.nac.net [209.123.11.77]
13 20ms 20ms * 0.e1-1.tbr2.oct.nac.net [209.123.10.21]
14 17ms 19ms 17ms vlan808.esd1.oct.nac.net [209.123.10.42]
15 18ms 21ms * www.dslreports.com [209.123.109.175]

Traceroute complete.

 

Verizon

 

Tracing route to a23-66-204-79.deploy.akamaitechnologies.com [23.66.204.79] with TTL of 32:

1 1ms 0ms 0ms Wireless_Broadband_Router.home [192.168.1.1]
2 * 12ms 7ms L100.BSTNMA-VFTTP-87.verizon-gni.net [98.118.119.1]
3 6ms 8ms 20ms G0-10-2-6.BSTNMA-LCR-22.verizon-gni.net [130.81.189.186]
4 8ms 6ms 6ms so-5-0-0-0.BOS-BB-RTR2.verizon-gni.net [130.81.151.220]
5 * * * Request timed out.
6 16ms 18ms 16ms 0.xe-4-0-4.XT1.NYC4.ALTER.NET [152.63.10.61]
7 19ms 21ms 19ms TenGigE0-5-4-0.GW8.NYC4.ALTER.NET [152.63.18.206]
8 16ms 14ms * akamai.customer.alter.net [157.130.19.178]
9 14ms 17ms 18ms a23-66-204-79.deploy.akamaitechnologies.com [23.66.204.79]

Traceroute complete.

 

Google

 

Tracing route to ve-in-f106.1e100.net [173.194.75.106] with TTL of 32:

1 0ms 0ms 0ms Wireless_Broadband_Router.home [192.168.1.1]
2 * 8ms * L100.BSTNMA-VFTTP-87.verizon-gni.net [98.118.119.1]
3 6ms 6ms 8ms G0-10-2-5.BSTNMA-LCR-21.verizon-gni.net [130.81.104.50]
4 49ms 22ms 16ms ae0-0.BOS-BB-RTR1.verizon-gni.net [130.81.209.86]
5 13ms 15ms 15ms 0.xe-4-2-0.XL4.NYC1.ALTER.NET [152.63.23.226]
6 15ms 18ms 17ms 0.xe-9-2-0.GW13.NYC1.ALTER.NET [152.63.4.145]
7 88ms 15ms 14ms google-gw.customer.alter.net [157.130.251.62]
8 13ms 15ms 14ms 72.14.239.248
9 15ms 14ms 15ms 209.85.252.250
10 24ms 25ms 27ms 72.14.239.93
11 39ms * 40ms 209.85.243.114
12 38ms * 34ms 216.239.48.159
13 * * * Request timed out.
14 * 37ms 36ms ve-in-f106.1e100.net [173.194.75.106]

Traceroute complete.

 

Finally STWOR.com

 

Tracing route to a23-67-242-19.deploy.akamaitechnologies.com [23.67.242.19] with TTL of 32:

1 0ms 0ms 0ms Wireless_Broadband_Router.home [192.168.1.1]
2 9ms 6ms 8ms L100.BSTNMA-VFTTP-87.verizon-gni.net [98.118.119.1]
3 8ms 7ms 6ms G0-10-2-6.BSTNMA-LCR-22.verizon-gni.net [130.81.189.186]
4 8ms 6ms * ae0-0.BOS-BB-RTR2.verizon-gni.net [130.81.209.94]
5 16ms 14ms 14ms 0.xe-1-1-0.XL4.NYC1.ALTER.NET [152.63.20.117]
6 74ms 34ms * 0.xe-2-0-8.XL4.EWR6.ALTER.NET [152.63.4.73]
7 * 16ms 19ms TenGigE0-5-0-0.GW8.EWR6.ALTER.NET [152.63.21.14]
8 19ms 16ms 20ms a23-67-242-19.deploy.akamaitechnologies.com [23.67.242.19]

Traceroute complete.

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Covid19


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.