Live / DigitalOcean / Incident
DigitalOcean: Container Registry and Spaces Accessibility
DigitalOcean · digitalocean.comMinor incidentResolved2026-08-21 14:52 UTC
Public — what happened
Summary
DigitalOcean said that starting at 12:59 UTC on August 21, 2026, customers in some regions could have trouble uploading or downloading container images through its Container Registry, and some saw an error page when trying to open Spaces storage buckets in the Cloud Control Panel. By 13:06 UTC the company said it had found the problem and put a fix in place, though it did not describe the cause. After a period of monitoring, DigitalOcean declared the issue resolved at 14:52 UTC, saying both services were working normally again.
Affected
Global, Global
Timeline
- Started — 2026-08-21 12:59 UTC
- Investigating — 2026-08-21 12:59 UTC
- Monitoring — 2026-08-21 13:06 UTC
- Resolved — 2026-08-21 14:52 UTC · 1h 53m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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