Frontier (AS5650) – sustained latency/jitter at 184.19.246.62, New Haven / Fort Wayne IN area since Nov 8
Hi all, Seeing sustained latency/jitter inside Frontier (AS5650) affecting a residential fiber circuit in New Haven, IN (Fort Wayne area) since the evening of Sun Nov 8 (~22:00 ET). Still ongoing as of Nov 10. Symptom: 50–300 ms jitter and intermittent loss (game telemetry showed up to 40%) to all destinations. Circuit is idle (<5 Mbps), WAN is 1000baseT full-duplex with no errors, ONT and router power-cycled, and it reproduces with a PC wired directly to the ONT. The fault starts one hop past the local gateway: hop 2 50.104.64.1 (50-104-64-1.prtg.in.frontiernet.net) 10/10, min/avg/max 2/3/6 ms <- clean hop 3 184.19.246.62 10/10, min/avg/max 49/104/204 ms <- jitter starts here, carried through every downstream hop to 1.1.1.1 Traceroute (Nov 9, ~21:23 ET): 1 <1 <1 <1 192.168.89.1 2 112 9 263 50.104.64.1 3 92 9 118 184.19.246.62 4 160 125 78 74.41.143.152 5 148 174 151 45.52.201.97 ... 9 162 16 200 1.1.1.1 Ping from the router itself (no LAN in path): 50.104.64.1 is clean (4.5/6.3/13.6 ms), 1.1.1.1 swings 10–151 ms (stddev 51 ms). Looks like a congested or degraded link/device between the prtg.in gateway and its upstream aggregation. Residential support has no path to network ops (ticket open, FCC complaint filed). Is anyone else on Frontier in the Fort Wayne / northeast Indiana area seeing this? Or if someone from Frontier/Verizon network ops is on the list, an off-list contact would be much appreciated. Thanks, Logan VanVleet -- *Logan VanVleet* Owner, VanVleet Development LLC Custom AV Control Systems | Full-Stack Web Solutions *W:* loganvanvleet.com | *P: 219-775-3625*
participants (1)
-
Logan VanVleet