DigitalOcean Outage History

Started Oct 13, 2026, 05:09 PM UTC· resolved Oct 13, 2026, 05:09 PM UTC

1. resolved Oct 13, 2026, 05:09 PM UTC

   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 back the update and restored the affected nodes. App Platform deployment and scaling operations have recovered and are operating normally. We sincerely apologize for any inconvenience this caused. If you continue to experience any issues, please open a support ticket and our team will be happy to assist you.

Read the full incident report →

Started Oct 11, 2026, 10:01 PM UTC· resolved Oct 11, 2026, 11:29 PM UTC

1. investigating Oct 11, 2026, 10:01 PM UTC

   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.

2. monitoring Oct 11, 2026, 10:54 PM UTC

   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.

3. resolved Oct 11, 2026, 11:29 PM UTC

   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/

Read the full incident report →

Started Oct 05, 2026, 10:38 AM UTC· resolved Oct 05, 2026, 12:13 PM UTC

1. identified Oct 05, 2026, 10:38 AM UTC

   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 continued stability. Existing VPC resources and network connectivity remain unaffected. We will provide another update as soon as more information becomes available.

2. monitoring Oct 05, 2026, 11:02 AM UTC

   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 operation has been fully confirmed.

3. resolved Oct 05, 2026, 12:13 PM UTC

   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.

Read the full incident report →

Started Oct 03, 2026, 02:51 PM UTC· resolved Oct 03, 2026, 02:51 PM UTC

1. resolved Oct 03, 2026, 02:51 PM UTC

   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 paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unexpected behavior, please open a support ticket so our team can investigate and assist you.

Read the full incident report →

Started Sep 16, 2026, 09:48 AM UTC· resolved Sep 16, 2026, 09:09 PM UTC

1. investigating Sep 16, 2026, 09:48 AM UTC

   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.digitalocean.com/company/contact/support. We apologize for the inconvenience and appreciate your patience while we work to resolve the issue. We'll provide another update as soon as we have more information.

2. monitoring Sep 16, 2026, 02:07 PM UTC

   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 patience.

3. resolved Sep 16, 2026, 09:09 PM UTC

   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 apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started Sep 09, 2026, 10:47 AM UTC· resolved Sep 09, 2026, 12:25 PM UTC

1. investigating Sep 09, 2026, 10:47 AM UTC

   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 inconvenience and appreciate your patience.

2. monitoring Sep 09, 2026, 11:32 AM UTC

   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.

3. resolved Sep 09, 2026, 12:25 PM UTC

   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.

Read the full incident report →

Started Aug 24, 2026, 05:14 PM UTC· resolved Aug 25, 2026, 07:04 PM UTC

1. investigating Aug 24, 2026, 05:14 PM UTC

   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.

2. investigating Aug 24, 2026, 06:33 PM UTC

   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 patience.

3. monitoring Aug 24, 2026, 07:14 PM UTC

   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.

4. investigating Aug 24, 2026, 10:27 PM UTC

   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 information becomes available. We apologize for the inconvenience and appreciate your patience.

5. monitoring Aug 25, 2026, 12:54 AM UTC

   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.

6. monitoring Aug 25, 2026, 04:30 PM UTC

   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.

7. resolved Aug 25, 2026, 07:04 PM UTC

   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

