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

Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Reply
MattLenco
Copper Contributor
Copper Contributor
Posts: 9
Registered: ‎02-12-2011

Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 1 of 22
(2,361 Views)

I ping my inside interface of my Verizon router and it get constant pings with RTT of <1ms. I did a tracert to www.verizon.com and www.verizon.net then did a continual ping to the next hop after my router, 71.178.197.1 and it get variability in the RTTs, telling me there is either asynchronous routing or some other reason why pings aren't consistently taking the usual path.

Will somebody take a look at the gateway one  hop up from my router and lower the mtu or find out if the syslog is showing a flapping interface?

 

My router's outside interface IP address picked by DHCP is {edited for privacy}

C:\Users\Me>tracert www.verizon.net

Tracing route to e3002.b.akamaiedge.net [173.223.124.79]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     9 ms     8 ms  L100.WASHDC-VFTTP-115.verizon-gni.net [71.178.197.1]
  3     8 ms     8 ms    10 ms  G0-8-3-2.WASHDC-LCR-22.verizon-gni.net [130.81.49.130]
  4     7 ms     9 ms     9 ms  so-14-0-0-0.RES-BB-RTR2.verizon-gni.net [130.81.22.56]
  5    12 ms    14 ms    15 ms  0.ae2.BR1.IAD8.ALTER.NET [152.63.32.158]
  6    13 ms    12 ms    11 ms  ae-9.r02.asbnva02.us.bb.gin.ntt.net [129.250.8.37]
  7    10 ms    11 ms    11 ms  a173-223-124-79.deploy.akamaitechnologies.com [173.223.124.79]

Trace complete.

C:\Users\Me>tracert www.verizon.com

Tracing route to e2546.g.akamaiedge.net [184.24.186.120]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     9 ms     9 ms  L100.WASHDC-VFTTP-115.verizon-gni.net [71.178.197.1]
  3     9 ms     9 ms     9 ms  P9-2.BSTNMA-LCR-03.verizon-gni.net [130.81.49.128]
  4    11 ms    11 ms    12 ms  so-13-1-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.22.54]
  5    11 ms    12 ms    13 ms  0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
  6    11 ms    11 ms    11 ms  204.255.169.218
  7    10 ms    12 ms    11 ms  a184-24-186-120.deploy.akamaitechnologies.com [184.24.186.120]

Trace complete.

C:\Users\Me>ping 71.178.197.1 -t
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=11ms TTL=126
Reply from 71.178.197.1: bytes=32 time=36ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=11ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=10ms TTL=126
Reply from 71.178.197.1: bytes=32 time=11ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=11ms TTL=126
Reply from 71.178.197.1: bytes=32 time=10ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=11ms TTL=126
----------------------------------------------------
C:\Users\Me>ping 192.168.1.1. -t
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

 

21 REPLIES 21
prisaz
Platinum Contributor III
Platinum Contributor III
Posts: 6,820
Registered: ‎08-23-2008

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 2 of 22
(2,348 Views)

Many routers will choke up and throttle traffic when being constantly hammered by ICMP traffic. Or they will simply start dropping your frames. or packets.

MattLenco
Copper Contributor
Copper Contributor
Posts: 9
Registered: ‎02-12-2011

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 3 of 22
(2,337 Views)

Do you have a AAA account on that router? Did you ssh in, sh log, and look to see if the interfaces i.e., GRE, FE et cetera are going up down? I have had a continual ping running from last night and every packet has returned so nothing has been dropped. Your reply that the the variability in RTT stems from dropped ICMP packets is thin at best, because I get all the packets back, not dropped. Variable icmp echo-reply RTT are a direct relationship to asynchronous routing or alternative paths used because the original path traverses a flapping interface(s). So going back to my original question, hopefully answered by someone else. Is the router syslog showing any flapping or similar problem that needs to be addressed?

MattLenco
Copper Contributor
Copper Contributor
Posts: 9
Registered: ‎02-12-2011

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 4 of 22
(2,336 Views)

the problem gets even worse at times...

 

Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=51ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=8ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=10ms TTL=126
Reply from 71.178.197.1: bytes=32 time=30ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=46ms TTL=126
Reply from 71.178.197.1: bytes=32 time=9ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=7ms TTL=126
Reply from 71.178.197.1: bytes=32 time=10ms TTL=126

