Skip to content

Outage tracker / DigitalOcean

Is DigitalOcean down?

I'm having a problem

Vendor reports no incidentWhat DigitalOcean reports

DigitalOcean reports no incident on its status page.

As of the last successful poll, 2026-10-22 23:30 UTC.

DigitalOcean's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of DigitalOcean pass from all 10 regions we check.

As of Oct 22, 2026, 11:37 PM UTC, RealUptime's checks of DigitalOcean passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 11:37 PM UTC
US-East837 msChecks passing
US-West1223 msChecks passing
Europe302 msChecks passing
Asia-Pacific1354 msChecks passing
US-Central105 msChecks passing
Canada467 msChecks passing
UK337 msChecks passing
Southeast Asia1415 msChecks passing
Australia884 msChecks passing
South America956 msChecks passing
their status pagetheir claim, not our reading

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

from DigitalOcean's own status page, checked Oct 22, 2026, 11:22 PM UTC
DigitalOcean's own status page shows no incident, and our checks of DigitalOcean pass 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
1.0sp95 · 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-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 541ms2026-10-06 UTC: p95 434ms2026-10-07 UTC: p95 390ms2026-10-08 UTC: p95 636ms2026-10-09 UTC: p95 614ms2026-10-10 UTC: p95 601ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 581ms2026-10-13 UTC: p95 667ms2026-10-14 UTC: p95 578ms2026-10-15 UTC: p95 575ms2026-10-16 UTC: p95 642ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.0s
Sep 23Oct 7Oct 22
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 462ms2026-10-06 UTC: p95 158ms2026-10-07 UTC: p95 418ms2026-10-08 UTC: p95 413ms2026-10-09 UTC: p95 446ms2026-10-10 UTC: p95 425ms2026-10-11 UTC: p95 434ms2026-10-12 UTC: p95 196ms2026-10-13 UTC: p95 316ms2026-10-14 UTC: p95 631ms2026-10-15 UTC: p95 663ms2026-10-16 UTC: p95 658ms2026-10-17 UTC: p95 737ms2026-10-18 UTC: p95 890ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 909ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Europe
771msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 356ms2026-10-06 UTC: p95 277ms2026-10-07 UTC: p95 343ms2026-10-08 UTC: p95 268ms2026-10-09 UTC: p95 250ms2026-10-10 UTC: p95 292ms2026-10-11 UTC: p95 439ms2026-10-12 UTC: p95 273ms2026-10-13 UTC: p95 405ms2026-10-14 UTC: p95 422ms2026-10-15 UTC: p95 404ms2026-10-16 UTC: p95 398ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 771ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.0sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.2s2026-10-06 UTC: p95 795ms2026-10-07 UTC: p95 949ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 2.0s
Sep 23Oct 7Oct 22
US-Central
282msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 310ms2026-10-06 UTC: p95 405ms2026-10-07 UTC: p95 187ms2026-10-08 UTC: p95 249ms2026-10-09 UTC: p95 329ms2026-10-10 UTC: p95 344ms2026-10-11 UTC: p95 368ms2026-10-12 UTC: p95 280ms2026-10-13 UTC: p95 245ms2026-10-14 UTC: p95 364ms2026-10-15 UTC: p95 370ms2026-10-16 UTC: p95 402ms2026-10-17 UTC: p95 704ms2026-10-18 UTC: p95 813ms2026-10-19 UTC: p95 837ms2026-10-20 UTC: p95 758ms2026-10-21 UTC: p95 615ms2026-10-22 UTC: p95 282ms
Sep 23Oct 7Oct 22
Canada
575msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 405ms2026-10-06 UTC: p95 434ms2026-10-07 UTC: p95 485ms2026-10-08 UTC: p95 470ms2026-10-09 UTC: p95 396ms2026-10-10 UTC: p95 524ms2026-10-11 UTC: p95 496ms2026-10-12 UTC: p95 154ms2026-10-13 UTC: p95 331ms2026-10-14 UTC: p95 763ms2026-10-15 UTC: p95 700ms2026-10-16 UTC: p95 847ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 575ms
Sep 23Oct 7Oct 22
UK
813msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 452ms2026-10-06 UTC: p95 385ms2026-10-07 UTC: p95 453ms2026-10-08 UTC: p95 432ms2026-10-09 UTC: p95 378ms2026-10-10 UTC: p95 350ms2026-10-11 UTC: p95 302ms2026-10-12 UTC: p95 331ms2026-10-13 UTC: p95 206ms2026-10-14 UTC: p95 222ms2026-10-15 UTC: p95 229ms2026-10-16 UTC: p95 234ms2026-10-17 UTC: p95 873ms2026-10-18 UTC: p95 964ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 813ms
Sep 23Oct 7Oct 22
Southeast Asia
2.0sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.2s2026-10-06 UTC: p95 606ms2026-10-07 UTC: p95 516ms2026-10-08 UTC: p95 471ms2026-10-09 UTC: p95 603ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 596ms2026-10-13 UTC: p95 724ms2026-10-14 UTC: p95 723ms2026-10-15 UTC: p95 708ms2026-10-16 UTC: p95 643ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 2.0s
Sep 23Oct 7Oct 22
Australia
1.1sp95 · 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-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 579ms2026-10-06 UTC: p95 682ms2026-10-07 UTC: p95 646ms2026-10-08 UTC: p95 604ms2026-10-09 UTC: p95 977ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 989ms2026-10-12 UTC: p95 846ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 839ms2026-10-15 UTC: p95 979ms2026-10-16 UTC: p95 864ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
South America
2.4sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 831ms2026-10-06 UTC: p95 529ms2026-10-07 UTC: p95 656ms2026-10-08 UTC: p95 591ms2026-10-09 UTC: p95 582ms2026-10-10 UTC: p95 598ms2026-10-11 UTC: p95 601ms2026-10-12 UTC: p95 353ms2026-10-13 UTC: p95 441ms2026-10-14 UTC: p95 464ms2026-10-15 UTC: p95 439ms2026-10-16 UTC: p95 588ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22

