Day: December 10, 2024

Dec 11, 01:30 UTC
Completed – The scheduled maintenance has been completed.

Dec 10, 19:30 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 10, 19:26 UTC
Scheduled – We are reaching out again to inform you that the Network maintenance in AMS3 region which was previously scheduled to start on 2024-12-10 at 12:00 UTC has been rescheduled to the following window:

Start: 2024-12-10 19:30 UTC
End: 2024-12-11 01:00 UTC

We apologize for any inconvenience this short notice causes and thank you for your understanding. You may find the initial maintenance notice along with a description of any expected impact related to this work included at the bottom of this message.

Expected impact:

During the maintenance window users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services including Droplets, Managed Kubernetes, Load Balancers, Container Registry, 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

Dec 11, 00:56 UTC
Resolved – From 16:10 UTC to 22:46 UTC, users may have experienced issues while executing Managed Database CRUD Operations.

Our Engineering team has confirmed the full resolution of the issue impacting Managed Database CRUD Operations, and all systems are now operating normally.
Users may safely resume operations, including upgrades, resizes, forking, and ad-hoc maintenance patches.

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

Dec 10, 22:54 UTC
Monitoring – Our Engineering team has implemented a fix for the issue impacting Managed Database CRUD Operations. The team is monitoring the situation, and we will share an update once this is fully resolved.

Dec 10, 22:44 UTC
Identified – Our Engineering team has identified the cause of the issue that is impacting Managed Database CRUD Operations and is actively working on a fix.

To avoid potential downtime, we continue to ask users to refrain from performing operations that trigger node rotations, such as upgrades, resizes, forking, and ad-hoc maintenance patches.

Existing database clusters remain unaffected as long as no node rotation occurs due to DNS issues, and all other services are functioning as expected.

We apologize for any inconvenience caused and appreciate your patience as we work diligently to address the situation. Further updates will be shared as soon as they become available.

Dec 10, 20:11 UTC
Update – During our investigation, we identified that operations triggering node rotation, such as upgrades, resizes, forking and ad-hoc maintenance patches, may also be impacted. To prevent potential downtime, we recommend avoiding these operations until the issue is fully resolved.

We apologize for the inconvenience and appreciate your patience as we work to address the situation.

Dec 10, 19:22 UTC
Investigating – Our Engineering team is investigating an issue causing Managed Database clusters to take longer than usual to be created. Our team is currently assessing the root cause and working to resolve the issue as quickly as possible.

Existing database clusters are not affected, and all other services are operating normally.

We apologize for any inconvenience this may cause and will share an update as soon as we have more information.