IPv4 Packet Loss Increase but IPv6 Packet Loss OK
MaxK99
Enthusiast - Level 2

I monitor my FIOS connection from my pfSense router which is connected to the ONT via CAT6 .  The monitor address is a Verizon address that I believe is immediately upstream of my router in the CO (given the ping delay ~3 ms). 

Starting on 2024-01-09, and continuing to today, I have recorded a degradation in IPv4 packet loss.  This can be seen in this graph below.

MaxK99_0-1705243830143.png

The max packet loss was 0.64% on 2024-01-13 at 12:00:00.  As can be seen in the graph above, my average packet loss prior to 2024-01-09 was almost 0.0% but now it is approaching 0.30%

When I overlay the IPv6 packet loss data, we can see there has been no change to IPv6 packet loss.  Max IPv6 packet loss is 0.24% and the average is 0.00%.

MaxK99_1-1705244943334.png

There have been no changes to my local network hardware or software.

What could be causing the packet loss increase on IPv4 but not IPv6?

Thanks.

Labels (1)
0 Likes
Reply
1 Solution
MaxK99
Enthusiast - Level 2

I ran MTR for ~24 hours, at 1 second intervals, behind pfSense to the Verizon address pfSense is monitoring. There was very little packet loss.

The pfSense monitoring has improved also. So, I'm going to assume it was some change on Verizon's side and it has been resolved.

View solution in original post

3 Replies
MaxK99
Enthusiast - Level 2

And it appears to be getting worse.  Max packet loss is now 1.24%

MaxK99_0-1705947115082.png

 

0 Likes
Reply
Cang_Household
Community Leader
Community Leader

Sounds like you are pinging the GWR sitting behind the OLT. Nonetheless, since you are not using a Verizon router, the engineering won't be able to pull the technical logs pertaining to your connection for troubleshooting. The majority of connection logs are stored on the Verizon CPE (Customer Premise Equipment).

MaxK99
Enthusiast - Level 2

I ran MTR for ~24 hours, at 1 second intervals, behind pfSense to the Verizon address pfSense is monitoring. There was very little packet loss.

The pfSense monitoring has improved also. So, I'm going to assume it was some change on Verizon's side and it has been resolved.