DIGITALOCEAN

🟠 The entire .co TLD decided to play hide-and-seek with DNS resolvers worldwide. DigitalOcean's engineers are frantically applying band-aids to someone else's burning building while pretending they have it under control. (Auto-resolved: no updates in 24h)

⏰ Apr 17, 2026 Fixed (for now) spotted via status_rss

// The official story

DNS Resolution Issues with .co TLD

// Status page says

Apr 17 , 21:22 UTC Identified - Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used. Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will conti

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

https://status.digitalocean.com/incidents/v6qdbpt1dcd3

Digitalocean'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)