← Back to the carnage
DIGITALOCEAN
🟠 A load balancer node in SFO3 decided to take early retirement, routing traffic to the void and nuking database connectivity. Engineering played hero and fixed it before the incident write-up got too embarrassing. Database appreciates the rescue mission. (Auto-resolved: no updates in 24h)
// The official story
Increased Error Rates in SFO3
// Status page says
Nov 19 , 04:45 UTC Monitoring - Our Engineering team has mitigated the increased error rates impacting multiple services in the SFO3 region and is monitoring the situation. The impact was caused by a network routing issue that disrupted connectivity to one of our core database systems after a load balancer node became unavailable. As of 04:32 UTC, users should no longer experience errors or timeouts when creating or managi
🔗 Official status page (for the PR-approved version)
https://status.digitalocean.com/incidents/bdr1xgf08wsrDigitalocean's Greatest Hits
🟢 DIGITALOCEAN
Oct 03, 2026
⚪ BLR1 region went full Sleeping Beauty from 11:59-13:02 UTC, ghosting Monitoring, App Platform, Databases, Functions, Load Balancers, Spaces, and the control panel. Users got the classic combo of latency, dropped connections, and errors—basically a networking horror movie where the power came back before anyone got to the climax. (Auto-resolved: no updates in 24h)
🟢 DIGITALOCEAN
Sep 16, 2026
🟡 DigitalOcean's support portal decided to ghost users because some third-party vendor flipped the wrong switch. Can't submit tickets, can't get help—basically the digital equivalent of calling 911 and reaching a busy signal. Support team is probably on Slack wondering why their own tools don't work. (Auto-resolved: no updates in 24h)
🟢 DIGITALOCEAN
Sep 09, 2026
🟡 DigitalOcean's Atlanta datacenter found out what happens when you skip the electrician's calls—GPU performance taking a sad nap while redundant power limps along. Your ML models are now running at 'laptop charger plugged into a gas station outlet' speeds. (Auto-resolved: no updates in 24h)
🟢 DIGITALOCEAN
Aug 19, 2026
🔴 DigitalOcean's MKC1 decided to take an unscheduled sabbatical, taking GPU workloads, Serverless Inference, and Kubernetes nodes along for the ride. Engineering is frantically flipping switches and probably refreshing their monitoring dashboards like they're slot machines. (Auto-resolved: no updates in 24h)