Sep 26, 02:45 UTC
Resolved - From 22:25 to 22:50 UTC, users may have experienced network connectivity issues with all DigitalOcean services deployed in the SFO3 region. Additionally, from 22:25 until 01:40 UTC, users may have encountered network connectivity issues affecting their Managed Kubernetes clusters in the SFO3 region.

Our Engineering team has fully resolved the issues impacting connectivity in the region, 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 caused.

Sep 26, 02:15 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue affecting networking connectivity with Managed Kubernetes clusters in the SFO3 region and is closely monitoring the situation. We will provide an update as soon as the issue is fully resolved.

Sep 26, 01:27 UTC
Identified - Our Engineering team has identified the cause of the networking connectivity issues with Managed Kubernetes clusters in the SFO3 region and is actively working on rolling out a fix. Once we have additional information, we will share another update.

Sep 26, 00:38 UTC
Update - We are continuing to investigate the network connectivity issue with Managed Kubernetes clusters.

During this investigation, we have also identified an earlier period of network connectivity disruption affecting all services in the region, from 22:25 to 22:50 UTC.

At this time, some Managed Kubernetes clusters may continue experiencing network connectivity issues, but all other services in the region should be accessible as normal.

Sep 25, 23:34 UTC
Investigating - Our Engineering team is currently investigating issues with network connectivity for Managed Kubernetes clusters in the SFO3 region. During this time, some users may experience difficulties connecting to their Managed Kubernetes clusters, or connecting to other services from their clusters.

We apologize for the inconvenience and will provide an update as soon as we have more information.

Sep 25, 22:59 UTC
Resolved - Our Engineering team has identified and resolved an issue that impacted the ability to resize Droplets via both the API and UI from 18:15 until 21:55 UTC. During this time, users might have experienced errors when attempting to resize their Droplets through the API or the UI.

Additionally, in an effort to resolve the issue with resizes, a secondary issue affected all event processing and some API calls for Droplets and related services from 21:50 until 22:00 UTC.

Swift action was taken by our Engineering team to restore full functionality, and now everything is operating normally.

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

Sep 25, 16:10 UTC
Resolved - From 00:01 to 15:15 UTC, users may have experienced errors when attempting to resize their MongoDB Managed Database clusters.

Our Engineering team has confirmed the full resolution of issue. Users should now be able to resize their MongoDB clusters normally.

If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.

Sep 25, 15:36 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issues impacting the resizing of Managed Database Clusters. Users should now be able to resize their existing MongoDB clusters without any issues.

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

Sep 25, 15:14 UTC
Investigating - Our Engineering team is investigating an issue with MongoDB Managed Databases. At this time, users may experience errors while attempting to resize their existing MongoDB clusters.

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