Live  /  DigitalOcean  /  Incident

DigitalOcean: Account Registration, Droplets, and Related Services

DigitalOcean · digitalocean.comMinor incidentResolved2026-08-09 01:01 UTC
Public — what happened

Summary

DigitalOcean said that starting at 18:57 UTC on August 8, 2026, customers in multiple regions had trouble signing up for new accounts, creating Droplets (virtual servers), reserving IP addresses, and running backups and snapshots, with autoscaling and Kubernetes cluster operations also hit. As the investigation went on, the company added that its GenAI services, the Droplet console, and new database clusters were affected too. DigitalOcean reported finding the root cause at 20:02 UTC but did not describe it publicly, and it said a fix was in place by 00:31 UTC on August 9. The company declared the incident fully resolved at 01:01 UTC.

Affected

Global, Global, Global, Reserved IP

As listed on DigitalOcean’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the DigitalOcean report →

More from DigitalOcean

The full archive is on the DigitalOcean status & history page.

Related: DigitalOcean status & history. SquidGrid is not affiliated with DigitalOcean.