prisaz
Platinum Contributor III
Platinum Contributor III
Posts: 6,820
Registered: ‎08-23-2008

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 5 of 22
(2,332 Views)

 


@MattLenco wrote:

Do you have a AAA account on that router? Did you ssh in, sh log, and look to see if the interfaces i.e., GRE, FE et cetera are going up down? I have had a continual ping running from last night and every packet has returned so nothing has been dropped. Your reply that the the variability in RTT stems from dropped ICMP packets is thin at best, because I get all the packets back, not dropped. Variable icmp echo-reply RTT are a direct relationship to asynchronous routing or alternative paths used because the original path traverses a flapping interface(s). So going back to my original question, hopefully answered by someone else. Is the router syslog showing any flapping or similar problem that needs to be addressed?


Ok. I was just saying if you were sending a continuos ICMP traffic to my router, I would cut you off. There is enough unnessasary traffic. Now in regards to a few ms in latency, I think there would be nothing to be done for changes between 5ms-46ms. But perhaps I am misuunderstanding your issue and will let someone more intelegent than myself answer your question.

 

Anti-Phish
Gold Contributor III
Gold Contributor III
Posts: 1,122
Registered: ‎12-04-2009

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 6 of 22
(2,330 Views)

@MattLenco wrote:

I ping my inside interface of my Verizon router and it get constant pings with RTT of <1ms.

then did a continual ping to the next hop after my router, 71.178.197.1 and it get variability in the RTTs, telling me there is either asynchronous routing or some other reason why pings aren't consistently taking the usual path.


In addition to what prisaz said, keep in mind that the fiber from your ONT to the OLT in the CO is shared.

 

If you're on GPON, then the 2.4/1.2 Gbps fiber bandwidth is shared by upto 32 users.  That's an average bandwidth available per user of 80/40, so FIOS is not oversubscribed like cable.  However, that does not mean you don't have latency.  The OLT can only transmit one frame to one user at a time.  If the OLT is busy transmitting a frame to one user, your frame gets queued, increasing latency.  Also, the interval at which frames to you are transmitted is determined by your speed tier also adding to latency.  Likewise, on upload, each ONT is given a window in which it can transmit.  If the ONT has a frame to send, it must wait for it's transmit window, again adding to latency.  So 8ms +/- 1ms is not unreasonable.

 

MattLenco
Copper Contributor
Copper Contributor
Posts: 9
Registered: ‎02-12-2011

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 7 of 22
(2,291 Views)

32 residential customers, checking email, pinging a gateway, surfing the web, saturating a 2.4Gb/s aggregate and so frequently to create multi periods during the day of latencies up to 50ms, though just ~10 miles from a CO? How about publishing some interface statistics from some of the upstream interfaces to qualify what you are claiming? It's funny how latency never gets packaged in the SLA though bandwidths are guaranteed. Though it is easy to snow a residential customer or a CIO, maybe it should be included in future SLA?

prisaz
Platinum Contributor III
Platinum Contributor III
Posts: 6,820
Registered: ‎08-23-2008

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 8 of 22
(2,285 Views)

Funny I recall no SLAs for residential or any other FiOS customer for that matter. I do recall seeing plenty references for up to xxx speed.

 

although not perfict, but Wiki does explain PON (Passive Optical Networking.

http://en.wikipedia.org/wiki/Verizon_FiOS

 

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

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 9 of 22
(2,268 Views)

just an FYI for the OP 

 

These are peer to peer forums,  VZ Workers may poke their heads in from time to time, but these are not actively monitored by actual vz tech's, especially ones with access to their head end routers.   

 

So your questions are probably meant moreso for actual NOC technicians,  If you're issue doesn't require immediate intervention then you may want to reach out to the Verizon Direct forum  or for immediate assistance you should open a chat link, or call verizon at 1-800 VERIZON

 

 

MattLenco
Copper Contributor
Copper Contributor
Posts: 9
Registered: ‎02-12-2011

Re: Variability in Pings to Next Hop Gateway in Tracert to www.verizon.net

Message 10 of 22
(2,220 Views)

SLA stands for service level agreement which all customers enter into when they subscribe to service. I wouldn't stop at the wiki as your final authoritative source.

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.
Have a spare Fios-G1100?Learn how to bridge it into your network
Get Started


Covid19

Browse Categories
Categories:
Posts

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