Periodic network slowness/drops started 6/7/2021
Dan-J
Newbie

I captured the following on an ssh session from my router to my Verizon FiOS gateway address (below).  It started 2 days ago, and is extreme enough that other clients on my network detect this as a drop, including my VPN link to work, not to mention extreme delays on other network-related functions.  This is new.  I've rebooted all my network gear, the ONT, and did the online troubleshooting which actually broke my connection until I dialed in and the automated system fixed the break, but this issue remains.

What's going on between my ONT and the gateway?

64 bytes from 173.49.xxx.x: seq=4830 ttl=255 time=1.489 ms
64 bytes from 173.49.xxx.x: seq=4831 ttl=255 time=4.331 ms
64 bytes from 173.49.xxx.x: seq=4832 ttl=255 time=4.337 ms
64 bytes from 173.49.xxx.x: seq=4833 ttl=255 time=2.012 ms
64 bytes from 173.49.xxx.x: seq=4834 ttl=255 time=4.924 ms
64 bytes from 173.49.xxx.x: seq=4835 ttl=255 time=18.423 ms
64 bytes from 173.49.xxx.x: seq=4836 ttl=255 time=4.798 ms
64 bytes from 173.49.xxx.x: seq=4837 ttl=255 time=13.770 ms
64 bytes from 173.49.xxx.x: seq=4838 ttl=255 time=6451.687 ms
64 bytes from 173.49.xxx.x: seq=4839 ttl=255 time=10892.586 ms
64 bytes from 173.49.xxx.x: seq=4840 ttl=255 time=11060.952 ms
64 bytes from 173.49.xxx.x: seq=4841 ttl=255 time=10118.823 ms
64 bytes from 173.49.xxx.x: seq=4842 ttl=255 time=9182.167 ms
64 bytes from 173.49.xxx.x: seq=4843 ttl=255 time=8223.750 ms
64 bytes from 173.49.xxx.x: seq=4844 ttl=255 time=7256.980 ms
64 bytes from 173.49.xxx.x: seq=4845 ttl=255 time=6267.829 ms
64 bytes from 173.49.xxx.x: seq=4846 ttl=255 time=5278.922 ms
64 bytes from 173.49.xxx.x: seq=4847 ttl=255 time=4304.474 ms
64 bytes from 173.49.xxx.x: seq=4848 ttl=255 time=3326.055 ms
64 bytes from 173.49.xxx.x: seq=4849 ttl=255 time=2338.177 ms
64 bytes from 173.49.xxx.x: seq=4850 ttl=255 time=1374.414 ms
64 bytes from 173.49.xxx.x: seq=4851 ttl=255 time=417.428 ms
64 bytes from 173.49.xxx.x: seq=4852 ttl=255 time=5.296 ms
64 bytes from 173.49.xxx.x: seq=4853 ttl=255 time=7.647 ms
64 bytes from 173.49.xxx.x: seq=4855 ttl=255 time=18.225 ms
64 bytes from 173.49.xxx.x: seq=4856 ttl=255 time=3.291 ms
64 bytes from 173.49.xxx.x: seq=4857 ttl=255 time=5.339 ms
64 bytes from 173.49.xxx.x: seq=4858 ttl=255 time=3.102 ms
64 bytes from 173.49.xxx.x: seq=4859 ttl=255 time=3.062 ms
64 bytes from 173.49.xxx.x: seq=4860 ttl=255 time=2.438 ms
64 bytes from 173.49.xxx.x: seq=4861 ttl=255 time=2.343 ms

0 Likes
Reply
4 Replies
Dan-J
Newbie

For reference, it just happened again exactly at 2:37 PM EDT.

