← Back to the carnage
LINODE

⚪ A router upgrade went full Shakespearean tragedy in the London data center, turning Object Storage into a 500-error vending machine for 12 minutes. The router got rebooted, dignity was not recovered, and files are back online. (Auto-resolved: no updates in 24h)

⏰ May 29, 2026 Fixed (for now) spotted via status_rss

// The official story

Service Issue - Object Storage

// Status page says

May 29 , 18:23 UTC Resolved - Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors. This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue was mitigated at 10:19 UTC on May 29,

🔗 Official status page (for the PR-approved version)

https://status.linode.com/incidents/ggqhkqmfwpkf

Linode's Greatest Hits

🟢 LINODE 2d ago
⚪ 🔧 Linode's playing catch-up with upstream vendors on a kernel vulnerability. They've got the fix ready, so go ahead and patch before this becomes someone else's problem on your resume. (Auto-resolved: no updates in 24h)
🟢 LINODE Oct 22, 2026
🟡 Linode's investigating whether three critical F5/NGINX exploits hit their infrastructure. Spoiler: The fact they're 'investigating' means the answer was probably yes. F5 dropped patches faster than their security team dropped the ball. (Auto-resolved: no updates in 24h)
🟢 LINODE Oct 21, 2026
🟡 Akamai's investigating recently published PHP remote code execution holes (CVE-2026-109618 & CVE-2026-109619). Quick Deploy apps and parts of the website are currently MIA while they figure out the damage. If you're running vulnerable PHP, congrats on being a walking security audit. (Auto-resolved: no updates in 24h)
🟢 LINODE Oct 20, 2026
🟠 Linode's fancy enterprise Kubernetes is provisioning nodes that look ready but refuse to actually do anything. It's the infrastructure equivalent of a participation trophy—technically achieved, functionally useless. System components ghosting harder than a bad date. (Auto-resolved: no updates in 24h)