Is DigitalOcean down?
Updates every minute
Two independent answers, side by side: what Infra Agent’s own checks observe from multiple regions, and what DigitalOcean reports on its official status page. We never mix the two.
DigitalOcean looks up right now
Infra Agent's checks are succeeding from all 3 of our regions, and DigitalOcean is not reporting any problems on its official status page.
Infra Agent checks
Independent · our own probes
Our checks are reaching DigitalOcean from all 3 regions.
Last checked 2 minutes ago
DigitalOcean’s official status
Provider-reported · official feed
DigitalOcean reports "All Systems Operational" on its official status page.
Our regional check results
The latest probe from each of our monitoring regions. A provider only counts as having problems when failures repeat across consecutive checks and more than one region.
| Check region | API (api.digitalocean.com) | Control panel (cloud.digitalocean.com) | Main website (www.digitalocean.com) |
|---|---|---|---|
| Amsterdam, NL | 106 ms | 339 ms | 27 ms |
| Ashburn, US (East) | 31 ms | 138 ms | 41 ms |
| San Jose, US (West) | 101 ms | 335 ms | 77 ms |
What we check
- API (api.digitalocean.com)https://api.digitalocean.com/v2/regions
- Control panel (cloud.digitalocean.com)https://cloud.digitalocean.com
- Main website (www.digitalocean.com)https://www.digitalocean.com
Last 24 hours
Response times and failures from Infra Agent’s own checks of DigitalOcean.
Recent DigitalOcean incidents
As reported by DigitalOcean on its official status page.
- MajorAgent Platform Requests Returning HTTP 500 Errorsstarted 1 day ago · resolved about 9 hours ago
- MinorNetwork Connectivity from India to NYCstarted 5 days ago · resolved 4 days ago
- MinorLlama-4-Maverick Model Availabilitystarted 6 days ago · resolved 6 days ago
- MinorGradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17bstarted 6 days ago · resolved 6 days ago
- MinorBlock Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1started 10 days ago · resolved 9 days ago
- MinorNetworking in BLR1started 10 days ago · resolved 10 days ago
DigitalOcean looks down for you? Work through this
DigitalOcean problems are often regional: one datacenter can have networking trouble while the rest of the platform is fine. Narrow it down before assuming a full outage.
Check your Droplet directly by IP
Ping or SSH to your Droplet's public IP address. If the Droplet answers but your site doesn't, the problem is your application or web server, not DigitalOcean. If the IP itself is unreachable from several networks, it's likely DigitalOcean networking in that region.
Use the Recovery Console when SSH fails
If you can log in to cloud.digitalocean.com, open your Droplet and use the Recovery Console. It attaches through DigitalOcean's internal network, so it usually works even when public networking to the Droplet is broken, and it tells you whether the machine itself is healthy.
Match your region against the official components
DigitalOcean's status page reports per-datacenter components (NYC1, AMS3, SFO3, and so on). An incident in a region you don't use won't affect you. Check which region your Droplets and databases live in and compare.
App Platform and Managed Databases fail differently
App Platform sits on top of DigitalOcean's infrastructure with its own build and routing layers, so deployments can fail while existing apps keep serving. Managed Database incidents usually show up as connection timeouts from your app rather than your site being unreachable.
API errors during an incident
Tools like Terraform, doctl, and CI pipelines talk to api.digitalocean.com. If the API is degraded, your running Droplets keep working. You just can't manage them. Pause automation that retries aggressively until the incident clears.
Check your own website
Provider looks fine but your site is down, or the other way around? Test any URL from our servers right now. No account needed.
About DigitalOcean
DigitalOcean is a cloud provider offering Droplets (virtual machines), managed databases, Kubernetes, and App Platform hosting. Problems can be regional, so one datacenter can be affected while others keep running.
Also check: Is Fly.io down? · Is Vercel down? · Is Cloudflare down? · All providers
Infra Agent is an independent monitoring service and is not affiliated with, endorsed by, or sponsored by DigitalOcean. The DigitalOcean name is used for identification only. “Official status” information is republished from DigitalOcean’s public status feed and always links back to the source.
DigitalOcean outage FAQ
Is it my Droplet or DigitalOcean that's down?
Test the Droplet's public IP directly (ping or SSH) from more than one network. Droplet answers but site doesn't: your application. IP unreachable everywhere: likely DigitalOcean networking in that datacenter, so check the region components on their status page. This page's checks test DigitalOcean's API, control panel, and website independently of any single customer's infrastructure.
Do DigitalOcean outages affect all regions at once?
Usually not. Most incidents are scoped to one datacenter (like AMS3 or NYC1) or one product (like App Platform or the API). A global check like ours can look healthy while a single region is having real trouble. That's why we also show DigitalOcean's own per-region reporting next to our results.
Why do your checks and DigitalOcean's status page disagree?
They measure different things. Infra Agent probes DigitalOcean's API, control panel, and website from multiple regions every couple of minutes. DigitalOcean's status page is updated by their team and covers every product and datacenter, including ones we don't probe. Early in an incident our checks may fail first; during a scoped incident theirs may report problems ours can't see.
How often is this DigitalOcean status page updated?
Every monitoring region probes DigitalOcean roughly every 2 minutes, and the official status feed is refreshed on the same schedule. The exact time of the last check and the last successful feed refresh are both shown above.