Live / Incidents / DigitalOcean
DigitalOcean: Container Registry and Spaces Accessibility
DigitalOcean · digitalocean.comImpact: minorResolved2026-08-21 14:52 UTC
Public — what happened
Summary
Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved.
Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues.
If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.
Timeline
- Started — 2026-08-21 12:59 UTC
- Last update — 2026-08-21 14:52 UTC
- Resolved — 2026-08-21 14:52 UTC
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 →