Sep 29, 13:30 UTC
Resolved - From 05.45 to 9.20 UTC, our Engineering team observed a Networking issue in the SFO3 and AMS3 region related to DDoS mitigation workflows. During this time, a subset of Droplets remained in protective filtering longer than intended due to a monitoring issue in AMS3 that caused a small number of IPs to stay blocked incorrectly. Users should no longer be experiencing these issues.

We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.

Sep 30, 14:00 UTC
Completed - The scheduled maintenance has been completed.

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

Sep 28, 16:04 UTC
Scheduled - Start: 2025-09-30 11:00 UTC
End: 2025-09-30 14: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 SFO3 region.

Expected impact:

We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. We will endeavor to keep this to a minimum for the duration of the change.

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