8. postmortem Sep 15, 2026, 06:44 PM UTC

   ## 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 initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a critical authorization query. In response to the elevated query latency, multiple upstream services initiated automated hedged retries. This secondary request amplification led to queue buildup in excess of the authentication service pool's processing throughput, resulting in cascading request timeouts across the authorization path. To mitigate the initial degradation, engineering teams rerouted authorization traffic onto a single healthy processing path and temporarily disabled hedging for primary callers, successfully restoring service availability. However, upon returning traffic to the standard multipath routing configuration, lingering query latency combined with retry behavior from unhedged callers caused recurrent queue saturation, leading to the second window of degradation. ## 2. Impact * Active customer accounts \(<2%\) experienced one or more API or Control Panel request failures during the event windows. * Aggregate failure rates across both impact windows averaged approximately 10% of authenticated requests, with a peak error rate of 25% during the second window. * Affected management control planes included the Cloud Control Panel, Public API, Kubernetes cluster authentication, Container Registry, and Serverless / AI Inference endpoints. * Data plane components—including active Droplets, network routing, and block storage volumes—maintained 100% availability, as established connections do not depend on the affected authorization control path. There was zero data loss. ## 3. Current state All impacted control plane services have been restored to nominal operational capacity. The database infrastructure migration has been completed. Remediation controls have been validated to ensure system stability against similar query latency scenarios. ## 4. Preventing recurrence To prevent future occurrences and enhance systemic resilience, DigitalOcean has implemented the following technical enhancements: 1. Automated Request Throttling and Circuit Breaking: Deployed automated circuit breakers across upstream services to detect downstream dependency degradation and automatically suppress hedged/retry amplification. Completed a broad architecture audit to ensure retry suppression and circuit breaking are uniformly enforced across all control plane services. 1. Queue Management and Load Shedding: Implemented fast-fail load-shedding mechanisms to prevent request queue saturation during dependency slowness, accompanied by proactive telemetry alerts to identify queue backing prior to customer impact. 1. Graceful Service Degradation: Configured critical authorization components to operate in degraded execution modes utilizing asynchronous, eventually-consistent data replicas during primary database latency events. ## 5. Timeline | **Time UTC** | **Event** | | --- | --- | | 16:56 | A specific authorization query began running significantly slower than its historical baseline. | | 16:58 | Automated monitoring detected abnormal error rates and latency; detected within 5 minutes of impact starting. | | 17:05–18:52 | Operators tuned retry configuration and consolidated requests to a healthy service instance \(first unavailability window closed\). | | 21:30 | Shifting traffic back to the production pattern caused the same saturation problem \(second unavailability window begins\). | | 21:30–23:09 | Teams disabled the retry/amplification behavior across the remaining affected services and added additional read capacity for the slow query. Service was restored to a stable state. |

Read the full incident report →

Started Aug 23, 2026, 05:11 AM UTC· resolved Aug 23, 2026, 02:33 PM UTC

1. investigating Aug 23, 2026, 05:11 AM UTC

   Our Engineering team has identified 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.

2. investigating Aug 23, 2026, 07:06 AM UTC

   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.

3. monitoring Aug 23, 2026, 11:30 AM UTC

   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.

4. resolved Aug 23, 2026, 02:33 PM UTC

   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/

Read the full incident report →

Started Aug 21, 2026, 12:59 PM UTC· resolved Aug 21, 2026, 02:52 PM UTC

1. investigating Aug 21, 2026, 12:59 PM UTC

   Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions. During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…" Our Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.

2. monitoring Aug 21, 2026, 01:06 PM UTC

   Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied. Spaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal. We are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored.

3. resolved Aug 21, 2026, 02:52 PM UTC

   Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.

Read the full incident report →

Started Aug 19, 2026, 11:10 AM UTC· resolved Aug 19, 2026, 07:34 PM UTC

1. investigating Aug 19, 2026, 11:10 AM UTC

   Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes. During this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state. Our team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.

2. identified Aug 19, 2026, 12:22 PM UTC

   We have identified the root cause of the issue in the MKC1 region affecting multiple racks and nodes. Our Engineering team is actively implementing remediation steps to restore connectivity and bring the impacted nodes back online. During this time, customers may continue to experience disruptions to GPU workloads, degraded performance for Serverless Inference, and Kubernetes (DOKS) worker nodes may remain in a NotReady state and inability to reach Kubernetes API endpoints or perform cluster-management operations in affected clusters. We will provide another update as soon as we have more information.

3. identified Aug 19, 2026, 03:28 PM UTC

   Our Engineering team continues to work on the issue affecting the MKC1 region. We are actively working to restore connectivity and bring the impacted nodes back online. We will provide another update as soon as we have more information.

4. monitoring Aug 19, 2026, 06:59 PM UTC

   At this time, the regional control plane is fully healthy. CPU Droplets, Managed databases, Load balancers, Block storage and Spaces are operating normally. Droplet create, resize and other management operations are working. Kubernetes (DOKS) control planes are reachable. Our teams are continuing to work with the facility to restore all equipment. GPU Droplets in MKC1 remain offline or unreachable. DOKS GPU worker nodes may remain NotReady, and GPU-backed inference endpoints in this region may be unavailable. We will monitor the regional control plane for a short time and then resolve this incident. GPU customers will receive personalized updates with more information in lieu of this status page. If you have questions about your affected resources, contact support and reference this incident.