Check your own site while you wait on DigitalOcean

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.

Email me when DigitalOcean reports an incident on its status page, and again when it reports it resolved.

Get an email when DigitalOcean reports an incident

Email me when DigitalOcean reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is DigitalOcean's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 837msstatus code: 401checked: Oct 22, 2026, 11:34 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
      Checks passinglatency: 1223msstatus code: 401checked: Oct 22, 2026, 11:37 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
      Checks passinglatency: 105msstatus code: 401checked: Oct 22, 2026, 11:29 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
      Checks passinglatency: 467msstatus code: 401checked: Oct 22, 2026, 11:36 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
    Checks passinglatency: 956msstatus code: 401checked: Oct 22, 2026, 11:19 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 302msstatus code: 401checked: Oct 22, 2026, 11:30 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
      Checks passinglatency: 337msstatus code: 401checked: Oct 22, 2026, 11:24 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1354msstatus code: 401checked: Oct 22, 2026, 11:34 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
      Checks passinglatency: 1415msstatus code: 401checked: Oct 22, 2026, 11:21 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
      Checks passinglatency: 884msstatus code: 401checked: Oct 22, 2026, 11:21 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 probe events

App Platform Deployments, 1mdeclared on their status page2026-10-13
DNS Resolution for Managed Kubernetes, 1h 27mdeclared on their status page2026-10-11
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

check 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 check readings and DigitalOcean's own claim at the time, side by side.

Full check history for DigitalOcean: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![DigitalOcean uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is DigitalOcean down?", https://realuptime.io/outages/digitalocean. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://api.digitalocean.com/v2/account
secondary
https://status.digitalocean.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.digitalocean.com

RealUptime is not affiliated with DigitalOcean; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.