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, @12:40PM (4 children)
Based on discussions on IRC and my own experiences, the upstream network issue appears to be resolved.
That doesn't mean it will stay that way, but hopefully all is good now.
Would Soylentils please keep their eyes open for reports about this outage.
I'd be very interested to hear what the cause might have been and what other networks were impacted.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 5, Funny) by NPC-131072 on Monday June 24 2019, @01:01PM (3 children)
Route leak [cloudflarestatus.com] affecting CF, AWS and also big league players like SN.
(Score: 2) by inertnet on Monday June 24 2019, @02:21PM (2 children)
That may explain why I got a cloudflare "I'm not a robot" screen, before I could connect to some site through a VPN. Which I didn't get without using the VPN.
(Score: 2, Funny) by NPC-131072 on Monday June 24 2019, @02:37PM (1 child)
I think that'll just be standard DOS countermeasure due to malicious traffic originating from the VPN netblock.
(Score: 3, Touché) by Thexalon on Monday June 24 2019, @11:22PM
As a Linux advocate, I am happy to see any countermeasures to DOS deployed widely!
The only thing that stops a bad guy with a compiler is a good guy with a compiler.