Skip to content

Outage tracker / DigitalOcean

Is DigitalOcean down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached DigitalOcean from all 10 regions we check.

As of Oct 5, 2026, 8:14 PM UTC, DigitalOcean answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured DigitalOcean (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:14 PM UTC
US-East81 msOperational
US-West130 msOperational
Europe236 msOperational
Asia-Pacific534 msOperational
US-Central84 msOperational
Canada139 msOperational
UK186 msOperational
Southeast Asia282 msOperational
Australia249 msOperational
South America182 msOperational
their status pagetheir claim, not our reading

DigitalOcean reports: All systems operational (“All Systems Operational”)

from DigitalOcean's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and DigitalOcean's own status page agree: both show DigitalOcean as reachable right now.

DigitalOcean's own component breakdown, as they publish it

  • APIOperational
  • ATL1Operational
  • Agent RuntimeOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • GlobalOperational
  • AMS2Operational
  • AMS2Operational
  • AMS2Operational
  • AMS2Operational
  • AMS2Operational
  • AMS2Operational
  • AMS2Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • ATL1Operational
  • AmsterdamOperational
  • BillingOperational
  • InferenceOperational
  • MKC1Operational
  • ADKOperational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • AMS3Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • AtlantaOperational
  • BLR1Operational
  • BLR1Operational
  • BYOIPOperational
  • MKC1Operational
  • RIC1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • ATL1Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • BangaloreOperational
  • Cloud Control PanelOperational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • Knowledge BasesOperational
  • NYC2Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • BLR1Operational
  • Cloud FirewallOperational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • FrankfurtOperational
  • GuardrailsOperational
  • LON1Operational
  • LON1Operational
  • NYC3Operational
  • RIC1Operational
  • CommunityOperational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • FRA1Operational
  • LON1Operational
  • LON1Operational
  • SFO2Operational
  • TOR1Operational

These are DigitalOcean's components, named and scored by DigitalOcean. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is DigitalOcean's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

DigitalOcean response time, by region

US-East
554msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 308ms2026-09-07 UTC: p95 332ms2026-09-08 UTC: p95 284ms2026-09-09 UTC: p95 257ms2026-09-10 UTC: p95 244ms2026-09-11 UTC: p95 321ms2026-09-12 UTC: p95 312ms2026-09-13 UTC: p95 313ms2026-09-14 UTC: p95 272ms2026-09-15 UTC: p95 311ms2026-09-16 UTC: p95 491ms2026-09-17 UTC: p95 912ms2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 984ms2026-09-20 UTC: p95 539ms2026-09-21 UTC: p95 513ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 578ms2026-09-24 UTC: p95 478ms2026-09-25 UTC: p95 518ms2026-09-26 UTC: p95 493ms2026-09-27 UTC: p95 520ms2026-09-28 UTC: p95 489ms2026-09-29 UTC: p95 566ms2026-09-30 UTC: p95 506ms2026-10-01 UTC: p95 468ms2026-10-02 UTC: p95 483ms2026-10-03 UTC: p95 601ms2026-10-04 UTC: p95 652ms2026-10-05 UTC: p95 554ms
Sep 6Sep 20Oct 5
US-West
466msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 633ms2026-09-07 UTC: p95 625ms2026-09-08 UTC: p95 598ms2026-09-09 UTC: p95 440ms2026-09-10 UTC: p95 356ms2026-09-11 UTC: p95 285ms2026-09-12 UTC: p95 365ms2026-09-13 UTC: p95 535ms2026-09-14 UTC: p95 691ms2026-09-15 UTC: p95 622ms2026-09-16 UTC: p95 559ms2026-09-17 UTC: p95 218ms2026-09-18 UTC: p95 288ms2026-09-19 UTC: p95 245ms2026-09-20 UTC: p95 288ms2026-09-21 UTC: p95 563ms2026-09-22 UTC: p95 557ms2026-09-23 UTC: p95 270ms2026-09-24 UTC: p95 249ms2026-09-25 UTC: p95 439ms2026-09-26 UTC: p95 697ms2026-09-27 UTC: p95 709ms2026-09-28 UTC: p95 620ms2026-09-29 UTC: p95 411ms2026-09-30 UTC: p95 409ms2026-10-01 UTC: p95 452ms2026-10-02 UTC: p95 408ms2026-10-03 UTC: p95 454ms2026-10-04 UTC: p95 462ms2026-10-05 UTC: p95 466ms
Sep 6Sep 20Oct 5
Europe
358msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 597ms2026-09-07 UTC: p95 637ms2026-09-08 UTC: p95 697ms2026-09-09 UTC: p95 639ms2026-09-10 UTC: p95 740ms2026-09-11 UTC: p95 711ms2026-09-12 UTC: p95 784ms2026-09-13 UTC: p95 792ms2026-09-14 UTC: p95 754ms2026-09-15 UTC: p95 762ms2026-09-16 UTC: p95 760ms2026-09-17 UTC: p95 497ms2026-09-18 UTC: p95 570ms2026-09-19 UTC: p95 584ms2026-09-20 UTC: p95 474ms2026-09-21 UTC: p95 517ms2026-09-22 UTC: p95 612ms2026-09-23 UTC: p95 560ms2026-09-24 UTC: p95 611ms2026-09-25 UTC: p95 650ms2026-09-26 UTC: p95 627ms2026-09-27 UTC: p95 643ms2026-09-28 UTC: p95 540ms2026-09-29 UTC: p95 432ms2026-09-30 UTC: p95 416ms2026-10-01 UTC: p95 443ms2026-10-02 UTC: p95 397ms2026-10-03 UTC: p95 519ms2026-10-04 UTC: p95 423ms2026-10-05 UTC: p95 358ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 909ms2026-09-07 UTC: p95 641ms2026-09-08 UTC: p95 868ms2026-09-09 UTC: p95 916ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 934ms2026-09-13 UTC: p95 830ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 564ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 829ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 983ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 876ms2026-09-28 UTC: p95 830ms2026-09-29 UTC: p95 838ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
267msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 467ms2026-09-07 UTC: p95 467ms2026-09-08 UTC: p95 475ms2026-09-09 UTC: p95 369ms2026-09-10 UTC: p95 309ms2026-09-11 UTC: p95 405ms2026-09-12 UTC: p95 145ms2026-09-13 UTC: p95 135ms2026-09-14 UTC: p95 178ms2026-09-15 UTC: p95 150ms2026-09-16 UTC: p95 159ms2026-09-17 UTC: p95 167ms2026-09-18 UTC: p95 197ms2026-09-19 UTC: p95 213ms2026-09-20 UTC: p95 156ms2026-09-21 UTC: p95 172ms2026-09-22 UTC: p95 172ms2026-09-23 UTC: p95 160ms2026-09-24 UTC: p95 325ms2026-09-25 UTC: p95 462ms2026-09-26 UTC: p95 384ms2026-09-27 UTC: p95 365ms2026-09-28 UTC: p95 375ms2026-09-29 UTC: p95 425ms2026-09-30 UTC: p95 396ms2026-10-01 UTC: p95 351ms2026-10-02 UTC: p95 318ms2026-10-03 UTC: p95 400ms2026-10-04 UTC: p95 422ms2026-10-05 UTC: p95 267ms
Sep 6Sep 20Oct 5
Canada
393msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 389ms2026-09-07 UTC: p95 412ms2026-09-08 UTC: p95 354ms2026-09-09 UTC: p95 347ms2026-09-10 UTC: p95 456ms2026-09-11 UTC: p95 375ms2026-09-12 UTC: p95 408ms2026-09-13 UTC: p95 489ms2026-09-14 UTC: p95 515ms2026-09-15 UTC: p95 539ms2026-09-16 UTC: p95 445ms2026-09-17 UTC: p95 230ms2026-09-18 UTC: p95 226ms2026-09-19 UTC: p95 220ms2026-09-20 UTC: p95 220ms2026-09-21 UTC: p95 212ms2026-09-22 UTC: p95 260ms2026-09-23 UTC: p95 309ms2026-09-24 UTC: p95 306ms2026-09-25 UTC: p95 219ms2026-09-26 UTC: p95 776ms2026-09-27 UTC: p95 550ms2026-09-28 UTC: p95 498ms2026-09-29 UTC: p95 410ms2026-09-30 UTC: p95 439ms2026-10-01 UTC: p95 373ms2026-10-02 UTC: p95 418ms2026-10-03 UTC: p95 403ms2026-10-04 UTC: p95 435ms2026-10-05 UTC: p95 393ms
Sep 6Sep 20Oct 5
UK
454msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 266ms2026-09-07 UTC: p95 265ms2026-09-08 UTC: p95 404ms2026-09-09 UTC: p95 223ms2026-09-10 UTC: p95 218ms2026-09-11 UTC: p95 152ms2026-09-12 UTC: p95 196ms2026-09-13 UTC: p95 202ms2026-09-14 UTC: p95 245ms2026-09-15 UTC: p95 248ms2026-09-16 UTC: p95 245ms2026-09-17 UTC: p95 236ms2026-09-18 UTC: p95 233ms2026-09-19 UTC: p95 281ms2026-09-20 UTC: p95 250ms2026-09-21 UTC: p95 458ms2026-09-22 UTC: p95 319ms2026-09-23 UTC: p95 513ms2026-09-24 UTC: p95 607ms2026-09-25 UTC: p95 738ms2026-09-26 UTC: p95 474ms2026-09-27 UTC: p95 287ms2026-09-28 UTC: p95 318ms2026-09-29 UTC: p95 424ms2026-09-30 UTC: p95 407ms2026-10-01 UTC: p95 439ms2026-10-02 UTC: p95 688ms2026-10-03 UTC: p95 747ms2026-10-04 UTC: p95 678ms2026-10-05 UTC: p95 454ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 926ms2026-09-10 UTC: p95 872ms2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 953ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 951ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
537msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 972ms2026-09-07 UTC: p95 808ms2026-09-08 UTC: p95 665ms2026-09-09 UTC: p95 689ms2026-09-10 UTC: p95 737ms2026-09-11 UTC: p95 731ms2026-09-12 UTC: p95 781ms2026-09-13 UTC: p95 998ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 554ms2026-09-16 UTC: p95 905ms2026-09-17 UTC: p95 692ms2026-09-18 UTC: p95 700ms2026-09-19 UTC: p95 897ms2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 929ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 918ms2026-09-24 UTC: p95 927ms2026-09-25 UTC: p95 962ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 847ms2026-09-28 UTC: p95 844ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 719ms2026-10-01 UTC: p95 747ms2026-10-02 UTC: p95 768ms2026-10-03 UTC: p95 533ms2026-10-04 UTC: p95 573ms2026-10-05 UTC: p95 537ms
Sep 6Sep 20Oct 5
South America
853msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 932ms2026-09-07 UTC: p95 987ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 784ms2026-09-10 UTC: p95 865ms2026-09-11 UTC: p95 772ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 943ms2026-09-17 UTC: p95 421ms2026-09-18 UTC: p95 371ms2026-09-19 UTC: p95 206ms2026-09-20 UTC: p95 362ms2026-09-21 UTC: p95 358ms2026-09-22 UTC: p95 390ms2026-09-23 UTC: p95 689ms2026-09-24 UTC: p95 872ms2026-09-25 UTC: p95 810ms2026-09-26 UTC: p95 756ms2026-09-27 UTC: p95 811ms2026-09-28 UTC: p95 588ms2026-09-29 UTC: p95 667ms2026-09-30 UTC: p95 702ms2026-10-01 UTC: p95 727ms2026-10-02 UTC: p95 675ms2026-10-03 UTC: p95 903ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 853ms
Sep 6Sep 20Oct 5

Is it DigitalOcean, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not DigitalOcean -- it cannot diagnose DigitalOcean's own systems.

Get an email when we see DigitalOcean go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching DigitalOcean, and again when they can reach it again. That is our own measurement from ten regions, not DigitalOcean's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 81msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach DigitalOcean normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 130msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach DigitalOcean normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 84msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach DigitalOcean normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 139msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach DigitalOcean normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 182msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach DigitalOcean normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 236msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach DigitalOcean normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 186msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach DigitalOcean normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 534msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach DigitalOcean normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 282msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach DigitalOcean normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 249msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach DigitalOcean normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using DigitalOcean, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for DigitalOcean yet, which is not evidence that nothing is wrong.

Recent outages

VPC Networking Availability, 1h 35mdeclared on their status page2026-10-05
A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved), 1mdeclared on their status page2026-10-03
Support Portal Service Disruption, 11h 21mdeclared on their status page2026-09-16
Power Degradation impacting GPU Performance in ATL1, 1h 38mdeclared on their status page2026-09-09
Cloud Control Panel and API, 25h 50mdeclared on their status page2026-08-24
Managed Databases Creation, 9h 22mdeclared on their status page2026-08-23
Container Registry and Spaces Accessibility, 1h 53mdeclared on their status page2026-08-21
Major Service Interruption in MKC1, 8h 25mdeclared on their status page2026-08-19

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring DigitalOcean since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for DigitalOcean covering any window you pick, with our measurements and DigitalOcean's own claim at the time, side by side.

Full availability history for DigitalOcean: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

DigitalOcean uptime measured by RealUptimeLive, from this page's own readings.
[![DigitalOcean uptime measured by RealUptime](https://realuptime.io/outages/digitalocean/badge.svg?days=30)](https://realuptime.io/outages/digitalocean)
<a href="https://realuptime.io/outages/digitalocean"><img src="https://realuptime.io/outages/digitalocean/badge.svg?days=30" alt="DigitalOcean uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What DigitalOcean's SLA implies, from our measurement

At or above your target

We measured none of downtime for DigitalOcean over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from DigitalOcean's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.digitalocean.com/v2/account
secondary
https://status.digitalocean.com/
RealUptime is not affiliated with DigitalOcean; the name identifies what we measured, and nothing here speaks for DigitalOcean's own team. We send a single web request to DigitalOcean from 10 regions on our own schedule and time the response. We do not see inside DigitalOcean's systems, do not use an account or real transaction, and are not the same signal DigitalOcean's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for DigitalOcean is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.