Anyone else seeing this? Since around 1250 UTC -4, FIOS's v6 network is having huge routing issues. Major backbones are unable to route to FIOS's v6 prefixes. Symptom of this is you'll be unable to ping your v6 IPs externally (they may succeed sometimes, but often will fail), and you'll find v6 outbound connections to google.com, YouTube, Apple Music, in fact nearly every major service (primary v6 sites) fail.
It looks like VZ is acknowledging a network issue on their service status, but come on; this happened not even 2 months ago for 36 hours, now it's happening again?
% ping6 cloudflare.com
PING6(56=40+8+8 bytes) 2600:4040:52a2:4b10:605b:9ae1:e8b6:5e60 --> 2606:4700::6810:84e5
16 bytes from 2606:4700::6810:84e5, icmp_seq=0 hlim=58 time=6.869 ms
16 bytes from 2606:4700::6810:84e5, icmp_seq=1 hlim=58 time=11.126 ms
16 bytes from 2606:4700::6810:84e5, icmp_seq=2 hlim=58 time=16.549 ms
16 bytes from 2606:4700::6810:84e5, icmp_seq=3 hlim=58 time=15.904 ms
16 bytes from 2606:4700::6810:84e5, icmp_seq=4 hlim=58 time=5.993 ms
^C
--- cloudflare.com ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 5.993/11.288/16.549/4.395 ms
% ping6 akamai.com
PING6(56=40+8+8 bytes) 2600:4040:52a2:4b10:605b:9ae1:e8b6:5e60 --> 2600:1408:5400:2f::17c3:2589
^C
--- akamai.com ping6 statistics ---
11 packets transmitted, 0 packets received, 100.0% packet loss
% ping6 google.com
PING6(56=40+8+8 bytes) 2600:4040:52a2:4b10:605b:9ae1:e8b6:5e60 --> 2607:f8b0:4002:c06::71
^C
--- google.com ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
ping6 youtube.com
PING6(56=40+8+8 bytes) 2600:4040:52a2:4b10:605b:9ae1:e8b6:5e60 --> 2607:f8b0:4002:c08::be
^C
--- youtube.com ping6 statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
How is this acceptable? These are serious routing issues. Who made an erroneous BGP change?
