Sep 29, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 29, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 27, 16:11 UTC
Scheduled - Start: 2025-09-29 17:00 UTC
End: 2025-09-29 20:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the LON1 region.

Expected impact:

These changes are designed and tested to be seamless. We do not expect any customer impact during the mentioned timeframe. If an unexpected issue arises, there could be a temporary loss of connectivity for Droplets and its dependent services, such as Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, in the LON1 region. We will endeavor to minimize any such impact.

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

Sep 28, 04:54 UTC
Resolved - Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region after monitoring. Users should be able to access droplets and all other resources without any issues.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Sep 27, 19:39 UTC
Monitoring - The network connectivity issue affecting the BLR1 region, which was caused by a broader internet issue, has been mitigated. Network accessibility in the region has improved, and users should already experience better performance when accessing Droplets and other services. We are closely monitoring the situation to ensure stability.

We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Sep 27, 14:29 UTC
Investigating - Our Engineering team is still observing intermittent issues impacting network connectivity in the BLR1 region. This stems from a broader Internet issue impacting the BLR1 region. As a result, users may still continue to experience packet loss/latency, timeouts, and related issues with Droplet-based services in this region, including Droplets, LBaaS, Managed Kubernetes, and Managed Database. Our Engineering team is actively investigating the issue.

We will post an update as soon as additional information is available.

Sep 27, 13:58 UTC
Monitoring - The network connectivity issue impacting the BLR1 region has been mitigated. Users should no longer experience packet loss/latency, timeouts, and related issues with Droplet-based services in this region, including Droplets, LBaas, Managed Kubernetes, and Managed Database.

We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Sep 27, 13:19 UTC
Investigating - Our Engineering team is investigating an issue impacting networking connectivity in BLR1 region with upstream provider. Users may experience network connectivity loss to Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters.

We apologize for the inconvenience and will share an update once we have more information.

Sep 26, 10:40 UTC
Resolved - Our Engineering team has resolved the performance issue affecting Spaces in the FRA1 region. From approximately 08:02 UTC - 09:40 UTC, customers may have experienced slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API, or Container Registry. 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.

Sep 26, 10:25 UTC
Monitoring - Our Engineering team has implemented a fix to address the performance issue affecting Spaces in the FRA1 region and is monitoring the situation. Customers should no longer experience slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API, and Container Registry access.

We will post an update as soon as the issue is fully resolved.

Sep 26, 09:47 UTC
Investigating - Our Engineering team is investigating a performance issue affecting Spaces in the FRA1 region. During this time, customers may experience slow performance or limited availability when accessing Spaces or its objects via the Control Panel or API, and Container Registry access may also be affected.

We apologize for the inconvenience and will share an update once we have more information.

Sep 24, 19:07 UTC
Resolved - Our Engineering team has confirmed that the issue affecting .space domains has been resolved, and customers should now be able to access their .space domains successfully.

If you continue to experience any issues, please open a support ticket for assistance.

Sep 24, 15:10 UTC
Identified - Our Engineering team has identified issues affecting .space domains. As a result, some customers may be unable to access their websites, and zone files may not appear in dig results. The engineers have confirmed that this is an issue with the registry and have informed upstream providers.

We apologize for the inconvenience and will provide updates as soon as more information is available.

Sep 20, 09:05 UTC
Resolved - Our Engineering team has resolved the issue that was affecting the ability to access and manage the Managed Databases and App Platform in the Cloud Control Panel. Users should now no longer experience slowness, timeouts, or errors when interacting with Managed Databases or App Platform services. All operations should be functioning normally.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Sep 20, 02:30 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue that was resulting in the degradation of the Managed Database and App platform deployment in the Cloud Control Panel.

During this time, users should no longer experience slowness issues with Managed Database and App Platform, and any other previously mentioned timeouts and errors.

We will post an update as soon as the issue is fully resolved.

Sep 20, 00:42 UTC
Identified - Our Engineering team has identified an issue affecting the ability to access and manage the Managed databases and App platform in the Cloud Control Panel.

While there is no impact on data-plane availability, Users may experience some issues like UI taking a while to load, request timeouts, some delays in App platform deployment for apps that have databases, and some API errors.

Our Engineering team is already working on this issue for the resolution. We apologize for the inconvenience and will share an update once we have more information.

Sep 15, 17:20 UTC
Resolved - From 14:29 to 16:01 UTC, our Engineering team identified an issue with the Droplet Create page in our Cloud Control Panel. During this time, users would have experienced issues with accessing the Droplet Create page at https://cloud.digitalocean.com/droplets/new. Our team has fully resolved the issues, and as of 16:01 UTC, all services are operating normally.

We apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account.

