Cloud & hosting
Is DigitalOcean down?
Live DigitalOcean status, measured independently. We probe 6 DigitalOcean endpoints from monitoring regions on every continent and record every outage we detect.
DigitalOcean is up
Our probes are reaching DigitalOcean normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 19 to 33 msUnknownp50median response25 msp95slowest 5% of checks59 ms50 ms25024 h ago12 h agonow
- API100% uptime, 30 days6 regions, 108 to 284 msUnknownp50median response197 msp95slowest 5% of checks282 ms500 ms250024 h ago12 h agonow
- Control panel100% uptime, 30 days6 regions, 224 to 559 msUnknownp50median response379 msp95slowest 5% of checks524 ms500 ms250024 h ago12 h agonow
- Documentation99.97% uptime, 30 days6 regions, 63 to 784 msUnknownp50median response316 msp95slowest 5% of checks465 ms500 ms250024 h ago12 h agonow
- Spaces (nyc3)99.97% uptime, 30 days6 regions, 231 to 733 msUnknownp50median response497 msp95slowest 5% of checks634 ms1000 ms500024 h ago12 h agonow
- Official status feed99.99% uptime, 30 days6 regions, 75 to 761 msUnknownp50median response302 msp95slowest 5% of checks482 ms500 ms250024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when DigitalOcean goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment DigitalOcean goes down. They don't count against your monitor quota. Free plan, no card required.
About DigitalOcean outages
DigitalOcean runs Droplets, DOKS Kubernetes, App Platform, Spaces object storage, and managed Postgres, MySQL, Redis, and Kafka across many regions. Incidents are typically regional, affecting networking or a specific product in one data centre.
We probe the website, the API, the cloud control panel, the documentation, and a Spaces object-storage endpoint. A regional networking event will usually show first as a control panel or API degradation.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website digitalocean.com is unreachable. | httpwww.digitalocean.com | HTTP 200 | 1 min |
API The DigitalOcean API is not answering. doctl, Terraform, and autoscaling integrations fail. | httpapi.digitalocean.com/v2/account | HTTP 401 | 2 min |
Control panel The cloud control panel is unreachable. | httpcloud.digitalocean.com/login | HTTP 200 | 1 min |
Documentation DigitalOcean's documentation is unreachable. | httpdocs.digitalocean.com | HTTP 200 | 5 min |
Spaces (nyc3) The Spaces object storage endpoint in nyc3 is not answering. Buckets and CDN-backed assets in that region are affected. | httpnyc3.digitaloceanspaces.com | HTTP 200 | 2 min |
Official status feed DigitalOcean's status page is unreachable. | httpstatus.digitalocean.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see DigitalOcean's official status page.
Recent DigitalOcean outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
DigitalOcean is up. Is your DigitalOcean integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on DigitalOcean and fail quietly. Here is what teams that rely on DigitalOcean monitor on their side.
Droplets and Kubernetes workloads
DigitalOcean reports on its infrastructure, not on whether your processes inside it are healthy. Probe your services and put heartbeats on your CronJobs.
HTTP and TCP monitoringManaged databases and Redis
Managed Redis maintenance drops connections for minutes at a time. A TCP check on the database port and a probe through your app tell you when it happened.
TCP port monitoringDigitalOcean status: frequently asked questions
Provider status pages describe platform-wide health. A single hypervisor, a noisy neighbour, or your own firewall rules can take your Droplet offline without any incident being declared. External probes on your own services are the only way to know.
Look at the per-region results above. If our probes fail from every region, DigitalOcean has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, DigitalOcean may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about DigitalOcean" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on DigitalOcean: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
upti.my is not affiliated with DigitalOcean. DigitalOcean and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.