Is DigitalOcean down?
Check DigitalOcean availability, incident history, downtime reports, and website performance.
https://www.digitalocean.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for DigitalOcean
Last 24 hoursThere is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.
Last collection attempt: 2026-10-20 07:53:25 UTC · Insufficient activity.
No user-submitted outage reports in the last 24 hours.
DigitalOcean outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
DigitalOcean website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-10-22 00:10:53 UTC.
Checked address: https://www.digitalocean.com/
DNS lookup: 5 ms · TCP connection: 1 ms · TLS handshake: 12 ms. Certificate expires 2026-12-10; trusted connection: yes.
100%
Successful website checks (24h)
136 successful / 136 measurable checks
45 ms
Median response time
64 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
DigitalOcean official status · fetched 2026-10-22 00:09:10 UTC
256 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| API | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Global | operational |
| Agent Runtime | operational |
| ATL1 | operational |
| Amsterdam | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| Billing | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS2 | operational |
| AMS3 | operational |
| ATL1 | operational |
| Inference | operational |
| MKC1 | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| BLR1 | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| AMS3 | operational |
| BLR1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| Atlanta | operational |
| BYOIP | operational |
| ADK | operational |
| MKC1 | operational |
| RIC1 | operational |
| Bangalore | operational |
| FRA1 | operational |
| BLR1 | operational |
| FRA1 | operational |
| FRA1 | operational |
| BLR1 | operational |
| Cloud Control Panel | operational |
| BLR1 | operational |
| NYC2 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| ATL1 | operational |
| Knowledge Bases | operational |
| Frankfurt | operational |
| BLR1 | operational |
| BLR1 | operational |
| NYC3 | operational |
| BLR1 | operational |
| FRA1 | operational |
| BLR1 | operational |
| FRA1 | operational |
| BLR1 | operational |
| LON1 | operational |
| FRA1 | operational |
| BLR1 | operational |
| BLR1 | operational |
| Cloud Firewall | operational |
| LON1 | operational |
| Guardrails | operational |
| RIC1 | operational |
| FRA1 | operational |
| FRA1 | operational |
| LON1 | operational |
| FRA1 | operational |
| FRA1 | operational |
| FRA1 | operational |
| FRA1 | operational |
| LON1 | operational |
| FRA1 | operational |
| Community | operational |
| TOR1 | operational |
| SFO2 | operational |
| Model Services | operational |
| MKC1 | operational |
| MKC1 | operational |
| Kansas | operational |
| MKC1 | operational |
| LON1 | operational |
| London | operational |
| SFO3 | operational |
| LON1 | operational |
| LON1 | operational |
| LON1 | operational |
| LON1 | operational |
| NYC3 | operational |
| LON1 | operational |
| LON1 | operational |
| NYC3 | operational |
| NYC1 | operational |
| DNS | operational |
| MKC1 | operational |
| MKC1 | operational |
| SGP1 | operational |
| NYC1 | operational |
| SFO3 | operational |
| NYC1 | operational |
| Support Center | operational |
| New York | operational |
| RIC1 | operational |
| RIC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| MKC1 | operational |
| NYC1 | operational |
| NYC1 | operational |
| SYD1 | operational |
| NYC1 | operational |
| NYC3 | operational |
| NYC1 | operational |
| NYC1 | operational |
| NYC2 | operational |
| SGP1 | operational |
| SFO3 | operational |
| NYC1 | operational |
| NYC1 | operational |
| Reserved IP | operational |
| SFO2 | operational |
| Richmond | operational |
| San Francisco | operational |
| NYC2 | operational |
| NYC2 | operational |
| NYC2 | operational |
| NYC2 | operational |
| NYC2 | operational |
| SFO3 | operational |
| NYC2 | operational |
| NYC2 | operational |
| NYC3 | operational |
| SGP1 | operational |
| SYD1 | operational |
| WWW | operational |
| RIC1 | operational |
| Singapore | operational |
| NYC3 | operational |
| NYC3 | operational |
| NYC3 | operational |
| NYC3 | operational |
| SGP1 | operational |
| NYC3 | operational |
| NYC3 | operational |
| TOR1 | operational |
| NYC3 | operational |
| SYD1 | operational |
| SFO2 | operational |
| SFO2 | operational |
| Agentic Inference Cloud | operational |
| Sydney | operational |
| App Platform | operational |
| SFO3 | operational |
| SYD1 | operational |
| SFO3 | operational |
| RIC1 | operational |
| RIC1 | operational |
| RIC1 | operational |
| RIC1 | operational |
| RIC1 | operational |
| RIC1 | operational |
| RIC1 | operational |
| Toronto | operational |
| Container Registry | operational |
| SGP1 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SFO1 | operational |
| SFO1 | operational |
| SFO1 | operational |
| SFO1 | operational |
| SFO1 | operational |
| SFO1 | operational |
| LON1 | operational |
| Droplets | operational |
| SYD1 | operational |
| SYD1 | operational |
| SFO2 | operational |
| SFO2 | operational |
| SFO2 | operational |
| SFO2 | operational |
| SFO2 | operational |
| SFO2 | operational |
| SFO1 | operational |
| SFO3 | operational |
| SFO3 | operational |
| SFO3 | operational |
| TOR1 | operational |
| Event Processing | operational |
| SFO3 | operational |
| TOR1 | operational |
| SFO3 | operational |
| SFO3 | operational |
| SFO2 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SGP1 | operational |
| SFO3 | operational |
| Functions | operational |
| SYD1 | operational |
| SYD1 | operational |
| SYD1 | operational |
| SYD1 | operational |
| SYD1 | operational |
| SYD1 | operational |
| SYD1 | operational |
| GPU Droplets | operational |
| TOR1 | operational |
| TOR1 | operational |
| TOR1 | operational |
| TOR1 | operational |
| TOR1 | operational |
| TOR1 | operational |
| Managed Databases | operational |
| TOR1 | operational |
| Monitoring | operational |
| Networking | operational |
| Network File Storage | operational |
| Kubernetes | operational |
| Load Balancers | operational |
| Spaces | operational |
| Spaces CDN | operational |
| VPC | operational |
| Volumes | operational |
| CSPM | operational |
Official incident timeline
App Platform Deployments · resolved · 2026-10-13T17:09:48.123Z
Product match: components.
Read the provider’s incident report
- · resolved
Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled
DNS Resolution for Managed Kubernetes · resolved · 2026-10-11T23:29:01.711Z
Product match: components.
Read the provider’s incident report
- · resolved
Our Engineering team has resolved the external DNS resolution failures affecting Managed Kubernetes across multiple regions. Applications running on Managed Kubernetes can now resolve external domain names. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience problems, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/
- · monitoring
Our Engineering team has implemented a fix to address the intermittent external DNS lookup failures affecting Managed Kubernetes clusters in multiple regions. We are currently monitoring the results to ensure the issue is fully resolved. We will provide another update as soon as the issue is confirmed to be resolved.
- · investigating
Our Engineering team is investigating an issue causing intermittent external DNS lookup failures for Managed Kubernetes clusters in multiple regions. Applications running on affected clusters may intermittently fail to resolve external domain names. We apologize for the inconvenience and will provide further updates as more information becomes available.
VPC Networking Availability · resolved · 2026-10-05T12:13:16.787Z
Product match: components.
Read the provider’s incident report
- · resolved
Our Engineering team fully resolved the VPC Networking disruption as of 10:29 UTC. Customers can now create and delete VPC peering connections, subnets, and routes as expected. Following the recovery, we monitored the affected systems and confirmed that VPC Networking operations remain stable. We apologize for any inconvenience this disruption may have caused. If you continue to experience unexpected behavior, please open a ticket with our Support team for further assistance.
- · monitoring
Our Engineering team has implemented a fix for the VPC Networking disruption. Customers should now be able to create and delete VPC peering connections, subnets, and routes as expected. Previously pending operations have been cleared, and VPC Networking operations are returning to normal. Our Engineering team is monitoring the affected systems to ensure continued stability and verify that operations remain healthy. We appreciate your patience and will provide another update once normal operati
- · identified
Our Engineering team identified a disruption affecting VPC Networking operations that began at approximately 08:48 UTC. During this time, customers may have experienced delays or failures when creating or deleting VPC peerings, VPC Native DOKS clusters, or Private Network Connections (PNCs), as well as when adding cluster members. Creating routes and subnets may also have been affected. Operations are now returning to normal, and our Engineering team is monitoring the affected systems to ensure
A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved) · resolved · 2026-10-03T14:51:13.637Z
Product match: components.
Read the provider’s incident report
- · resolved
From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant path
Support Portal Service Disruption · resolved · 2026-09-16T21:09:31.524Z
Product match: components.
Read the provider’s incident report
- · resolved
From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We a
- · monitoring
The Support Portal and ticket creation are now accessible. Our upstream provider has applied a fix, and we've verified ticket creation and review are working as expected. We'll continue monitoring for the next 2 hours to confirm full stability and will post a final update once the incident is closed. If you're still unable to access the portal, please use our Support Contact form as a backup: https://www.digitalocean.com/company/contact/support We apologize for the disruption and appreciate your
- · investigating
Our Support Portal is currently experiencing issues due to a third-party service disruption impacting our systems. During this time, customers may be unable to access the Support Portal or create new support tickets for their concerns. Existing support requests may also experience delayed responses from our Support team. As a workaround if you're unable to access the Support Portal or need to create a new support ticket, please submit your request via Support Contact form: https://www.digitaloc
Power Degradation impacting GPU Performance in ATL1 · resolved · 2026-09-09T12:25:52.160Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident is now resolved. Power redundancy has been fully restored, and we have confirmed that customer impact has been mitigated. We are closing this incident.
- · monitoring
The power issue affecting part of our ATL1 datacenter has been fully resolved. Power redundancy has been restored, and any potential customer impact has been mitigated. We will continue monitoring the environment to ensure continued stability.
- · investigating
We are investigating a power issue affecting part of our ATL1 datacenter. Redundant power systems are keeping servers online, and we have not observed any server outages. However, available power capacity is reduced, which may cause degraded performance for some GPU workloads, particularly during periods of high utilization. Our datacenter and infrastructure teams are working to restore full power redundancy. We will provide an update as more information becomes available. We apologize for the
Cloud Control Panel and API · postmortem · 2026-09-15T19:11:53.801Z
Product match: components.
Read the provider’s incident report
- · postmortem
## 1. What happened Between 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \(Volumes\) remained fully functional and unaffected throughout the event. No customer data loss occurred. The event was in
- · resolved
Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more. Thank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account
- · monitoring
Our Engineering team has continued to monitor the health of all services and has observed no recurrence of impact over the past 12+ hours. We will continue to monitor services for a short period to confirm stability before we mark this incident resolved. We understand the impact this incident had for DigitalOcean users and we will publish a postmortem on the status page to provide further details on root cause and mitigation.
- · monitoring
Our Engineering team has implemented mitigation measures to address the issue impacting the DigitalOcean public API and Cloud Control Panel. We are seeing improvements, and users should now be able to access the Cloud Control Panel and use the public API normally. We are continuing to monitor the service to ensure it remains stable and will provide further updates as more information becomes available. We appreciate your patience and understanding.
- · investigating
Our Engineering team is investigating a recurrence of the issue impacting the DigitalOcean public API and Cloud Control Panel. This issue does not impact our data plane (i.e. running droplets). Users may experience difficulties accessing the Cloud Control Panel, along with elevated latency and intermittent errors when accessing the public API or Cloud Control Plane. We are actively investigating the issue and working to restore normal service. We will continue to provide updates as more inform
- · monitoring
Our Engineering team has implemented mitigation measures to address the issue affecting the DigitalOcean public API and Cloud Control Panel. We are seeing requests succeed, and users should now be able to access the Cloud Control Panel and issue/receive API requests normally. We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved
- · investigating
We are continuing to investigate the issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, we are seeing some improvement in latency/error rates and some users may now be able to access the Cloud Control Panel. Serverless Inference users may currently experience 403 and 503 errors when making API requests or accessing affected services. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your
- · investigating
Our Engineering team is investigating an issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, users will see elevated 5xx errors for all API requests, including things like creates for various products. Users may also be unable to access cloud.digitalocean.com. We are actively investigating the root cause and will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience.
Managed Databases Creation · resolved · 2026-08-23T14:33:31.735Z
Product match: components.
Read the provider’s incident report
- · resolved
Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally. Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/
- · monitoring
Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters. We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
- · investigating
We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions. During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API. Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.
- · investigating
Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests. We apologize for the inconvenience and will share an update once we have more information.
Recovery tracker
No recent recovery can be established from available evidence.
6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 49 ms · Earlier median: 46 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
- is digitalocean down
Query “is digitalocean” · observed 2026-10-22 00:11:54 UTC · 0 newly observed problem phrases.
Query “digitalocean” · observed 2026-10-22 00:11:54 UTC · 0 newly observed problem phrases.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of DigitalOcean.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
About DigitalOcean status on Iszdown
Check DigitalOcean availability, incident history, downtime reports, and website performance.
This page combines the available DigitalOcean report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
256 product-matched official components are listed above. Latest public website measurement: 2026-10-22T00:10:53.000Z.
Visit the official DigitalOcean website · Official provider status · How it works
What to check when DigitalOcean is not working
These are troubleshooting suggestions, not a list of currently reported problems.
DigitalOcean will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
DigitalOcean is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent DigitalOcean outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| DNS Resolution for Managed Kubernetes | 87 min | resolved | |
| VPC Networking Availability | 95 min | resolved | |
| Support Portal Service Disruption | 681 min | resolved | |
| Power Degradation impacting GPU Performance in ATL1 | 98 min | resolved | |
| Cloud Control Panel and API | 1550 min | postmortem | |
| Managed Databases Creation | 562 min | resolved | |
| Container Registry and Spaces Accessibility | 113 min | resolved | |
| Major Service Interruption in MKC1 | 505 min | resolved |
Frequently asked questions about DigitalOcean
Is DigitalOcean down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:14:17.000Z.
How many DigitalOcean outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does DigitalOcean show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every DigitalOcean feature.
When was DigitalOcean status last updated?
The latest status observation was 2026-10-22T00:09:10.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has DigitalOcean had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow DigitalOcean or report a problem?
Use “Watch this service” to save DigitalOcean in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to DigitalOcean
Check a related product separately; its status can differ from DigitalOcean.