Sep 12, 19:33 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue with the upstream provider. Users should now be able to deploy to App Platform and manage their Spaces Buckets as normal.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Sep 12, 19:14 UTC
Monitoring - Our Engineering team has identified that the ongoing issue with the upstream provider is also impacting DigitalOcean Spaces. They continue to monitor the ongoing issue with the upstream provider impacting DigitalOcean Spaces and App Platform services.

Improvements are being seen with lower error rates and latency for App Platform deployments as well as for fetching Spaces endpoints.

We apologize for the inconvenience and will share further updates in the due course.

Sep 12, 18:54 UTC
Investigating - Our Engineering team is aware of an upstream provider issue that is causing impact to some DigitalOcean services. More details are being gathered.

At this time, users may experience delayed App Platform deployments.

We apologize for the inconvenience and will provide another update as soon as possible.

Sep 15, 12:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 15, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 12, 11:02 UTC
Scheduled - Start: 2025-09-15 10:00 UTC
End: 2025-09-15 12:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the NYC1 region.

Expected impact:

While no service disruption is expected during the scheduled maintenance window, there is a low risk of hardware failure associated with the activity. In such a scenario, customers may experience brief interruptions to network traffic within the affected region. If triggered, our Engineering teams will respond immediately to isolate and mitigate the impact.

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

Sep 12, 02:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 11, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 9, 15:41 UTC
Scheduled - Start: 2025-Sep-11 02:00 PM UTC
End: 2025-Sep-12 02:00 AM UTC

During the above window, our Engineering team will be performing power maintenance in our SFO2 data center cages to ensure infrastructure stability.

Expected Impact:

All devices run on redundant power. We do not expect any customer impact during this maintenance. If the redundant power feed experiences an issue during the course of the maintenance (which is unlikely), customers could see impact to existing resources housed in the affected cages, including Droplets, rDNS, and Object Storage. We will post updates if any unexpected outage occurs.

To help ensure a safe operation, we've temporarily reduced Droplet capacity in our SFO2 region. Customers who deploy Droplets in SFO2 may see some sizes unavailable or run into capacity errors for large deployments. This is temporary, so if you do encounter an error, we encourage you to try to deploy once more once the maintenance is complete.

Our engineering and operations teams are onsite and will be monitoring affected systems closely throughout the maintenance. Emergency notifications will be sent promptly if any critical impacts arise.

We appreciate your understanding as we work to resolve this situation as quickly and safely as possible.

If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Sep 8, 15:22 UTC
Resolved - Our Engineering team investigated reports of Droplets becoming unresponsive. This issue was found to be caused by guest-level kernel hangs, and affected Droplets required a power cycle to restore functionality.

Upon further investigation, this was identified to be an upstream kernel issue with Ubuntu 20.04 running kernel version 5.4.0-122-generic. This kernel version has exhibited stability problems that can lead to Droplets becoming unresponsive intermittently. Customers running Ubuntu 20.04 with kernel 5.4.0-122-generic are advised to upgrade to a newer kernel version using the commands below:

sudo apt update
sudo apt upgrade linux-virtual

This problem is fixed with the newer kernel 5.4.0-123.139. The recommended option is to migrate to a more recent and fully supported OS version, such as Ubuntu 24.04, to ensure continued system stability and support. The affected customers can take the recommended steps above to avoid further impact.

We appreciate your patience and apologize for any inconvenience caused.

Sep 8, 08:41 UTC
Investigating - Our Engineering team is actively investigating an issue causing some Droplets to become unresponsive due to guest-level errors. Affected users may find that their Droplets intermittently hang, requiring a power cycle to restore access.

We've identified that this behavior is occurring on a subset of Droplets running Ubuntu 20.04. The standard support for Ubuntu 20.04 has ended, which may contribute to the observed behavior in certain configurations. We recommend affected customers consider updating their Droplets to a currently supported operating system, such as Ubuntu 24.04, to ensure continued stability and support.

We apologize for the inconvenience and appreciate your patience as we continue to investigate and work toward a resolution. We will share further updates as more information becomes available.

Sep 16, 17:39 UTC
Resolved - Our Engineering team has confirmed that our upstream providers have been able to mitigate the network connectivity issues in the BLR1 and SGP1 regions.

At this time users should not experience intermittent degraded performance and timeout errors with Droplet-based services to and from these regions.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Sep 15, 16:59 UTC
Update - Our Engineering team has observed significant improvements with the network latency and packet loss during peak hours today. This is a result of our upstream providers making some routing adjustments. We are carefully monitoring the network performance for the next 24 hours.

We will communicate any further relevant information as we have it. We apologize for the inconvenience in the meantime.

