Skip to main content
DigitalOcean logo

Is DigitalOcean Down?

No — DigitalOcean is up

Reachable from all 8 checked regions

Average response time: 38ms

Last checked · checks run every 6 hours

Official status page: https://status.digitalocean.com

DigitalOcean uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
40ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 28 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 24 checks
Aug 5: 100.00% uptime, 28 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 40 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 40 checks
Jul 20 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg
27ms
DNS 0ms TCP 1ms TLS 6ms TTFB 19ms
dfw
54ms
DNS 0ms TCP 2ms TLS 13ms TTFB 45ms
ewr
30ms
DNS 0ms TCP 1ms TLS 7ms TTFB 21ms
fra
35ms
DNS 0ms TCP 1ms TLS 8ms TTFB 27ms
gru
45ms
DNS 0ms TCP 3ms TLS 9ms TTFB 28ms
iad
45ms
DNS 0ms TCP 10ms TLS 10ms TTFB 37ms
jnb
25ms
DNS 0ms TCP 0ms TLS 6ms TTFB 19ms
lax
33ms
DNS 0ms TCP 1ms TLS 6ms TTFB 26ms
lhr
38ms
DNS 0ms TCP 1ms TLS 7ms TTFB 28ms

What DigitalOcean does

DigitalOcean is a cloud provider offering virtual servers, managed databases, Kubernetes and object storage, aimed at smaller teams than the large hyperscalers. Many products run their whole production estate inside a single DigitalOcean region, which turns a regional incident there into a full outage rather than the partial capacity loss a multi-region deployment would see.

What an outage looks like

Droplets stop answering over SSH and the applications on them go quiet, or they keep serving traffic while the control panel refuses to load. App Platform deployments hang mid-build. Spaces returns errors on uploads and downloads, and assets served through Spaces CDN fail while the origin application is healthy. Managed database connections time out.

What to do about it

Check status.digitalocean.com, which reports per datacenter region (New York, Amsterdam, Frankfurt, London, San Francisco, Singapore, Sydney, Toronto and others) as well as per product, so confirm your region is the affected one first. Avoid destroying and recreating Droplets during a regional incident: the control plane can accept the destroy and then fail the create.

Is it down for everyone, or just you?

If this page says DigitalOcean is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
Fly.io
Fly.io
Netlify
Netlify
Vercel
Vercel

DigitalOcean outage FAQ

Is DigitalOcean down everywhere or just in my region?
Usually just one region. DigitalOcean reports status per datacenter, and most incidents are confined to a single location such as NYC or AMS rather than affecting the whole platform. Find your Droplet's region in the control panel and check that entry specifically. If your region is green and only your server is unreachable, the problem is more likely the Droplet itself.
Are my Droplets and data affected if DigitalOcean has an outage?
Networking and control plane incidents usually leave the underlying disks intact, and Droplets come back with their data when connectivity returns. What you lose is availability, not storage. Incidents affecting Volumes or Managed Databases are the ones worth watching more closely, since those touch the storage layer directly and are reported as separate components.
Why can I reach my Droplet but not the DigitalOcean control panel?
Because they are separate systems. The control panel and API run on DigitalOcean's own infrastructure, while your Droplet is a virtual machine that keeps running whether or not the management layer is reachable. A control panel outage means you cannot create, resize or destroy resources, but existing servers carry on serving traffic normally.
Should I fail over to another region during a DigitalOcean outage?
Only if you already had that path built and tested. Rebuilding into a new region mid-incident means moving data you may not be able to read right now, and the control plane you need to create resources is often part of what is degraded. Note it as a resilience gap for afterwards rather than attempting the migration under pressure.
Does a DigitalOcean outage affect Spaces and the CDN separately?
Yes, and this is a common source of confusion. Spaces and Spaces CDN are listed as their own components, so static assets can fail to load while your application servers are completely healthy. If your site renders but images and stylesheets are missing, check the Spaces components rather than assuming the whole platform is down.

How we measure this

  • We request DigitalOcean's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where DigitalOcean publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when DigitalOcean goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required