Hey Verizon Community,
As the title says, what can I do about packet loss?
I have been having network spike issues in the video game Starcraft II, and Blizzard support told me to run a pathping to their servers (pathping pasted below). Upon doing that, I discovered that in hop 4, also known as G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214], there was 2% packet loss. What can I do about this? Who can I contact to try and get this resolved?
PATHPING TO BLIZZARD SERVERS:
Tracing route to 12.129.202.154 over a maximum of 30 hops
0 Mitch-PC [10.0.0.2]
1 10.0.0.1
2 Wireless_Broadband_Router.home [192.168.1.1]
3 L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
4 G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
5 ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mitch-PC [10.0.0.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
0/ 100 = 0% |
4 11ms 2/ 100 = 2% 2/ 100 = 2% G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
Trace complete.
they won't do anything, they will just tell you it looks to be outside of the verizon network even though its not, 1-4 hops is your router and verizon, even 5 is verizon im having similar issues with bf4 and packet loss.
You need tier II support. Usually the only way to get to them is by calling in a trouble ticket.for your data service.
Actually it means nothing since its in the middle of the tracert. Probably the server supports the ping, but at a very low priority so the packets are being counted as lost. Many servers don't even respond to tracert.
Also 2% is negligible
.
It won't affect your service.
But also they are correct, it's a misinterpretation (handy little how to, on how to interpret your MTR / trace results) of your results. you don't actualy have packet Loss
What I would look at first is your TWO router set up.
If you haven't rebooted BOTH of the routers, I would do that. Most people in your scenario don't bother with their store bought router, they only reboot the Verizon Router, and that isn't neccessarily where your problem is, it could be your other router.
You should do two tests, one behind your second router as you are now. and then one directly connected to the Verizon router as well.
If the problem happens when you direct connect to your FiOS actiontec router, then you can start looking at that, but your trace shows a good round trip MS and no "real" packet loss or latency. the rule of thumb is that if you have packet loss, it continue's, a spike here and there, isn't real packet loss, and if it were, how does the packet become 100% on the next few hops? it's not really possible. packet loss is real loss, and you don't typically get it back.
FWIW, I Can't even trace route to them, through any data center via http://cloudmonitor.ca.com
| Traceroute to 12.129.202.154 (12.129.202.154), 20 hops max | |
| - | CA APM Cloud Monitor Checkpoint |
| 2 | gi0-0-0-0.agr11.alb02.atlas.cogentco.com (38.104.52.57) 1.105 ms |
| 3 | be2141.ccr21.alb02.atlas.cogentco.com (66.28.4.101) 1.224 ms |
| 4 | be2109.mpd22.jfk02.atlas.cogentco.com (154.54.3.137) 4.414 ms |
| 5 | be2151.mpd22.dca01.atlas.cogentco.com (154.54.40.73) 10.690 ms |
| 6 | be2171.ccr42.atl01.atlas.cogentco.com (154.54.31.109) 22.106 ms |
| 7 | be2173.ccr22.iah01.atlas.cogentco.com (154.54.29.118) 35.973 ms |
| 8 | be2066.ccr22.lax01.atlas.cogentco.com (154.54.7.54) 71.422 ms |
| 9 | be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82) 72.067 ms |
| 10 | att.lax05.atlas.cogentco.com (154.54.13.150) 73.368 ms |
| 11 | cr2.la2ca.ip.att.net (12.122.129.234) 73.956 ms |
| 12 | 12.123.132.209 (12.123.132.209) 71.872 ms |
| 13 | 12.122.251.186 (12.122.251.186) 72.675 ms |
| 14 | 206.16.68.50 (206.16.68.50) 72.459 ms |
| 15 | * |
| 16 | * |
| 17 | * |
| 18 | * |
| 19 | * |
| 20 | * |
| Number of hops exceeded | |
Start a new topic or ask questions in the open forum.