Sep 8, 22:29 UTC
Update - Significant submarine cable outages continue to impact multiple network carriers on the Indian subcontinent, with increased latency and packet loss to our BLR1 region occurring sporadically throughout the day.

On a positive note, our upstream providers have worked diligently over the past couple of days to minimize the impact of the loss of submarine capacity. As a result, we are now mainly seeing service degradation during the busier evening peak hours only.

For the moment, we have no updates to provide regarding when the situation might improve. Repair times for submarine cables are typically on the order of weeks or months. However, further short-term improvements may still be possible as upstream carriers work to re-balance traffic where feasible.

Separately, we continue to look into potential avenues for additional mitigations and will keep our customers aprised as we make progress in this area.

We apologize for the ongoing inconvenience created by this extraordinary situation and thank our customers for their patience.

Sep 6, 23:02 UTC
Monitoring - Our Engineering team confirms that multiple subsea cable cuts are impacting connectivity in the APAC region, which also affects traffic to Europe and the U.S. East Coast.

Traffic is being rerouted through alternate paths to maintain service continuity. As a result, users may experience higher latency and intermittent connectivity issues.

Our engineering team continues to monitor the situation closely and is working with upstream providers as repair efforts progress. We will share further updates as they become available.

We apologize for the disruption and appreciate your patience.

Sep 6, 18:49 UTC
Update - We are continuing to work on a fix for this issue.

Sep 6, 18:44 UTC
Update - Our Engineering team has implemented changes to optimize traffic routing in the BLR and SGP regions, addressing networking issues stemming from our upstream providers, which are affected by major submarine cable outages in the APAC region. Despite these adjustments, users may still encounter intermittent packet loss or connectivity issues when accessing resources in the affected areas. We are working with our upstream vendors to gain further insights and achieve a definitive resolution.

We apologize for any inconvenience caused.

Sep 6, 16:48 UTC
Identified - Our Engineering team has identified the cause of the issue impacting networking connectivity in BLR1 region to be with our upstream provider.

Our team is actively working on remediation steps. We will post an update as soon as we have more information.

Sep 6, 16:13 UTC
Investigating - Our Engineering team is currently investigating an issue impacting networking in BLR1 region. Users may experience network connectivity loss to Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters.

We apologize for the inconvenience and will share an update once we have more information.

Sep 5, 19:42 UTC
Resolved - From 18:53 to 19:15 UTC, our Engineering team identified an issue with the public Droplet API, resulting in difficulties in creating, accessing and listing Droplets via the Cloud Control Panel or API. Autoscaler and LBaaS APIs were also affected. Our team has fully resolved the issues, and as of 19:15 UTC, all services are operating normally.
We apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account

Sep 3, 11:30 UTC
Completed - The scheduled maintenance has been completed.

Sep 3, 07:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 2, 22:10 UTC
Scheduled - Start: 2025-09-03 07:30 UTC
End: 2025-09-03 11:30 UTC

During the above window, our Engineering team will be performing maintenance on the Managed Databases API to enhance security, improve access control and enable better auditing and compliance. Please note that existing Databases and workloads will continue to run normally and will not be impacted.

Expected Impact:

We don’t anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally and will not be impacted.

In the event of an unexpected issue occurs, only control plane actions like provisioning new clusters, modifying configurations, and fetching database details will be impacted. The data-plane for connecting and running queries on your databases will be unaffected.

If an unexpected issue arises, we will endeavor to keep any impact to a minimum and may revert if required.

If you have any questions related to this event, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Aug 29, 15:45 UTC
Resolved - From 14:24 to 14:41 UTC, our Engineering team identified issues affecting Block Storage Volumes in the NYC1 region. During this time, users may have experienced difficulties processing requests on Volumes. It was observed that this might have impacted Kubernetes clusters in the NYC1 region as well. Our team has fully resolved the issues, and as of 14:42 UTC, all services are operating normally.

We apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account

Aug 26, 20:01 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue impacting Droplet creation in all regions. Users can now create Droplets without any issues.

We appreciate your patience while we worked to fix this issue. If you continue to experience any problems, please open a ticket from your account for further investigation.

Aug 26, 19:33 UTC
Monitoring - Our Engineering team has identified the reason behind the failed Droplet creates and implemented a fix to resolve the issue. Users should now be able to create Droplets.

We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.

Aug 26, 18:30 UTC
Investigating - Our Engineering team is currently investigating an issue with Droplet creation in multiple regions. This is only affecting new accounts at this time. Existing users are not impacted.

Users with new accounts may experience an elevated failure rate when attempting to create Droplets during this time.

We apologize for the inconvenience and will share an update once we have more information.

Aug 22, 04:54 UTC
Completed - Our Engineering team has confirmed that the issue caused by the unexpected power event has been fully resolved. Droplet connectivity in SFO2 should now be completely restored, and events like powering on/off should work as expected.