5. resolved Aug 19, 2026, 07:34 PM UTC

   Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally. GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates. Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.

Read the full incident report →

Started Aug 13, 2026, 02:59 PM UTC· resolved Aug 13, 2026, 02:59 PM UTC

1. resolved Aug 13, 2026, 02:59 PM UTC

   Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters. During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources. Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this. We apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.

Read the full incident report →

Started Aug 08, 2026, 06:57 PM UTC· resolved Aug 09, 2026, 01:01 AM UTC

1. investigating Aug 08, 2026, 06:57 PM UTC

   Our Engineering team is currently investigating reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions. During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected. Our Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.

2. investigating Aug 08, 2026, 07:38 PM UTC

   Our Engineering team is continuing to investigate reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions. During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected. Further investigation has found that GenAI services are also affected due to this issue, customers may also be unable to access the Droplet console, and Database clusters may be stuck in a "Creating" state. Our Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.

3. identified Aug 08, 2026, 08:02 PM UTC

   Our Engineering team has identified the root cause of the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions. Customers may experience the following: Unable to create new accounts Unable to create Droplets Unable to allocate Reserved IPs Failures with Automated Backups and Snapshots operations Droplet Autoscale scaling operations not working as expected DOKS cluster operations failing GenAI services impacted Unable to access the Droplet console Database clusters stuck in a "Creating" state Our Engineering team is working on implementing a fix and we will provide another update as soon as more information becomes available.

4. identified Aug 08, 2026, 10:02 PM UTC

   Our Engineering team continues to work on implementing and rolling out a fix for the issue affecting multiple services across multiple regions, including new account registration, Droplets, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet console, and Database cluster creation. Customers may continue to experience the previously reported service disruptions while remediation efforts remain in progress. We will provide another update as soon as more information becomes available.

5. monitoring Aug 09, 2026, 12:31 AM UTC

   Our Engineering team has implemented a fix for the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions, and is currently monitoring the situation. At this time, customers should no longer experience errors with: New account registration Droplet creation Reserved IP allocation Automated Backups and Snapshots operations Droplet Autoscale scaling operations DOKS cluster operations GenAI services Access to the Droplet console Database cluster creation We will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved.

6. resolved Aug 09, 2026, 01:01 AM UTC

   Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation. We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.

Read the full incident report →

Started Aug 06, 2026, 07:01 PM UTC· resolved Aug 06, 2026, 09:05 PM UTC

1. investigating Aug 06, 2026, 07:01 PM UTC

   Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform. We apologize for the inconvenience and will share an update once we have more information.

2. monitoring Aug 06, 2026, 08:02 PM UTC

   Our Engineering team has implemented a fix for the issue affecting Functions on App Platform. Functions builds/deploys and requests to Functions endpoints should now be completing successfully. We are currently monitoring the situation to ensure the service has returned to normal operation and remains stable. We apologize for the inconvenience and will provide a further update once the incident is confirmed resolved.

3. resolved Aug 06, 2026, 09:05 PM UTC

   Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.

Read the full incident report →

Started Aug 06, 2026, 04:33 PM UTC· resolved Aug 06, 2026, 04:33 PM UTC

1. resolved Aug 06, 2026, 04:33 PM UTC

   Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing. Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications. The services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing. We apologize for any inconvenience this may have caused. If you continue to experience issues with any of these services, please don't hesitate to open a support ticket. Our team will be happy to assist you.

Read the full incident report →

Started Aug 04, 2026, 04:13 PM UTC· resolved Aug 04, 2026, 09:42 PM UTC

1. investigating Aug 04, 2026, 04:13 PM UTC

   Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.

2. identified Aug 04, 2026, 06:52 PM UTC

   Our Engineering team has identified the issue affecting Spaces Cold Storage billing. The team is actively working on a fix to resolve the issue. We apologize for the inconvenience and will provide another update as soon as more information becomes available.