64 bytes from 173.49.xxx.x: seq=6370 ttl=255 time=3.023 ms
64 bytes from 173.49.xxx.x: seq=6371 ttl=255 time=2.773 ms
64 bytes from 173.49.xxx.x: seq=6372 ttl=255 time=3.085 ms
64 bytes from 173.49.xxx.x: seq=6373 ttl=255 time=11.285 ms
64 bytes from 173.49.xxx.x: seq=6374 ttl=255 time=5.578 ms
64 bytes from 173.49.xxx.x: seq=6375 ttl=255 time=2.014 ms
64 bytes from 173.49.xxx.x: seq=6376 ttl=255 time=23.724 ms
64 bytes from 173.49.xxx.x: seq=6377 ttl=255 time=2.947 ms
64 bytes from 173.49.xxx.x: seq=6378 ttl=255 time=4.437 ms
64 bytes from 173.49.xxx.x: seq=6379 ttl=255 time=17.454 ms
64 bytes from 173.49.xxx.x: seq=6380 ttl=255 time=8972.657 ms
64 bytes from 173.49.xxx.x: seq=6381 ttl=255 time=23081.644 ms
64 bytes from 173.49.xxx.x: seq=6382 ttl=255 time=23592.991 ms
64 bytes from 173.49.xxx.x: seq=6383 ttl=255 time=22610.213 ms
64 bytes from 173.49.xxx.x: seq=6384 ttl=255 time=21630.577 ms
64 bytes from 173.49.xxx.x: seq=6385 ttl=255 time=20637.190 ms
64 bytes from 173.49.xxx.x: seq=6386 ttl=255 time=19655.621 ms
64 bytes from 173.49.xxx.x: seq=6387 ttl=255 time=18665.221 ms
64 bytes from 173.49.xxx.x: seq=6388 ttl=255 time=17666.024 ms
64 bytes from 173.49.xxx.x: seq=6389 ttl=255 time=16667.998 ms
64 bytes from 173.49.xxx.x: seq=6390 ttl=255 time=15666.941 ms
64 bytes from 173.49.xxx.x: seq=6391 ttl=255 time=14669.785 ms
64 bytes from 173.49.xxx.x: seq=6392 ttl=255 time=13670.027 ms
64 bytes from 173.49.xxx.x: seq=6393 ttl=255 time=12672.211 ms
64 bytes from 173.49.xxx.x: seq=6394 ttl=255 time=11671.971 ms
64 bytes from 173.49.xxx.x: seq=6395 ttl=255 time=10668.503 ms
64 bytes from 173.49.xxx.x: seq=6396 ttl=255 time=9673.367 ms
64 bytes from 173.49.xxx.x: seq=6397 ttl=255 time=8673.492 ms
64 bytes from 173.49.xxx.x: seq=6398 ttl=255 time=7675.204 ms
64 bytes from 173.49.xxx.x: seq=6399 ttl=255 time=6676.736 ms
64 bytes from 173.49.xxx.x: seq=6400 ttl=255 time=5688.252 ms
64 bytes from 173.49.xxx.x: seq=6401 ttl=255 time=4688.799 ms
64 bytes from 173.49.xxx.x: seq=6402 ttl=255 time=3691.056 ms
64 bytes from 173.49.xxx.x: seq=6403 ttl=255 time=2697.264 ms
64 bytes from 173.49.xxx.x: seq=6404 ttl=255 time=1698.269 ms
64 bytes from 173.49.xxx.x: seq=6405 ttl=255 time=704.612 ms
64 bytes from 173.49.xxx.x: seq=6406 ttl=255 time=4.367 ms
64 bytes from 173.49.xxx.x: seq=6407 ttl=255 time=4.179 ms
64 bytes from 173.49.xxx.x: seq=6408 ttl=255 time=1.530 ms
64 bytes from 173.49.xxx.x: seq=6409 ttl=255 time=4.774 ms
64 bytes from 173.49.xxx.x: seq=6410 ttl=255 time=9.815 ms
64 bytes from 173.49.xxx.x: seq=6411 ttl=255 time=4.015 ms
64 bytes from 173.49.xxx.x: seq=6412 ttl=255 time=4.803 ms
64 bytes from 173.49.xxx.x: seq=6413 ttl=255 time=4.746 ms
64 bytes from 173.49.xxx.x: seq=6414 ttl=255 time=3.628 ms

0 Likes
Reply
Cang_Household
Community Leader
Community Leader

A ping with more than 10 seconds of latency is just unacceptable. I would recommend you to contact official tech support through Social Media channels and request a line tech, as opposed to a field tech, to check the GPON line from the OLT to your ONT. I believe the fiber line may be damaged and causing signal strength to fluctuate and degrade.

0 Likes
Reply
Dan-J
Newbie

What's the best way to engage?

I also have an interesting correlation.  Here's the times of the last 3 that I captured:

8:37 AM
10:37 AM
12:37 PM
2:15 PM*
2:37 PM

That's got to be something programmed.

Edit - definitely every 2 hours, plus one "extra" one marked with * for some unknown reason.

0 Likes
Reply
Cang_Household
Community Leader
Community Leader

I am only aware that WAN DHCP lease is hourly renewed. Can you check your router's WAN DHCP log to see whether the renewal time coincides with the "slowness?"

0 Likes
Reply