CompaniesDigitalOceanIncidents
DigitalOcean: Increased Error Rates in SFO3
Affected components: Networking - SFO3SFO3
Timeline of updates
- investigating
As of 02:53 UTC, our Engineering team is investigating increased error rates impacting multiple services in the SFO3 region. At this point, users with resources in SFO3 may experience errors, timeouts, or delays when creating or managing Droplets, Volumes, Load Balancers, Reserved IPs, Cloud Firewalls, Managed Databases, and Managed Kubernetes clusters through the API or Cloud Control Panel. Some users may also experience connectivity issues with Load Balancers and with newly created or restarted Droplets.
We apologize for the inconvenience and will share an update once we have more information. - 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 managing resources in SFO3. Operations that failed during the incident may need to be retried.
We will post an update as soon as the issue is fully resolved. - monitoring
Our Engineering team has mitigated the issue, and services in the SFO3 region are currently operating normally. The team is continuing to monitor the situation to ensure stability given the scope of the impact.
We will continue monitoring and share another update once the situation is fully resolved. In the meantime, if you encounter any further errors or timeouts, please retry the affected operations. If the issue persists, please submit a ticket through your Cloud Support page so our team can assist you further: https://cloudsupport.digitalocean.com/s/createticket (opens in new tab)
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by DigitalOcean, started 2026-11-19 04:37 UTC, not resolved, 3 update(s); edited after publishing.
- Title
- Increased Error Rates in SFO3
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/bdr1xgf08wsr
DigitalOcean profileRecent DigitalOcean incidentsAll outages on November 19, 2026DigitalOcean in November 2026MarkdownJSON