Is it DigitalOcean, or is it me?
DigitalOcean's status page at status.digitalocean.com reports incidents and maintenance for its products and datacenters, many of which you do not use. Duskwatch is an independent iPhone app for DigitalOcean, in development; it matches DigitalOcean's status to the regions and products your team uses, puts the incidents that touch you first, and sends a push when one does.
Updated
Incidents that touch your regions and products
At 2 a.m. the useful question is not whether DigitalOcean has an incident somewhere, but whether it has one where your things run. The status screen answers that first. "Your regions" lists each place your team uses, worked out from its droplets, apps and database clusters, with the worst component status there, for example "FRA1 and App Platform · 14 services operational".
Open incidents follow, the ones that affect your regions and products ranked above the rest, each with its timeline of updates. Under "Your regions", a component with issues is named by what you have there, such as "Droplets (NYC3): degraded". The screen reads DigitalOcean's public status page without your sign-in, shows when the status it displays is from, and links to status.digitalocean.com (external link) for the full picture.
The status page lists components by product, each broken down by datacenter such as NYC3 or FRA1, alongside global ones.
DigitalOcean status page (external link), verified
Maintenance ahead, and the last 14 days
Scheduled maintenance has its own section, so a window that overlaps your next release is visible before it starts rather than discovered during it. Below that, the last 14 days of incidents are grouped by day: enough to answer "has this happened before" when a client asks, without scrolling an archive.
Status also appears where it matters on resource screens. A Spaces bucket shows the state of Spaces and the Spaces CDN in its region, and an incident there becomes a finding on the bucket, with a link to the status page.
A push for incidents in your regions
If you turn on alerts, an incident that affects your team's regions, or DigitalOcean's API or control panel, sends a push, and another follows when DigitalOcean resolves it. Incidents in regions you do not use stay on the status screen and never wake you. The push names the team and how many of its regions are affected.
"DigitalOcean incident in your regions" · acme-prod · In 1 region since 02:14.
"DigitalOcean incident resolved" · acme-prod
Ways to follow DigitalOcean status
DigitalOcean offers several subscriptions on its status page. All of them cover every incident, wherever it is, which is thorough but noisy if you use two regions out of many.
| Channel | What you get | Filtered to your regions |
|---|---|---|
| Incident created, updated and resolved | No | |
| SMS | Incident created and resolved | No |
| Slack | Updates in a channel | No |
| RSS or Atom feed | The incident history in a feed reader | No |
| status.digitalocean.com | Every component and incident | No |
| Push from Duskwatch | Incidents in your team's regions or the API and control panel, and their resolution | Yes |
Email subscribers hear when DigitalOcean creates, updates or resolves an incident; SMS subscribers hear when one is created or resolved.
DigitalOcean status page: subscribe to updates (external link), verified
The status page also offers a Slack subscription and RSS and Atom feeds of its incident history.
DigitalOcean status page: subscribe to updates (external link), verified
Telling the two apart
- An incident in your region and a droplet off there: likely DigitalOcean. Watch the incident timeline before you reboot.
- No incident, and an uptime check down in every region: likely your service. Open its findings and logs.
- No incident, and a check down in one region only: likely a network path. Give it a few minutes and watch the regions.
- A failed deploy during an App Platform incident: check the incident before you roll back.
What Duskwatch doesn't do here
- No replacement for status.digitalocean.com: the app reads it and links to it.
- No push for incidents in regions your team does not use.
- No status history beyond the last 14 days on the status screen.
- No support tickets or contact with DigitalOcean support.
Questions
Is DigitalOcean down right now?
Check DigitalOcean's status page at status.digitalocean.com for the current state. Duskwatch shows the same status filtered to the regions and products your team uses.
How do I get DigitalOcean incident alerts on my phone?
DigitalOcean offers email, SMS, Slack and RSS or Atom feeds for every incident. Duskwatch sends a push only for incidents in your team's regions or in DigitalOcean's API or control panel, and another when they are resolved.
Is it DigitalOcean or is it me?
The status screen puts incidents in your regions first, next to your resources' own findings. An incident where your droplet runs points to DigitalOcean; none, with your uptime check down everywhere, points to your service.
Which regions count as mine?
The ones your team uses, worked out from its droplets, apps and database clusters. They are listed under "Your regions".