Where does this status come from?

From DigitalOcean's own status page API at https://status.digitalocean.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are DigitalOcean's words.

How can my agent or app check DigitalOcean status?

Fetch https://upbutler.com/status/digitalocean/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"digitalocean"}, on https://upbutler.com/mcp/public.

Is DigitalOcean down?

Right now

No. DigitalOcean is operational.

No incidents reported.

Read from status.digitalocean.com 69 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/digitalocean/status.agent.json

MCP: upstream_status {"service":"digitalocean"}

Droplets, App Platform, managed databases and Spaces.

What DigitalOcean reports

Operational

Taken as is from DigitalOcean's own status page API. Incident titles and component names below are theirs.

Open status.digitalocean.com

UpButler's independent probe

There is no keyless endpoint of DigitalOcean that says anything useful, so UpButler does not probe it. To check your own DigitalOcean account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

DigitalOcean components

80 operational

APIOperational
BillingOperational
BYOIPOperational
Cloud Control PanelOperational

Monitoring

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational
BLR1Operational

Networking

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational

App Platform

GlobalOperational
AmsterdamOperational
AtlantaOperational
BangaloreOperational
FrankfurtOperational

Event Processing

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational
BLR1Operational

VPC

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational

Droplets

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational
BLR1Operational

Managed Databases

GlobalOperational
AMS3Operational
ATL1Operational
BLR1Operational

Load Balancers

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational
BLR1Operational

Functions

GlobalOperational
AMS3Operational
BLR1Operational
FRA1Operational

Kubernetes

GlobalOperational
AMS3Operational
ATL1Operational
BLR1Operational
FRA1Operational

Volumes

GlobalOperational
AMS2Operational
AMS3Operational
ATL1Operational
BLR1Operational

GPU Droplets

GlobalOperational
ATL1Operational
MKC1Operational
NYC2Operational

Spaces

GlobalOperational
AMS3Operational
ATL1Operational
BLR1Operational
FRA1Operational

Container Registry

GlobalOperational
AMS3Operational
BLR1Operational
FRA1Operational
NYC3Operational

Spaces CDN

GlobalOperational
AMS3Operational
ATL1Operational
FRA1Operational

Agentic Inference Cloud

Agent RuntimeOperational
InferenceOperational
ADKOperational
Knowledge BasesOperational

Network File Storage

ATL1Operational
MKC1Operational
RIC1Operational

DigitalOcean incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-05 10:38	VPC Networking Availability	minor	1 h 35 min
2026-10-03 14:51	A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)	none	under a minute

Tell your outage from DigitalOcean's

Declare that your project depends on DigitalOcean. When one of your monitors fails while DigitalOcean has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - digitalocean

Ask before you retry

curl -s https://upbutler.com/status/digitalocean/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "digitalocean",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is DigitalOcean down right now?: No. As of 2026-10-10 05:12 UTC, DigitalOcean is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From DigitalOcean's own status page API at https://status.digitalocean.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are DigitalOcean's words.
How can my agent or app check DigitalOcean status?: Fetch https://upbutler.com/status/digitalocean/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"digitalocean"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or DigitalOcean's?: Add "digitalocean" to the dependencies of your UpButler workspace. When one of your monitors fails while DigitalOcean has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in cloud and edge

UpButler is not affiliated with DigitalOcean. Status and incident text belong to DigitalOcean and are read from their public status source; the probe result is UpButler's own measurement.