We apologize for any inconvenience caused. If you continue to experience any issues, please open a support ticket from within your account.

Aug 22, 01:25 UTC
Update - Our Engineering team has mitigated the issue with the unexpected power event and will continue to monitor this closely. Droplet connectivity in SFO2 should be restored, and events, such as powering on/off, should complete successfully now.

We apologize for the inconvenience this has caused. We will post updates if any further unexpected issues arise, and once this maintenance is fully completed. Thank you for your patience.

Aug 22, 00:35 UTC
Update - Our Engineering team is still working on the issue with some nodes in SFO2 going offline. Some users may still experience connectivity and event processing issues in SFO2.

We apologize for the inconvenience. We will post an update once we've confirmed that this issue is resolved.

Aug 21, 23:29 UTC
Update - During this maintenance, an unexpected power issue has occurred, which has caused multiple nodes to go down. Some customers with Droplets in SFO2 may notice that their Droplets are experiencing connectivity and event processing issues.

Our Engineering team is working to resolve this immediately, we will post an update here once we have more information.

Aug 21, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Aug 21, 20:50 UTC
Scheduled - We are initiating an emergency power maintenance in one of our data center cages. This maintenance is critical and must be performed immediately to ensure infrastructure stability.

Expected Impact:

All devices run on redundant power. We do not expect any customer impact during this maintenance. If the redundant power feed experienced an issue during the course of the maintenance (which is unlikely), customers could see impact to existing resources housed in the affected cages, including Droplets, rDNS, and Object Storage. We will post updates if any unexpected outage occurs.

To help ensure a safe operation, we've temporarily reduced Droplet capacity in our SFO2 region. Customers who deploy Droplets in SFO2 may see some sizes unavailable or run into capacity errors for large deployments. This is temporary, so if you do encounter an error, we encourage you to try to deploy once more once the maintenance is complete.

Our engineering and operations teams are onsite and will be monitoring affected systems closely throughout the maintenance. Emergency notifications will be sent promptly if any critical impacts arise.

We appreciate your understanding as we work to resolve this situation as quickly and safely as possible.

If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Aug 15, 15:42 UTC
Resolved - From 14:40 UTC to 14:52 UTC, users may have experienced errors when trying to use the API or while accessing our Cloud Control Panel at https://cloud.digitalocean.com.

Our Engineering team has implemented a fix and confirmed full resolution of the issue. Users should be able to access the API and Cloud Control Panel without issue now.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Aug 13, 09:30 UTC
Resolved - As of 18:45 UTC, our Engineering team has resolved the issues with OpenAI rate limits that were affecting certain DigitalOcean services. The problem, which began at approximately 09:30 UTC, caused errors (429s) for Agents using OpenAI models for serverless inference.

Systems Affected:

Serverless inference
Evaluations

Technical Details: The issue was caused by exceeding OpenAI rate limits, which resulted in 429 errors for OpenAI models.

Duration: The incident lasted for approximately 9 hours, from 09:30 UTC to 18:45 UTC. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve the issue. If you continue to experience problems, please open a ticket with our Support team.

Aug 7, 23:45 UTC
Resolved - Our Engineering team identified and resolved an issue with the doctl v1.136.0 that was affecting automations and integrations, including App Platform and GitHub Action.

Users with the affected version of doctl may see 404 errors blocking their pipeline. The issue was caused by missing binaries in the release. The broken release has been deleted. Automations depending on doctl should now function as expected.

We apologize for the inconvenience. The new release shall be published soon.

Jul 30, 02:04 UTC
Resolved - Our Engineering team has implemented a fix for the issue that was preventing users from submitting or viewing tickets through our Support Ticket Portal. At this time, all users should be able to access the portal and manage tickets normally via https://cloudsupport.digitalocean.com/s/.

Additionally, any previously submitted tickets that were affected by this issue have now been successfully routed to our Support Team, who will be addressing them as quickly as possible.

We sincerely apologize for the inconvenience and appreciate your patience while we worked to resolve this issue.

Jul 30, 01:42 UTC
Identified - Our Engineering team has identified the root cause of the issue affecting the ability to submit or view tickets through our Support Ticket Portal. They are actively working on implementing a fix.

We will share another update as soon as more information becomes available. Thank you for your continued patience and understanding as we work to resolve this issue.

Jul 30, 01:26 UTC
Investigating - Our Engineering team is investigating an issue with our DigitalOcean Support Ticket Portal. At this time, users may not be able to submit new tickets or view currently opened tickets at https://cloudsupport.digitalocean.com/s/.

We apologize for the inconvenience and will share an update once we have more information.