Oct 17, 04:28 UTC
Resolved - Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.

Oct 17, 03:56 UTC
Monitoring - Our Engineering team has implemented the fix to resolve the IPv6 networking issues in multiple regions. Users should no longer have issues connecting to via IPv6 to their Droplets.

We will continue to monitor the situation, and we will post an update once we've confirmed complete resolution.

Oct 17, 02:52 UTC
Identified - Our Engineering team has identified the issue and are implementing a fix. Our team has resolved the IPv6 connectivity issue in FRA1 and are monitoring the situation.

In addition, it was discovered that the NYC1, and SFO2 regions were affected by this issue as well, and our team is currently working to resolve the issue in those regions. To summarize, users in the regions of AMS2, SGP1, NYC1, and SFO2 may still experience connection issues via IPv6.

We are rapidly working on a fix. We will share more information once available.

Oct 17, 00:44 UTC
Update - While investigating this issue, our Engineering team has noticed that the issue is occurring in SGP1 as well. Users in SGP1 may also experience IPv6 connectivity issues at this time.

We are working to resolve this issue as quickly as possible. We will post updates as soon as we have more information.

Oct 17, 00:19 UTC
Investigating - Our Engineering team is investigating an issue affecting IPv6 connectivity in FRA1, and a small subset of users in AMS2. At this time, users may experience issues connecting to IPv6-enabled resources.

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

Oct 15, 14:25 UTC
Resolved - Our Engineering team has resolved the issue affecting the creation of NVDIA GPU nodes on new Kubernetes clusters. Users will no longer encounter issues when creating NVDIA GPU nodes on new Kubernetes clusters.

If you continue to experience any issues, please open a support ticket. We sincerely apologize for the inconvenience caused and appreciate your understanding.

Oct 15, 12:18 UTC
Identified - Our Engineering team has identified the issue affecting the creation of GPU nodes on new Kubernetes clusters. Users may continue to experience difficulties when attempting to create GPU nodes on new Kubernetes clusters.

Our team is actively working to resolve the issue and will provide an update as soon as we have more information. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 15, 11:29 UTC
Investigating - Our Engineering team has identified an issue impacting creation of GPU nodes on new Kubernetes clusters. During this time, you will not be able to launch a new Kubernetes cluster with NVIDIA GPU nodes. Existing workloads are not impacted. We apologize for the inconvenience and will share an update once we have more information.

Oct 14, 22:18 UTC
Resolved - Our Engineering team has confirmed the full resolution of the issue with Managed Database 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.

Oct 14, 19:00 UTC
Monitoring - Our engineering team has implemented a fix for the issue that affected a subset of customers who were unable to provision Managed Database Clusters, including MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka.

We will continue to closely monitor the situation to ensure full stability and will provide an update once the issue is fully resolved.

Oct 14, 17:10 UTC
Identified - Our engineering team has identified the cause of the issue affecting a subset of our customer who were unable to provision Managed Database Clusters including MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka.

Our team is actively working on remediation steps and will share an update as soon as more information becomes available.

Oct 14, 11:56 UTC
Investigating - Our engineering team is investigating an ongoing issue affecting Managed Database Clusters. Currently, users may encounter errors when creating MySQL, PostgreSQL, Valkey, OpenSearch, and Kafka clusters through the Cloud Control Panel or API requests.

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

Oct 13, 14:45 UTC
Resolved - Our Engineering team has confirmed that the issue affecting Spaces access in the FRA1 region has been fully resolved.

Users should now be able to list and access their Spaces objects without any errors. We appreciate your patience and understanding while we worked to restore normal service.

If you experience any further problems or have any questions, please open a support ticket within your account.

Oct 13, 13:38 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Spaces access in the FRA1 region. We are observing recovery, and users should now be able to list and access their Spaces objects without encountering InvalidAccessKeyId errors.

We will continue to closely monitor the situation to ensure full stability and will provide an update once the issue is fully resolved.

Oct 13, 11:23 UTC
Investigating - Our Engineering team is currently investigating an issue affecting Spaces access in the FRA1 region.

During this time users trying to access or list the Spaces objects will be experiencing InvalidAccessKeyId errors.

This issue appears to be isolated to the FRA1 region. Our engineering team is actively investigating the root cause. We will provide an update as soon as more information becomes available.

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

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

Oct 12, 22:08 UTC
Scheduled - Start: 2025-10-14 22:00 UTC
End: 2025-10-15 00: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:

During the maintenance window, we do not anticipate any downtime for Droplets or Droplet related services. If an unexpected issue arises, users may experience brief delays or failures in event processing including Droplets, Managed Kubernetes, Load Balancers, Container Registry, Public API, Cloud Control Panel and App Platform. 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

Oct 10, 23:58 UTC
Resolved - Our Engineering team has resolved the issue affecting multiple services, including the Cloud Control Panel and API.

Users should now be able to access their accounts and use the API without any errors.

If you still encounter any issues, please launch a ticket with our Support team.

Oct 10, 22:29 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the Cloud Control Panel, API, and related services. We are observing recovery, and users should now be able to access their accounts and use the API without errors.

We are continuing to monitor the situation closely and will provide an update once full resolution is confirmed.

Oct 10, 21:56 UTC
Investigating - Our Engineering team is investigating an issue impacting multiple services including the Cloud Control Panel and API.

Users may encounter errors when accessing their accounts or using the API.

We are actively working to resolve this issue and will provide updates as soon as more information becomes available.