After years of testing in a couple of limited areas of Virginia, along with Waltham MA, it appears that Verizon may finally be starting to roll out IPv6 support to more areas. Over the past couple of weeks on another community site, there have been six reports from users in five Maryland areas near Baltimore that IPv6 is now working for them. In Virginia, reports have come from two users in the Yorktown/Newport News area, as well as Sterling in Northern VA.
Verizon had sent emails to Fios business accounts late last year about IPv6 rolling out this year (an account in MD had received a January date, and an account in NJ had received a February date). Obviously those dates were missed, but there are also reports of new emails being sent (a NY business customer recently received an email with a date in June).
The implementation is done on a per-CO (central office) basis, so it's relatively localized (large cities often have multiple CO's serving them), though they could upgrade multiple nearby CO's at the same time. There does seem to be a pattern of at least one momentary overnight outage in the days leading up to it being enabled. Based on the original emails sent to businesses, it looks like they're starting in Virginia/MD and moving north.
Additionally, areas receiving IPv6 seem to be seeing a fix for the 2-hop ICMP Traceroute issue that's been plaguing the network for a few years. So if you notice your traceroutes returning complete results now, try enabling IPv6 and see if you have it.
I don't believe Verizon routers have IPv6 enabled by default, so if you want to see if you have IPv6 in your area, you'll probably need to enable it in your router's settings first. It's possible that Verizon could enable IPv6 in their routers in the future. A note that some older routers may not perform at full speed with IPv6 enabled because of hardware acceleration that only works for IPv4.
If you don't use a Verizon router, here are links for info on setting up pfSense and Ubiquiti EdgeRouter. If you use something else, the general requirement is to send a DHCPv6 Prefix Delegation request for a /56 prefix. Then allocate /64 prefixes from the /56 received for the local network(s) you have. Using DHCPv6 to get a WAN address is not necessary, Verizon does not provide a separate global WAN IPv6 address. Link-local on the WAN interface is more than sufficient for IPv6 to function. Also make sure to set your firewall to allow IPv6 connections from your local network(s) to the internet.
I've been fortunate enough to be in a test area, so if there are questions, I'll do my best to answer them. I don't use a Verizon router though (just pfSense), so I may not be able to answer router-specific questions.
