There was just a massive DC region Verizon FiOS backbone routing failure
starting at 6:27pm EST and running for ~11 minutes. All paths were
impacted but some were more loss prone than others.
Here's a loss/latency graph to Google's local anycasted 8.8.8.8 resolver:
[image: image.png]
vs a graph to Cogent:
[image: image.png]
vs one to Azure:
[image: image.png]
MTR graphs show major loss down every path that touches one of Verizon's "
ALTER.NET" named routers.
Really just sending this one in because the footprint was massive. I'm
used to smaller DC-region path failures, but this impacted nearly every
path for nearly every FiOS user in DC and the close-in Virginia and
Maryland suburbs. This was far worse than their usual routing hiccups.
- Cary
starting at 6:27pm EST and running for ~11 minutes. All paths were
impacted but some were more loss prone than others.
Here's a loss/latency graph to Google's local anycasted 8.8.8.8 resolver:
[image: image.png]
vs a graph to Cogent:
[image: image.png]
vs one to Azure:
[image: image.png]
MTR graphs show major loss down every path that touches one of Verizon's "
ALTER.NET" named routers.
Really just sending this one in because the footprint was massive. I'm
used to smaller DC-region path failures, but this impacted nearly every
path for nearly every FiOS user in DC and the close-in Virginia and
Maryland suburbs. This was far worse than their usual routing hiccups.
- Cary