3. monitoring Aug 04, 2026, 08:44 PM UTC

   Our Engineering team has implemented a fix for the issue affecting Spaces Cold Storage billing and is currently monitoring the situation. Customers with cold storage buckets should no longer see incorrect values reflected in their daily usage and current invoices. We will post an update as soon as the issue is fully resolved.

4. resolved Aug 04, 2026, 09:42 PM UTC

   As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets. Our team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Aug 03, 2026, 01:58 PM UTC· resolved Aug 03, 2026, 05:59 PM UTC

1. investigating Aug 03, 2026, 01:58 PM UTC

   Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating. We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

2. monitoring Aug 03, 2026, 04:39 PM UTC

   We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved

3. resolved Aug 03, 2026, 05:59 PM UTC

   Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.

Read the full incident report →

Started Jul 29, 2026, 05:56 PM UTC· resolved Jul 30, 2026, 06:15 AM UTC

1. investigating Jul 29, 2026, 05:56 PM UTC

   We are currently investigating this issue.

2. investigating Jul 29, 2026, 09:41 PM UTC

   Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3. At this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service. We apologize for the inconvenience and will share an update once we have more information.

3. resolved Jul 30, 2026, 06:15 AM UTC

   Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 27, 2026, 06:31 PM UTC· resolved Jul 28, 2026, 03:24 PM UTC

1. investigating Jul 27, 2026, 06:31 PM UTC

   We are currently investigating this issue.

2. identified Jul 27, 2026, 07:44 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Jul 28, 2026, 03:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 10:36 AM UTC· resolved Jul 24, 2026, 12:42 PM UTC

1. identified Jul 24, 2026, 10:36 AM UTC

   We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

2. monitoring Jul 24, 2026, 11:45 AM UTC

   We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. resolved Jul 24, 2026, 12:42 PM UTC

   Between 07:46 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.

Read the full incident report →

Started Jul 23, 2026, 11:16 AM UTC· resolved Jul 23, 2026, 12:37 PM UTC

1. investigating Jul 23, 2026, 11:16 AM UTC

   Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference. We apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.

2. resolved Jul 23, 2026, 12:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 04:50 PM UTC· resolved Jul 22, 2026, 07:42 PM UTC

1. investigating Jul 22, 2026, 04:50 PM UTC

   We are currently investigating this issue.

2. resolved Jul 22, 2026, 07:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 19, 2026, 09:51 AM UTC· resolved Jul 19, 2026, 03:32 PM UTC

1. investigating Jul 19, 2026, 09:51 AM UTC

   Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1 and NYC3 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.

2. investigating Jul 19, 2026, 01:34 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 19, 2026, 01:36 PM UTC

   We are continuing to investigate this issue.

4. monitoring Jul 19, 2026, 02:52 PM UTC

   Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

5. resolved Jul 19, 2026, 03:32 PM UTC

   Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Started Jul 19, 2026, 06:57 AM UTC· resolved Jul 19, 2026, 09:52 AM UTC

1. investigating Jul 19, 2026, 06:57 AM UTC

   We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services. Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.

2. identified Jul 19, 2026, 08:27 AM UTC

   Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution. Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1. We will provide another update once the issue has been fully resolved or when additional information becomes available.

3. monitoring Jul 19, 2026, 09:31 AM UTC

   Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1. We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

4. resolved Jul 19, 2026, 09:52 AM UTC

   Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Read the full incident report →

Started Jul 16, 2026, 01:39 PM UTC· resolved Jul 16, 2026, 05:24 PM UTC

1. investigating Jul 16, 2026, 01:39 PM UTC

   Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1. Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.

2. identified Jul 16, 2026, 03:30 PM UTC

   Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1. Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.

3. monitoring Jul 16, 2026, 05:01 PM UTC

   Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results. Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team. We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.

4. resolved Jul 16, 2026, 05:24 PM UTC

   Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Started Jul 13, 2026, 07:04 PM UTC· resolved Jul 15, 2026, 09:46 PM UTC

1. identified Jul 13, 2026, 07:04 PM UTC

   We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts. Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place

2. monitoring Jul 13, 2026, 10:24 PM UTC

   A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

3. identified Jul 14, 2026, 11:07 AM UTC

   We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts. Our Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

4. monitoring Jul 15, 2026, 10:06 AM UTC

   A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

5. resolved Jul 15, 2026, 09:46 PM UTC

   The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels. We will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.

Read the full incident report →