DigitalOcean logo

Is DigitalOcean down?

No reported issues

From status.digitalocean.com · checked 46 seconds ago · every minute

Get alerts for DigitalOcean

An email when it goes down, and when it’s back.

As of 03:34 UTC on 12 November 2026, DigitalOcean's status page reports no issues. Its last reported problem was on 27 October 2026: “Kubernetes Cluster Management Operations”, major outage, for 3 h 40 min from 22:15 UTC.

Last problem
27 Oct · 3 h 40 min
Problems, last 30 days
1
Typical incident
1 h 35 min
Longest in 90 days
3 h 40 min · 27 Oct

Uptime

DigitalOcean, last 30 days

99.47 %

100%95%90%
Oct 14 Today

Biggest dip: DigitalOcean, 3.7 h of major outage on Oct 27.

Incidents

Started in the last 7 days

0

210
FSSMTWToday

This week Week before

No incidents this week. The last one: DigitalOcean, major outage on Oct 27.

Recovery

Median time back online

3 h 40 min

3 h 40 min0
30 days ago Today

0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 239

All online

  • API
  • Billing
  • BYOIP
  • Cloud Control Panel
  • Cloud Firewall
  • Community
  • DNS
  • Support Center
  • Reserved IP
  • WWW
  • CSPM
Monitoring 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SGP1
  • SFO1
  • SFO2
  • SFO3
  • SYD1
  • TOR1
Networking 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
App Platform 13 parts
  • Global
  • Amsterdam
  • Atlanta
  • Bangalore
  • Frankfurt
  • Kansas
  • London
  • New York
  • Richmond
  • San Francisco
  • Singapore
  • Sydney
  • Toronto
Event Processing 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
VPC 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Droplets 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Managed Databases 15 parts
  • Global
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Load Balancers 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Functions 11 parts
  • Global
  • AMS3
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Kubernetes 15 parts
  • Global
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC3
  • RIC1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
Volumes 18 parts
  • Global
  • AMS2
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • LON1
  • MKC1
  • NYC1
  • NYC2
  • NYC3
  • RIC1
  • SFO1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • TOR1
GPU Droplets 6 parts
  • Global
  • ATL1
  • MKC1
  • NYC2
  • RIC1
  • TOR1
Spaces 13 parts
  • Global
  • AMS3
  • ATL1
  • BLR1
  • FRA1
  • MKC1
  • NYC3
  • RIC1
  • SFO2
  • SFO3
  • SGP1
  • SYD1
  • LON1
Container Registry 9 parts
  • Global
  • AMS3
  • BLR1
  • FRA1
  • NYC3
  • SFO2
  • SFO3
  • SGP1
  • SYD1
Spaces CDN 11 parts
  • Global
  • AMS3
  • ATL1
  • FRA1
  • LON1
  • MKC1
  • NYC3
  • RIC1
  • SFO3
  • SGP1
  • SYD1
Agentic Inference Cloud 6 parts
  • Agent Runtime
  • Inference
  • ADK
  • Knowledge Bases
  • Guardrails
  • Model Services
Network File Storage 3 parts
  • ATL1
  • MKC1
  • RIC1

Last 90 days

3 incidents in 49 days tracked · no reported issues 99.4% of the time · typical incident 1 h 35 min

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Major outage
    Kubernetes Cluster Management Operations 3 h 40 min
  2. Issue
    DNS Resolution for Managed Kubernetes 1 h 27 min
  3. Issue
    VPC Networking Availability 1 h 35 min
All incidents on status.digitalocean.com ↗

Where this comes from

Stackpulse reads DigitalOcean’s official status page at status.digitalocean.com every minute and keeps 90 days of what changed. We don’t test DigitalOcean ourselves, so a problem shows here once DigitalOcean reports it.

Stackpulse isn’t affiliated with DigitalOcean. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.