- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am experencing packet loss between two verizon servers. Will Verizon be able to correct this issue if I post this information here?
Computing statistics for 75 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Leonard.fios-router.home [192.168.1.160] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 0/ 100 = 0% | 2 16ms 0/ 100 = 0% 0/ 100 = 0% L100.WASHDC-VFTTP-127.verizon-gni.net [96.241.32.1] 1/ 100 = 1% | 3 12ms 1/ 100 = 1% 0/ 100 = 0% G1-6-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.221.186] Trace complete
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not think that they would be concerned over a 1% loss.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually this is an example of False Packet loss reporting. These servers are often designed not to respond quickly and sometimes not at all to such requests. Its done to avoid denial of service attacks.
I interesting document about interpreting TRACERT is at
https://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf
It even discusses some of the servers and how they handle such things and why these false reports occur.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1 % is negligible. Unfortunately there is such a thing as acceptable packet loss, and I think it's under 5% but more pointedly I believe under 3% if I remember correctly.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Remember he is specifically tracing to a verizon server that is set to place icmp (pings,tracerts, etc) on a low priority. So it still means nothing.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OP
Please show a traceroute to normal server that goes through these servers. A traceroute server ending at one of these Verizon routers will unusually be meaningless.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I'm not very good at network things. My reason for asking this is that I've been getting a lot of "network spikes" to Blizzard servers after switching to Verizon FIOS. "Network Spikes" according to blizzard are when the client side misses a "turn" and has to catch up to the server. I assume this equates to packet loss somewhere along the connection?
Please enlighten me if I am mistaken.
Below is a Pathping and Tracerout for that original post:
Tracing route to 12.129.202.154 over a maximum of 30 hops 0 homePC.fios-router.home [192.168.1.160] 1 FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 2 L100.WASHDC-VFTTP-127.verizon-gni.net [96.241.32.1] 3 G1-6-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.221.186] 4 * * * Computing statistics for 75 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Leonard.fios-router.home [192.168.1.160] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 0/ 100 = 0% | 2 16ms 0/ 100 = 0% 0/ 100 = 0% L100.WASHDC-VFTTP-127.verizon-gni.net [96.241.32.1] 1/ 100 = 1% | 3 12ms 1/ 100 = 1% 0/ 100 = 0% G1-6-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.221.186] Trace complete. Tracing route to 12.129.202.154 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 2 7 ms 6 ms 5 ms L100.WASHDC-VFTTP-127.verizon-gni.net [96.241.32.1] 3 13 ms 15 ms 14 ms G1-6-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.221.186] 4 * * * Request timed out. 5 9 ms 12 ms 12 ms 0.ae1.BR1.IAD8.ALTER.NET [140.222.229.163] 6 18 ms 22 ms 22 ms 192.205.36.137 7 82 ms 80 ms 76 ms cr82.wshdc.ip.att.net [12.122.135.182] 8 75 ms 84 ms 86 ms cr2.wswdc.ip.att.net [12.122.134.94] 9 77 ms 75 ms 82 ms cr1.cgcil.ip.att.net [12.122.18.21] 10 78 ms 77 ms 80 ms cr2.dvmco.ip.att.net [12.122.31.85] 11 78 ms 82 ms 83 ms cr1.slkut.ip.att.net [12.122.30.25] 12 82 ms 112 ms 148 ms cr2.la2ca.ip.att.net [12.122.30.30] 13 82 ms 76 ms 78 ms gar5.lsrca.ip.att.net [12.122.85.33] 14 77 ms 77 ms 79 ms 12-122-254-230.attens.net [12.122.254.230] 15 78 ms 77 ms 76 ms 206.16.68.50 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is nothing that out of the ordinary with your ping and trace. What is actually happening when you go to their servers?