This issue seems to crop up from time to time and it takes days for Verizon to finally get their act together and fix it. Upstate NY Verizon FIOS IPv6 routing seems to be broken. I can get 3-4 hops out into Verizon before it dies. Similar traces off net to my IPv6 prefix just dies in their network and never gets to me. Verizon FIOS frontline support is completely useless to escalate this issue and can't talk to anyone who is not understanding because it's not on the support script. Does anyone have a Verizon/FIOS NOC or know someone VZ NOC/engineering that can look into this. It's been a few days. The last time this happened (for several days) it stayed fix for a while, now it's back. It's like VZ is missing routes... My IPv6 PD 2600:4040:561f:ff::/56 From FIOS to google: traceroute6 to www.google.com (2607:f8b0:4006:80e::2004) from 2600:4040:561f:ff01:20c1:18c9:d440:24ff, 64 hops max, 12 byte packets 1 2600:4040:561f:ff01::1 3.265 ms 4.194 ms 3.578 ms 2 2600:4040:5610::1 10.472 ms 9.278 ms 14.681 ms 3 2600:4000:1:134::14 21.434 ms * 21.067 ms 4 * * * 5 * * * 6 * * * From off net to FIOS; tracing the route to 2600:4040:561F:FF01::1 ... 15 msec 15 msec * 9 * * oak-agg8.cenic.net (2607:F380::118:9A41:231) 48 msec 10 * * * 11 * 2600:807:A0F::A5 115 msec * 12 2600:807:A0F::A5 [AS 701] 115 msec * 68 msec 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * BGP route exists but doesn't complete... Routing entry for 2600:4040:5000::/36 Route count is 1/1, share count 0 Routing paths: 2600:803::15 MPLS label: nolabel Last updated 4d14h ago I can ping the first two hops outside my home network; wondering if anyone else in FIOS land can get to 2600:4040:5610::1 ? Anyone else run into similar issues? Kind of a pain to have this broken, the only way to fix this is to disable IPv6 everywhere on my inside network at home... -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://pgp.inoc.net/rblayzor/