Also, Linode is planning some server reboots over the next week or so. We will try to give advance notice and keep downtime to a minimum.
Update: Everything seems to have quieted down. Many many thanks to NotSanguine for jumping in and lending his expertise to help identify and isolate where things were borked.
Indications are that a bad BGP (Border Gateway Protocol) route was published causing a relatively small AS (Autonomous System) to have all traffic to/from a large fraction of the internet attempt to go through its routers.
(Score: 2) by NotSanguine on Monday June 24 2019, @01:11PM (1 child)
It's possible that Verizon was the source of the issue.
However, it's quite possible it wasn't.
Just because your traceroute died at a Verizon router, that doesn't mean it was Verizon. It's just (more?) as likely, that the route leak (as reported here https://www.cloudflarestatus.com/incidents/46z55mdhg0t5) [cloudflarestatus.com] gave Verizon incorrect routing information and it flung your data the wrong way.
Since this has affected a lot of folks and a some of the big boys, we'll likely get some details in the press over the next day or so.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by pkrasimirov on Monday June 24 2019, @01:20PM
> Verizon was falling on it's face
Perhaps yes.
> Verizon was the source of the issue
Not necessarily.
It is possible to filter out bogus BGP announcements (if that was the problem cause). For example Google was working just fine.