DigitalOcean Outage History
DigitalOcean is up right nowPingoru has recorded 104 incidents for DigitalOcean: 104 in the last 12 months and 18 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 15 | 42 of 720 (6%) |
| May 2026 | 10 | 30 of 744 (4%) |
| June 2026 | 6 | 11 of 720 (1%) |
| July 2026 | 16 | 166 of 744 (22%) |
| August 2026 | 10 | 63 of 744 (8%) |
| September 2026 | 2 | 13 of 720 (2%) |
| October 2026 | 4 | 3 of 590 (1%) |
Incidents, newest first
Minor April 17, 2026 DNS Resolution for .co TLD 16h 47m DNS
Started Apr 17, 2026, 09:22 PM UTC· resolved Apr 18, 2026, 02:10 PM UTC
- identified Apr 17, 2026, 09:22 PM UTC
Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used. Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will continue to monitor the situation closely and post updates as more information becomes available.
- monitoring Apr 17, 2026, 10:53 PM UTC
Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD). During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution. Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.
- resolved Apr 18, 2026, 02:10 PM UTC
Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.
Notice April 17, 2026 Spaces availability in NYC3 – NYC3
Started Apr 17, 2026, 06:27 PM UTC· resolved Apr 17, 2026, 06:27 PM UTC
- resolved Apr 17, 2026, 06:27 PM UTC
From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
Minor April 15, 2026 Serverless Inference 1h 48m Agent Runtime
Started Apr 15, 2026, 01:07 AM UTC· resolved Apr 15, 2026, 02:56 AM UTC
- investigating Apr 15, 2026, 01:07 AM UTC
Our Engineering team is investigating an issue causing elevated error rates due to service instability and terminating open connections which causes some 500s. Some requests may fail while we work to resolve it. We apologize for the inconvenience and will share an update once we have more information.
- monitoring Apr 15, 2026, 02:24 AM UTC
Our Engineering team has implemented a fix for the issue causing elevated error rates due to service instability. We are currently monitoring the situation to ensure stability and confirm that error rates, including HTTP 500 responses, have returned to normal levels. We will provide a further update once we confirm the issue is fully resolved.
- resolved Apr 15, 2026, 02:56 AM UTC
From 23:20 UTC to 02:00 UTC, users may have experienced elevated error rates due to service instability, which resulted in intermittent HTTP 500 errors and terminated connections. Our Engineering team has confirmed full resolution of the issue, and all systems are now operating normally. If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.
Minor April 14, 2026 Managed Database Resizes 2h 26m Global, Global
Started Apr 14, 2026, 12:53 PM UTC· resolved Apr 14, 2026, 03:19 PM UTC
- investigating Apr 14, 2026, 12:53 PM UTC
Our engineering team is investigating an issue impacting resize operations for Managed Databases. During this time, users may experience error when attempting to resize Managed Database via Cloud Control Panel and API in all regions. We apologize for the inconvenience and will share an update once we have more information.
- monitoring Apr 14, 2026, 02:30 PM UTC
Our Engineering team has taken action to mitigate the issue with resize operations for Managed Databases and implemented a fix . We are monitoring the situation and will post an update as soon as we confirm that the issue is fully resolved.
- resolved Apr 14, 2026, 03:19 PM UTC
Our Engineering team has resolved the issue with resize operations for Managed Databases and should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience.
Notice April 10, 2026 Droplet Availability in All Regions 33m API, Global, Global, Cloud Control Panel
Started Apr 10, 2026, 08:32 PM UTC· resolved Apr 10, 2026, 09:06 PM UTC
- monitoring Apr 10, 2026, 08:32 PM UTC
Subject: Droplet Availability in All Regions Our Engineering team has identifed an issue with Droplet creates in all regions. A root cause has been found, a fix has been put in place and we are currently monitoring the situation to ensure full resolution. Users should be able to create new Droplets at this time. We will continue to monitor and we will post an update as soon as it is fully resolved. We apologize for the inconvenience.
- resolved Apr 10, 2026, 09:06 PM UTC
Our Engineering team has confirmed full resolution of the issue with creating Droplets in all regions. Users should be able to create Droplets without issue. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.
Notice April 7, 2026 Control Plane – API, Cloud Control Panel
Started Apr 07, 2026, 05:49 PM UTC· resolved Apr 07, 2026, 05:49 PM UTC
- resolved Apr 07, 2026, 05:49 PM UTC
Our Engineering team has resolved the control plane disruption that occurred from 17:06 to 17:18 UTC. During this time, users may have experienced intermittent issues with managing their resources through the Cloud Control Panel or DigitalOcean API. The root cause of the disruption was identified and addressed, and all services are now operating normally. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
Minor April 7, 2026 Serverless Inference - High error rates for open source models ( Qwen 3 32B) 3h 1m Agent Runtime
Started Apr 07, 2026, 12:49 PM UTC· resolved Apr 07, 2026, 03:50 PM UTC
- investigating Apr 07, 2026, 12:49 PM UTC
Serverless inference for alibaba-qwen3-32b (Qwen 3 32B) in tor1 is experiencing high error rates starting at 10:46 UTC.
- identified Apr 07, 2026, 12:55 PM UTC
We are currently investigating reports of elevated latency affecting requests to this model when using Serverless Inference and Agents. Earlier observations indicated increased error rates for the open-source Qwen 3 32B model. The Ray dashboard also showed multiple workers in a pending state, suggesting capacity constraints. Our analysis determined that the model was experiencing higher-than-expected request volume without sufficient resources to scale accordingly. To address this, the node pool size has been increased to improve available capacity. However, there are still insufficient nodes to fully support the desired number of model replicas. Following the node pool expansion, a new pod-related error has been identified. Our Engineering team is actively working to resolve this issue and restore full service performance.
- resolved Apr 07, 2026, 03:50 PM UTC
Service has been fully restored, and the model is now operating normally. We have implemented improvements to enhance stability and reduce the likelihood of similar issues in the future.
Minor April 6, 2026 Serverless Inference Issue 5h 34m Agent Runtime
Started Apr 06, 2026, 12:28 PM UTC· resolved Apr 06, 2026, 06:02 PM UTC
- investigating Apr 06, 2026, 12:28 PM UTC
Our Engineering team is investigating an issue with Serverless inference. At this time, users may experience high error rates for open source models (llama 3.3 70b). We apologize for the inconvenience and will share an update once we have more information.
- monitoring Apr 06, 2026, 03:15 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 06, 2026, 06:02 PM UTC
This incident has been resolved.
Minor March 20, 2026 App platform seeing delays in deployments across FRA1 region 1h 28m Frankfurt
Started Mar 20, 2026, 10:32 AM UTC· resolved Mar 20, 2026, 12:01 PM UTC
- investigating Mar 20, 2026, 10:32 AM UTC
Our engineers are currently investigating an issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. During this time, some users may experience delay when creating new App Platform apps or deploying existing apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.
- monitoring Mar 20, 2026, 11:14 AM UTC
Our Engineering team has deployed a fix to resolve the issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. We are actively monitoring the situation to ensure stability and will provide an update once the incident has been fully resolved. Thank you for your patience and we apologize for the inconvenience.
- resolved Mar 20, 2026, 12:01 PM UTC
The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 00:08am UTC & 11:46am UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue. We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.
Major March 20, 2026 Gradient AI Platform agents and services Accessibility 5h 24m Agent Runtime
Started Mar 20, 2026, 08:50 AM UTC· resolved Mar 20, 2026, 02:14 PM UTC
- investigating Mar 20, 2026, 08:50 AM UTC
We are currently investigating issue affecting the accessibility of agents and services on the Gradient AI Platform. Users may experience failures or unresponsiveness when attempting to use these features. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will share an update once we have more information.
- identified Mar 20, 2026, 09:51 AM UTC
We’ve identified the issue and are currently working on restoring the services. We’ll continue to provide updates as progress is made.
- identified Mar 20, 2026, 11:05 AM UTC
We've identified the issue and are actively working to restore the affected services. We're making steady progress and closely monitoring the situation. Further updates will be shared as they become available.
- monitoring Mar 20, 2026, 02:04 PM UTC
A fix has been implemented and services have been restored. We are continuing to monitor the system to ensure stability. We will provide further updates if needed.
- resolved Mar 20, 2026, 02:14 PM UTC
Our Engineering team has implemented a fix, the issues impacting Gradient AI Platform have been resolved. All agents are back up and healthy. Service has been fully restored.
Minor March 17, 2026 Gradient AI model availability 4h 48m Agent Runtime
Started Mar 17, 2026, 03:00 PM UTC· resolved Mar 17, 2026, 07:49 PM UTC
- investigating Mar 17, 2026, 03:00 PM UTC
Our Engineering team is investigating reports of Gradient AI model availability issues impacting multiple models. Users may experience issues with models availability, including Llama3.1-8b and Qwen3-32b, as well as embedding models such as GTE Large (v1.5), All-MiniLM-L6-v2, Multi-QA-mpnet-base-dot-v1, and Qwen3 Embedding 0.6B. Additionally, Guardrails are not available, affecting associated agents, and users attempting to run inference on the Llama3.3-70b model will see degraded performance. We apologize for the inconvenience and will share an update once we have more information.
- resolved Mar 17, 2026, 07:49 PM UTC
Our Engineering team has implemented a fix, the issues impacting model availability and performance have been resolved. All models, including those previously degraded, are back up and healthy. Service has been fully restored.
Minor March 15, 2026 Degraded performance with BYOK Anthropic models 36m Agent Runtime
Started Mar 15, 2026, 02:55 AM UTC· resolved Mar 15, 2026, 03:31 AM UTC
- investigating Mar 15, 2026, 02:55 AM UTC
Our Engineering team is investigating an issue related to all Gradient AI agents and serverless inference that require BYOK Anthropic modles. Impacted users may experience degraded performance. We will provide an update as soon as possible
- resolved Mar 15, 2026, 03:31 AM UTC
The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally. Contact support if issues persist.
Minor March 13, 2026 Delay in App Platform Deployments 3h 46m Global
Started Mar 13, 2026, 10:01 PM UTC· resolved Mar 14, 2026, 01:47 AM UTC
- monitoring Mar 13, 2026, 09:30 PM UTC
Starting at 20:40 UTC, users may have seen delays with deploying new apps on App Platform. At this time, our Engineering team is seeing signs of recovery, and users should be able to deploy new apps without issue. We're currently monitoring the situation to ensure full recovery. We apologize for the inconvenience. We'll post an update once the issue has been confirmed to be resolved.
- identified Mar 13, 2026, 10:01 PM UTC
Our Engineering team is starting to see delays once again with new App Platform deployments. During this time, users may still experience delays with deploying new apps. We're working with our upstream provider to resolve the issue. We again apologize for the inconvenience. We will post further updates once we have more information.
- monitoring Mar 13, 2026, 11:39 PM UTC
After working with our upstream provider, our Engineering team has implemented a fix to resolve the issue that was causing delays in the deployment of new apps, and they are currently monitoring the situation. During this time, users should no longer experience issues with creating new apps and all the stalled creation events should provision completely. We will post an update as soon as the issue is fully resolved.
- resolved Mar 14, 2026, 01:47 AM UTC
As of 23:00 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments. Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.
Minor March 13, 2026 Newly Created Managed Kubernetes Nodes 5h 8m Global
Started Mar 13, 2026, 11:26 AM UTC· resolved Mar 13, 2026, 04:35 PM UTC
- investigating Mar 13, 2026, 11:26 AM UTC
Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, new nodes may experience DNS timeouts, which could temporarily affect cluster services. We apologize for the inconvenience and will share an update once we have more information.
- identified Mar 13, 2026, 12:32 PM UTC
Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, Only customers who run a NAT Gateway in their VPC and a VPC-native clusters are affected and may experience DNS timeouts. We apologize for the inconvenience and will share an update once we have more information.
- monitoring Mar 13, 2026, 01:55 PM UTC
Our Engineering team has implemented a fix to address the issue causing DNS timeouts for newly provisioned Managed Kubernetes nodes. Further investigation has confirmed that this issue primarily affected customers utilizing a NAT Gateway within their VPC and running a VPC-native cluster. We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.
- resolved Mar 13, 2026, 04:35 PM UTC
Our Engineering team has confirmed the resolution of the issue impacting DNS timeouts for newly provisioned Managed Kubernetes nodes. At this time all cluster services should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Notice March 9, 2026 Ubuntu/Debian Package Mirror Failure – Global
Started Mar 09, 2026, 07:23 PM UTC· resolved Mar 09, 2026, 07:23 PM UTC
- resolved Mar 09, 2026, 07:23 PM UTC
From 17:50 to 19:06 UTC, Our Engineering team observed an issue with mirrors.digitalocean.com. During this time, users may have experienced errors when trying to update packages on Debian and Ubuntu Images. Our team has fully resolved the issues as of 19:06 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
Notice March 6, 2026 HTTP 522 Error on App Platform – Global
Started Mar 06, 2026, 09:22 PM UTC· resolved Mar 06, 2026, 09:22 PM UTC
- resolved Mar 06, 2026, 09:22 PM UTC
Our Engineering team identified an issue affecting the App Platform. During the incident, users may have experienced HTTP 522 (Connection Timed Out) errors when accessing their apps. The issue seems to be resolved now. We apologize for the inconvenience caused. If you continue to experience any related errors, please contact our Support team by opening a ticket at https://www.digitalocean.com/support/contact/.
Minor March 5, 2026 Internal Load Balancers Connectivity 1h 28m Global
Started Mar 05, 2026, 12:23 AM UTC· resolved Mar 05, 2026, 01:52 AM UTC
- investigating Mar 05, 2026, 12:23 AM UTC
Our Engineering team is investigating an issue affecting Internal Load Balancers. Customers may experience connectivity loss between Internal Load Balancers and their associated target droplets. We apologize for the inconvenience and will share an update as soon as more information becomes available.
- monitoring Mar 05, 2026, 01:19 AM UTC
Our Engineering team has implemented mitigation measures to address the connectivity issues affecting Internal Load Balancers and their associated target droplets. We are actively monitoring the situation to ensure stability and to prevent any recurrence. We will provide a further update once we confirm the issue is fully resolved.
- resolved Mar 05, 2026, 01:52 AM UTC
From 19:57 UTC to 01:03 UTC, customers may have experienced connectivity issues between Internal Load Balancers and their associated target droplets, which could have resulted in service disruption or traffic routing failures. Our Engineering team has confirmed full resolution of the issue, and Internal Load Balancers should now be functioning normally. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience caused.
Minor February 26, 2026 Intermittent Errors with Llama 3.3-70B 6h 23m Agent Runtime
Started Feb 26, 2026, 04:00 PM UTC· resolved Feb 26, 2026, 10:23 PM UTC
- investigating Feb 26, 2026, 07:38 PM UTC
We are currently investigating an issue affecting the Llama 3.3-70B model. Symptoms: Users may encounter intermittent errors when making serverless inference requests via APIs and Agents. Current Status: Our engineering team is actively investigating the issue to determine the root cause.
- monitoring Feb 26, 2026, 09:52 PM UTC
Fix deployed. Monitoring resources related to the Llama 3.3-70B. Users should no longer experience intermittent errors when making serverless inference requests via APIs and Agents . Awaiting confirmation before closure.
- resolved Feb 26, 2026, 10:23 PM UTC
Issue resolved. Cause: A few requests made to the Llama 3.3-70B model caused issues. Impact: Intermittent errors when interacting with the model through serverless inference and/or with agents created using this model. Contact support if issues persist.
Minor February 19, 2026 Control Panel Visibility 1h 7m Cloud Control Panel
Started Feb 19, 2026, 05:34 PM UTC· resolved Feb 19, 2026, 06:42 PM UTC
- investigating Feb 19, 2026, 05:34 PM UTC
Our team is currently investigating an issue impacting the visibility of the Control Panel. Users may notice unexpected behavior, such as being prompted for login credentials when accessing the console, being unable to select radio buttons for any plans during resize, columns appearing squished, etc. We apologize for the inconvenience and will share further updates as soon as more information becomes available.
- monitoring Feb 19, 2026, 06:05 PM UTC
Our team has implemented a fix to address the issue affecting the visibility of the Cloud Panel. We are actively monitoring the situation to ensure overall stability. Users should no longer encounter abnormalities when accessing the console, resizing the Droplet, misalignments within the Cloud Panel, etc. We will provide a further update once the issue is fully confirmed to be resolved.
- resolved Feb 19, 2026, 06:42 PM UTC
The issue impacting the visibility of Cloud Panel has been confirmed to be resolved. Between approximately 16:08 PM & 17:56 PM UTC, users may have noticed unusual behavior when accessing the console, performing resizing operations, or experiencing issues with the Cloud Panel visibility. Our team has taken necessary corrective measures to restore the service, and we can confirm that it is now functioning as expected. We sincerely apologize for the inconvenience caused and truly appreciate your understanding throughout this process. However, if you continue to experience any issues, please do not hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.
Notice February 16, 2026 Spaces Availability in NYC3 3h 21m NYC3, NYC3
Started Feb 16, 2026, 07:36 AM UTC· resolved Feb 16, 2026, 10:58 AM UTC
- monitoring Feb 16, 2026, 07:36 AM UTC
Between 5:34 and 6:32 UTC, our Engineering team identified the issue that was impacting the availability of Spaces and the Container Registry in the NYC3 region. A fix has been implemented to resolve the issue. During this time users may have experienced errors while interacting with Spaces. Additionally, CRUD operations (create, read, update, delete) within the Container Registry may have failed or returned errors during this time. We are now monitoring the platform to ensure services remain stable and operating as expected. We will provide a final update once the issue is fully resolved. If you continue to experience any issues, please contact our Support team.
- resolved Feb 16, 2026, 10:58 AM UTC
Our Engineering team has confirmed that the issue impacting the availability of Spaces and the Container Registry in the NYC3 region has been fully resolved. A fix was implemented, and services have been restored. All operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.
Notice February 16, 2026 Droplet Limit Increase Feature 2h 46m
Started Feb 16, 2026, 06:38 AM UTC· resolved Feb 16, 2026, 09:24 AM UTC
- investigating Feb 16, 2026, 06:38 AM UTC
Our Engineering team is currently investigating an issue affecting the Droplet limit increase feature within the Cloud Control Panel. At this time requests to increase Droplet limits submitted through the Control Panel are not being processed. Customer submissions to increase limits are not generating support tickets as expected. We are actively working to identify the root cause and restore normal functionality as quickly as possible. If you urgently require a Droplet limit increase, please contact Support directly by creating a Support ticket from within your account.
- monitoring Feb 16, 2026, 08:37 AM UTC
The issue affecting the Droplet limit increase feature within the Cloud Control Panel has been identified and a fix has been implemented. Requests submitted through the Control Panel are now generating Support tickets as expected. Our team is continuing to monitor the system to ensure full functionality and stability. If you experience any further issues with Droplet limit increase requests, please contact Support directly by creating a Support ticket from within your account.
- resolved Feb 16, 2026, 09:24 AM UTC
Our Engineering team has confirmed that the issue affecting the Droplet limit increase feature within the Cloud Control Panel has been fully resolved. Requests to increase Droplet limits submitted through the Control Panel are now being processed correctly, and Support tickets are being generated as expected. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.
Minor February 12, 2026 MongoDB Cluster Creation 6h 24m Global
Started Feb 12, 2026, 05:42 AM UTC· resolved Feb 12, 2026, 12:06 PM UTC
- investigating Feb 12, 2026, 05:42 AM UTC
Our Engineering team is investigating an issue with all events for MongoDB clusters in all of our regions. During this time, users may face issues with creation, fork and resize operations in the MongoDB clusters. We apologize for the inconvenience and will share an update once we have more information.
- investigating Feb 12, 2026, 07:34 AM UTC
Our engineering team continues to investigate the issue with create, fork and resize events failure for MongoDB clusters in all of our regions. We appreciate your patience and will post an update as soon as additional information is available.
- identified Feb 12, 2026, 09:04 AM UTC
Our engineering team has identified the cause of the issue with create, fork and resize events failure for MongoDB clusters in all of our regions and is actively working on a fix. We will post an update as soon as additional information is available.
- monitoring Feb 12, 2026, 09:50 AM UTC
Our Engineering team has implemented a fix to resolve the issue with MongoDB clusters and at this time, services should be functioning as expected. We're monitoring the situation and will post a final update once we confirm this is fully resolved.
- resolved Feb 12, 2026, 12:06 PM UTC
Our Engineering team has confirmed the full resolution of the issue with MongoDB Clusters. Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.
Minor February 11, 2026 App platform seeing delays in deployments across all regions. 1h 18m Global
Started Feb 11, 2026, 11:50 AM UTC· resolved Feb 11, 2026, 01:08 PM UTC
- investigating Feb 11, 2026, 11:50 AM UTC
Our engineers are currently investigating an issue impacting new App Platform deployments. During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.
- monitoring Feb 11, 2026, 12:03 PM UTC
Our team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. Users may already notice improvements while deploying apps. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.
- resolved Feb 11, 2026, 01:08 PM UTC
The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 08:52 UTC & 13:01 UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue. We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.
Minor February 3, 2026 Cloud Control Panel 1h 26m API, Cloud Control Panel
Started Feb 03, 2026, 05:27 PM UTC· resolved Feb 03, 2026, 06:53 PM UTC
- investigating Feb 03, 2026, 05:27 PM UTC
Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.
- investigating Feb 03, 2026, 05:32 PM UTC
Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.
- identified Feb 03, 2026, 05:51 PM UTC
Our Engineering team has identified the cause of the issue impacting the Cloud Control Panel and API and is actively working on deploying a fix. At this time, users will continue to see timeouts/5xx errors, but may intermittently see requests succeeding. We will post further updates as soon as the fix is deployed or there is more information to share.
- monitoring Feb 03, 2026, 06:03 PM UTC
Our Engineering team has implemented a fix for the timeouts affecting the Cloud Control Panel and API, and is currently monitoring the situation. Services have recovered, and users should no longer experience 5xx errors when using the API or gateway timeouts when accessing the Cloud Control Panel. 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.
- resolved Feb 03, 2026, 06:53 PM UTC
As of 17:55 UTC, our Engineering team has resolved the timeouts affecting the Cloud Control Panel and API. The issue was caused by a temporary overload on our infrastructure, resulting in 5xx errors for API requests and gateway timeouts for Cloud Control Panel users. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.
Minor January 28, 2026 Kubernetes Clusters and Droplets in FRA1 region 6h 10m FRA1, FRA1
Started Jan 28, 2026, 11:27 AM UTC· resolved Jan 28, 2026, 05:37 PM UTC
- investigating Jan 28, 2026, 11:27 AM UTC
Our Engineering team is investigating an issue with Kubernetes clusters in the FRA1 region. During this time, subset of users may experience an issue while provisioning Kubernetes clusters and mounting volumes. Additionally, users may also notice the droplet events appearing to be stuck or delayed in this region. We apologize for the inconvenience and will share an update once we have more information.
- identified Jan 28, 2026, 01:30 PM UTC
Our Engineering team has identified the root cause of the issue impacting Kubernetes clusters and Droplet events in the FRA1 region and is actively working on a fix. In the meantime, users may continue to experience issues. We appreciate your patience and will share updates as more information becomes available.
- monitoring Jan 28, 2026, 02:47 PM UTC
Our Engineering team has implemented a fix to address the issue affecting Kubernetes clusters and Droplet events in the FRA1 region and is actively monitoring the situation. Customers should no longer experience issues provisioning Kubernetes clusters or mounting volumes. We will provide an update as soon as the issue is fully resolved.
- resolved Jan 28, 2026, 05:37 PM UTC
Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. All services should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.