Cloud Service Status

Description

We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.

Details

Description

We are investigating issues with AWS services in the ME-CENTRAL-1 Region.

Details

Description

<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>12:01</var> UTC</small><br><strong>Resolved</strong> - The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 00:08am UTC & 11:46am UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue.<br /><br />We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding.<br /><br />However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>11:14</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has deployed a fix to resolve the issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. We are actively monitoring the situation to ensure stability and will provide an update once the incident has been fully resolved. Thank you for your patience and we apologize for the inconvenience.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>10:32</var> UTC</small><br><strong>Investigating</strong> - Our engineers are currently investigating an issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. During this time, some users may experience delay when creating new App Platform apps or deploying existing apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.</p>

Details

Affected Regions

Status Timeline

Description

<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>14:14</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has implemented a fix, the issues impacting Gradient AI Platform have been resolved. All agents are back up and healthy. Service has been fully restored.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>14:04</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and services have been restored. We are continuing to monitor the system to ensure stability. We will provide further updates if needed.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>11:05</var> UTC</small><br><strong>Update</strong> - We've identified the issue and are actively working to restore the affected services. We're making steady progress and closely monitoring the situation. Further updates will be shared as they become available.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>09:51</var> UTC</small><br><strong>Identified</strong> - We’ve identified the issue and are currently working on restoring the services. We’ll continue to provide updates as progress is made.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>08:50</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating issue affecting the accessibility of agents and services on the Gradient AI Platform. Users may experience failures or unresponsiveness when attempting to use these features. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>19:49</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has implemented a fix, the issues impacting model availability and performance have been resolved. All models, including those previously degraded, are back up and healthy. Service has been fully restored.</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating reports of Gradient AI model availability issues impacting multiple models. Users may experience issues with models availability, including Llama3.1-8b and Qwen3-32b, as well as embedding models such as GTE Large (v1.5), All-MiniLM-L6-v2, Multi-QA-mpnet-base-dot-v1, and Qwen3 Embedding 0.6B. <br /><br />Additionally, Guardrails are not available, affecting associated agents, and users attempting to run inference on the Llama3.3-70b model will see degraded performance. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>17:39</var> UTC</small><br><strong>Resolved</strong> - From 16:14 to 16:38 UTC, Our Engineering team observed an issue impacting Cloud control panel and API. During this time, users may experienced errors when trying to access the Cloud control panel and when trying to use the API. Our team has fully resolved the issues as of 16:38 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.</p>

Details

Description

<p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>03:31</var> UTC</small><br><strong>Resolved</strong> - The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally.<br />Contact support if issues persist.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>02:55</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue related to all Gradient AI agents and serverless inference that require BYOK Anthropic modles.<br />Impacted users may experience degraded performance.<br />We will provide an update as soon as possible</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'>14</var>, <var data-var='time'>01:47</var> UTC</small><br><strong>Resolved</strong> - As of 23:00 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments.<br /><br />Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.<br /><br />However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>23:39</var> UTC</small><br><strong>Monitoring</strong> - After working with our upstream provider, our Engineering team has implemented a fix to resolve the issue that was causing delays in the deployment of new apps, and they are currently monitoring the situation. <br /><br />During this time, users should no longer experience issues with creating new apps and all the stalled creation events should provision completely.<br /><br />We will post an update as soon as the issue is fully resolved.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>22:01</var> UTC</small><br><strong>Identified</strong> - Our Engineering team is starting to see delays once again with new App Platform deployments. During this time, users may still experience delays with deploying new apps. We're working with our upstream provider to resolve the issue.<br /><br />We again apologize for the inconvenience. We will post further updates once we have more information.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>21:30</var> UTC</small><br><strong>Monitoring</strong> - Starting at 20:40 UTC, users may have seen delays with deploying new apps on App Platform. <br /><br />At this time, our Engineering team is seeing signs of recovery, and users should be able to deploy new apps without issue. We're currently monitoring the situation to ensure full recovery.<br /><br />We apologize for the inconvenience. We'll post an update once the issue has been confirmed to be resolved.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>16:35</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed the resolution of the issue impacting DNS timeouts for newly provisioned Managed Kubernetes nodes. At this time all cluster 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.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>13:55</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to address the issue causing DNS timeouts for newly provisioned Managed Kubernetes nodes. Further investigation has confirmed that this issue primarily affected customers utilizing a NAT Gateway within their VPC and running a VPC-native cluster. We are actively monitoring the situation to ensure overall stability.<br /><br />We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>12:32</var> UTC</small><br><strong>Identified</strong> - Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, Only customers who run a NAT Gateway in their VPC and a VPC-native clusters are affected and may experience DNS timeouts. We apologize for the inconvenience and will share an update once we have more information.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>11:26</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, new nodes may experience DNS timeouts, which could temporarily affect cluster services. We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>19:23</var> UTC</small><br><strong>Resolved</strong> - From 17:50 to 19:06 UTC, Our Engineering team observed an issue with mirrors.digitalocean.com. During this time, users may have experienced errors when trying to update packages on Debian and Ubuntu Images. Our team has fully resolved the issues as of 19:06 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.</p>

Details

Description

We are investigating increased error rates in the EU-CENTRAL-2 Region.

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>21:22</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team identified an issue affecting the App Platform. During the incident, users may have experienced HTTP 522 (Connection Timed Out) errors when accessing their apps. The issue seems to be resolved now.<br /><br />We apologize for the inconvenience caused. If you continue to experience any related errors, please contact our Support team by opening a ticket at https://www.digitalocean.com/support/contact/.</p>

Details

Description

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>01:12</var> UTC</small><br><strong>Resolved</strong> - As of 00:22 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments.<br /><br />Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.<br /><br />However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>00:32</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. <br /><br />We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>23:28</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is currently investigating an issue impacting App Platform deployments. During this time, users may experience a delay or failure when deploying new and existing App Platform apps. <br /><br />We apologize for any inconvenience, and we'll share more information as it becomes available.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>01:52</var> UTC</small><br><strong>Resolved</strong> - From 19:57 UTC to 01:03 UTC, customers may have experienced connectivity issues between Internal Load Balancers and their associated target droplets, which could have resulted in service disruption or traffic routing failures.<br /><br />Our Engineering team has confirmed full resolution of the issue, and Internal Load Balancers should now be functioning normally.<br /><br />If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience caused.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>01:19</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented mitigation measures to address the connectivity issues affecting Internal Load Balancers and their associated target droplets. We are actively monitoring the situation to ensure stability and to prevent any recurrence.<br /><br />We will provide a further update once we confirm the issue is fully resolved.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>00:23</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue affecting Internal Load Balancers. Customers may experience connectivity loss between Internal Load Balancers and their associated target droplets.<br /><br />We apologize for the inconvenience and will share an update as soon as more information becomes available.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>15:55</var> UTC</small><br><strong>Completed</strong> - This scheduled maintenance is now complete across all regions. Thank you for your patience and understanding throughout this process.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>13:05</var> UTC</small><br><strong>Scheduled</strong> - Phase 2 maintenance is complete. Phase 3 is scheduled to begin at March 06, 11:00 UTC.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>13:03</var> UTC</small><br><strong>Scheduled</strong> - Phase 1 maintenance is complete. Phase 2 is scheduled to begin at March 05, 10:00 UTC.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>10:44</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-03-03 10:00 UTC<br />End: 2026-03-06 13:00 UTC<br /><br />Hello,<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in all regions. Please note that the existing infrastructure will continue running without issue.This maintenance will be carried out in three phases as outlined below:<br /><br />March 03, 10:00 to 13:00 UTC<br />March 05, 10:00 to 13:00 UTC<br />March 06, 11:00 to 13:00 UTC<br /><br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.</p>

Details

Status Timeline

Description

<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>13:20</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-03-02 13:00 UTC<br />End: 2026-03-02 16:00 UTC<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in SFO2 and SFO3. Please note that the existing infrastructure will continue running without issue.<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.</p>

Details

Affected Regions

Status Timeline

Description

Vertex AI Gemini API customers experienced increased error rates when accessing the global endpoint.

Details

Description

<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>22:23</var> UTC</small><br><strong>Resolved</strong> - Issue resolved.<br />Cause: A few requests made to the Llama 3.3-70B model caused issues.<br />Impact: Intermittent errors when interacting with the model through serverless inference and/or with agents created using this model.<br />Contact support if issues persist.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>21:52</var> UTC</small><br><strong>Monitoring</strong> - Fix deployed. Monitoring resources related to the Llama 3.3-70B.<br />Users should no longer experience intermittent errors when making serverless inference requests via APIs and Agents . Awaiting confirmation before closure.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue affecting the Llama 3.3-70B model.<br />Symptoms: Users may encounter intermittent errors when making serverless inference requests via APIs and Agents.<br />Current Status: Our engineering team is actively investigating the issue to determine the root cause.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>04:55</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved. Between approximately 14:30 UTC on the 26th and 00:01 UTC on the 27th, users may have experienced errors when attempting to build or deploy applications using older versions of the Node.js buildpack. A fix has been implemented, and build and deployment operations have been restored to normal.<br /><br />All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.<br /><br />If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>17:14</var> UTC</small><br><strong>Investigating</strong> - As of 14:30 UTC, our Engineering team is investigating reports of build failures on App Platform for customers using older version of the Node.js buildpack. Users may experience errors when attempting to build their applications, resulting in failed deployments.<br /><br />Our Engineering team is working to fix the issue and will share an update once we have more information. In the meantime, as a workaround, we recommend that customers upgrade to the latest version of Node.js build packs. This may help to resolve the build failures and allow for successful deployments. To upgrade, please follow the instructions outlined here:<br /><br />https://docs.digitalocean.com/products/app-platform/how-to/migrate-nodejs-buildpack/<br /><br />We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>15:04</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-26 16:00 UTC<br />End: 2026-02-26 20:00 UTC<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in AMS1, FRA1, and LON1. Please note that the existing infrastructure will continue running without issue.<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.</p>

Details

Affected Regions

Status Timeline

Description

<p><small>Feb <var data-var='date'>25</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>25</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>16:05</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-25 15:00 UTC<br />End: 2026-02-25 18:00 UTC<br /><br />Hello,<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in BLR1 and SGP1. Please note that the existing infrastructure will continue running without issue.<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.<br /><br />Thank you,<br />Team DigitalOcean</p>

Details

Affected Regions

Status Timeline

Description

We are experiencing intermittent missing or delayed EC2 instance and status check metrics in the US-EAST-1 Region. Alarms on delayed or missing metrics may transition into an INSUFFICIENT_DATA state. We are taking multiple parallel paths to mitigate this issue. While underlying resources are not affected by this issue, customers with automated actions based off of delayed or missing metric data may see their automations start. EC2 APIs are not impacted and therefore EC2 AutoScaling will not be affected by this issue.

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>15:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>15:12</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-24 15:00 UTC<br />End: 2026-02-24 17:00 UTC<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in SYD1. Please note that the existing infrastructure will continue running without issue.<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.</p>

Details

Affected Regions

Status Timeline

Description

<p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>21:28</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>09:36</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-24 09:00 UTC<br />End: 2026-02-24 22:00 UTC<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SFO1 region.<br /><br />Expected Impact:<br /><br />These upgrades are designed and tested to be seamless and we do not expect any impact to customer traffic due to this maintenance. If an unexpected issue arises, network traffic for the SFO1 region might be affected for a short period of time. We will endeavor to keep any such impact to a minimum.<br /><br />If you have any questions related to this maintenance, please send us a ticket from your cloud support page.<br /> https://cloudsupport.digitalocean.com/s/createticket</p>

Details

Affected Regions

Status Timeline

Description

We are investigating connectivity issues impacting AWS Direct Connect connectivity to the US-EAST-1 Region.

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>19:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>18</var>, <var data-var='time'>10:16</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-19 19:00 UTC<br />End: 2026-02-20 23:00 UTC<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in NYC3. Please note that the existing infrastructure will continue running without issue.<br /><br />Expected Impact:<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from https://cloudsupport.digitalocean.com/s/createticket. We’re here to help.</p>

Details

Affected Regions

Status Timeline

Description

<p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>18:42</var> UTC</small><br><strong>Resolved</strong> - The issue impacting the visibility of Cloud Panel has been confirmed to be resolved. Between approximately 16:08 PM & 17:56 PM UTC, users may have noticed unusual behavior when accessing the console, performing resizing operations, or experiencing issues with the Cloud Panel visibility. <br /><br />Our team has taken necessary corrective measures to restore the service, and we can confirm that it is now functioning as expected. We sincerely apologize for the inconvenience caused and truly appreciate your understanding throughout this process. <br /><br />However, if you continue to experience any issues, please do not hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>18:05</var> UTC</small><br><strong>Monitoring</strong> - Our team has implemented a fix to address the issue affecting the visibility of the Cloud Panel. We are actively monitoring the situation to ensure overall stability. <br /><br />Users should no longer encounter abnormalities when accessing the console, resizing the Droplet, misalignments within the Cloud Panel, etc. We will provide a further update once the issue is fully confirmed to be resolved.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>17:34</var> UTC</small><br><strong>Investigating</strong> - Our team is currently investigating an issue impacting the visibility of the Control Panel. Users may notice unexpected behavior, such as being prompted for login credentials when accessing the console, being unable to select radio buttons for any plans during resize, columns appearing squished, etc.<br /><br />We apologize for the inconvenience and will share further updates as soon as more information becomes available.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>10:58</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed that the issue impacting the availability of Spaces and the Container Registry in the NYC3 region has been fully resolved. A fix was implemented, and services have been restored. <br /><br />All operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account. <br /><br />Thank you for your patience while we worked to resolve this issue.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>07:36</var> UTC</small><br><strong>Monitoring</strong> - Between 5:34 and 6:32 UTC, our Engineering team identified the issue that was impacting the availability of Spaces and the Container Registry in the NYC3 region. A fix has been implemented to resolve the issue.<br /><br />During this time users may have experienced errors while interacting with Spaces. Additionally, CRUD operations (create, read, update, delete) within the Container Registry may have failed or returned errors during this time.<br /><br />We are now monitoring the platform to ensure services remain stable and operating as expected. We will provide a final update once the issue is fully resolved.<br /><br />If you continue to experience any issues, please contact our Support team.</p>

Details

Affected Regions

Status Timeline

Description

<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>09:24</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed that the issue affecting the Droplet limit increase feature within the Cloud Control Panel has been fully resolved. Requests to increase Droplet limits submitted through the Control Panel are now being processed correctly, and Support tickets are being generated as expected.<br /><br />If you experience any further issues, please contact Support by creating a Support ticket from within your account.<br /><br />Thank you for your patience while we worked to resolve this issue.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>08:37</var> UTC</small><br><strong>Monitoring</strong> - The issue affecting the Droplet limit increase feature within the Cloud Control Panel has been identified and a fix has been implemented.<br /><br />Requests submitted through the Control Panel are now generating Support tickets as expected. Our team is continuing to monitor the system to ensure full functionality and stability.<br /><br />If you experience any further issues with Droplet limit increase requests, please contact Support directly by creating a Support ticket from within your account.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>06:38</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is currently investigating an issue affecting the Droplet limit increase feature within the Cloud Control Panel.<br /><br />At this time requests to increase Droplet limits submitted through the Control Panel are not being processed. Customer submissions to increase limits are not generating support tickets as expected. We are actively working to identify the root cause and restore normal functionality as quickly as possible.<br /><br />If you urgently require a Droplet limit increase, please contact Support directly by creating a Support ticket from within your account.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>19:34</var> UTC</small><br><strong>Resolved</strong> - As of 18:55 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments.<br /><br />Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.<br /><br />However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>19:17</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to address the issue causing delays in App Platform deployments. <br /><br />We are actively monitoring the situation to ensure overall stability. Users may already notice improvements while deploying apps. <br /><br />We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>19:06</var> UTC</small><br><strong>Investigating</strong> - Our engineers are currently investigating an issue impacting new App Platform deployments. <br /><br />During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. <br /><br />We apologize for any inconvenience, and we'll share more information as it becomes available.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>12:06</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed the full resolution of the issue with MongoDB Clusters.<br /><br />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.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>09:50</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue with MongoDB clusters and at this time, services should be functioning as expected. <br /><br />We're monitoring the situation and will post a final update once we confirm this is fully resolved.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>09:04</var> UTC</small><br><strong>Identified</strong> - Our engineering team has identified the cause of the issue with create, fork and resize events failure for MongoDB clusters in all of our regions and is actively working on a fix. We will post an update as soon as additional information is available.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>07:34</var> UTC</small><br><strong>Update</strong> - Our engineering team continues to investigate the issue with create, fork and resize events failure for MongoDB clusters in all of our regions. <br /><br />We appreciate your patience and will post an update as soon as additional information is available.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>05:42</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with all events for MongoDB clusters in all of our regions.<br /><br />During this time, users may face issues with creation, fork and resize operations in the MongoDB clusters. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>11</var>, <var data-var='time'>13:08</var> UTC</small><br><strong>Resolved</strong> - The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 08:52 UTC & 13:01 UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue.<br /><br />We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding.<br /><br />However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.</p><p><small>Feb <var data-var='date'>11</var>, <var data-var='time'>12:03</var> UTC</small><br><strong>Monitoring</strong> - Our team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. <br /><br />Users may already notice improvements while deploying apps. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.</p><p><small>Feb <var data-var='date'>11</var>, <var data-var='time'>11:50</var> UTC</small><br><strong>Investigating</strong> - Our engineers are currently investigating an issue impacting new App Platform deployments. During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.</p>

Details

Status Timeline

Description

Between 12:20 PM and 1:55 PM PST, we experienced elevated DNS resolution errors for CloudFront distributions served from a subset of edge locations globally. During this time, customers may have received NXDOMAIN responses. Engineers were automatically engaged, immediately began investigating in multiple parallel paths and mitigated errors by taking the affected fleet of DNS servers out of service. Additionally, between 12:20 PM and 8:08 PM PST, we experienced longer than usual propagation times for changes to CloudFront configurations. The propagation delay was limited to certain types of changes, such as creating/deleting distributions, or updating the distributions for DNS or TLS certificate related changes. Following mitigation of the DNS resolution errors at 1:55 PM, end-user requests for content delivery from our edge locations were not affected and are being served normally. Invalidations operated normally throughout the event. Both issues have been resolved and all services are operating normally. We are confident this issue will not reoccur.

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>04:38</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-02-10 09:00 UTC<br />End: 2026-02-10 17:00 UTC<br /><br /><br />Hello,<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the AMS2 region.<br /><br />Expected Impact:<br /><br />These upgrades are designed and tested to be seamless and we do not expect any impact to customer traffic due to this maintenance. If an unexpected issue arises, network traffic for the AMS2 region might be affected for a short period of time. We will endeavour to minimise any such impact.<br /><br />If you have any questions related to this maintenance, please send us a ticket from your cloud support page.<br /> https://cloudsupport.digitalocean.com/s/createticket</p>

Details

Affected Regions

Status Timeline

Description

Between 6:36 AM to 7:09 AM PST, we experienced intermittent network connectivity issues between two Availability Zones (sae1-az1 and sae1-az3) in the SA-EAST-1 Region. This issue resulted in API error rates and latencies for AWS Services in the SA-EAST-1 Region. The issue has been resolved and all services are operating normally.

Details

Status Timeline

Description

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>18:53</var> UTC</small><br><strong>Resolved</strong> - As of 17:55 UTC, our Engineering team has resolved the timeouts affecting the Cloud Control Panel and API. The issue was caused by a temporary overload on our infrastructure, resulting in 5xx errors for API requests and gateway timeouts for Cloud Control Panel users.<br /><br />If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>18:03</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix for the timeouts affecting the Cloud Control Panel and API, and is currently monitoring the situation. Services have recovered, and users should no longer experience 5xx errors when using the API or gateway timeouts when accessing the Cloud Control Panel.<br /><br />We will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved.</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:51</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the cause of the issue impacting the Cloud Control Panel and API and is actively working on deploying a fix. At this time, users will continue to see timeouts/5xx errors, but may intermittently see requests succeeding. <br /><br />We will post further updates as soon as the fix is deployed or there is more information to share.</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:32</var> UTC</small><br><strong>Update</strong> - Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:27</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Description

<p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>17:37</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. All services should now be functioning normally.<br /><br />If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>14:47</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to address the issue affecting Kubernetes clusters and Droplet events in the FRA1 region and is actively monitoring the situation. Customers should no longer experience issues provisioning Kubernetes clusters or mounting volumes. We will provide an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>13:30</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the root cause of the issue impacting Kubernetes clusters and Droplet events in the FRA1 region and is actively working on a fix. In the meantime, users may continue to experience issues. We appreciate your patience and will share updates as more information becomes available.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>11:27</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with Kubernetes clusters in the FRA1 region. During this time, subset of users may experience an issue while provisioning Kubernetes clusters and mounting volumes. Additionally, users may also notice the droplet events appearing to be stuck or delayed in this region. We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Affected Regions

Description

Between 7:08 AM and 10:48 AM PST, we experienced elevated latencies for network change propagation in the EU-WEST-1 Region. This was due to a delay in propagation of configuration updates on a sub-system which supports external and cross account connectivity. Customers experienced delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services were also impacted by this issue and were impacted by delayed or stuck workflows such as pulling container images. Engineers were automatically engaged at 6:29 AM, prior to customer impact beginning. At 7:20 AM, root cause was identified. By 9:20 we began observing early signs of recovery. Our mitigation efforts completed at 10:43 AM and full recovery was observed at 10:48 AM. We recommend customers retry any failed requests. The issue has been resolved and all services are operating normally.

Details

Status Timeline

Description

<p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>04:27</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed that the issue impacting our Droplet-based products in the FRA1 region has been completely mitigated. Users should no longer see issues with their Droplets and Droplet-related services.<br /><br />If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>04:11</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has identified the cause of the issue impacting our Droplet-based products in the FRA1 region and applied a fix. The impact has started to mitigate and users should be able to connect to their Droplets and also start to see events getting processed successfully.<br /><br />We're now monitoring the fix for stability and will post an update once we are confident it is successful.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>00:45</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is currently investigating an issue affecting events in FRA1. During this time, customers may experience delays or errors when creating or deleting Droplets, as well as when using Droplet-based products such as Load Balancers, Kubernetes Clusters, or Databases.<br /><br />Our teams are actively working to identify the root cause and restore full service as quickly as possible. We apologize for the inconvenience and will provide updates as more information becomes available.</p>

Details

Affected Regions

Description

<p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>09:28</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-01-27 09:00 UTC<br />End: 2026-01-27 12:00 UTC<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the NYC3 region.<br /><br />Expected impact:<br /><br />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.<br /><br />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</p>

Details

Affected Regions

Description

<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>22:44</var> UTC</small><br><strong>Resolved</strong> - From 20:45 UTC to 21:06 UTC, users may have experienced issue affecting the Cloud Control Panel, API, and related services.<br /><br />Our Engineering team has confirmed that the issue is fully resolved, and all systems are now operating normally.<br /><br />If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>21:27</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix for the issue affecting the Cloud Control Panel, API, and related services. <br /><br />We are observing recovery, and users should now be able to access their accounts and use the API without errors.<br /><br />We are continuing to monitor the situation closely and will provide an update once full resolution is confirmed.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>21:06</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue impacting multiple services including the Cloud Control Panel and API.<br /><br />Users may encounter errors when accessing their accounts or using the API.<br /><br />We are actively working to resolve this issue and will provide updates as soon as more information becomes available.</p>

Details

Description

<p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>18:25</var> UTC</small><br><strong>Resolved</strong> - The issue impacting App Platform deployments has been successfully resolved. Users should no longer encounter delays during the build phase or have deployments getting stuck. All services are now confirmed to be stable and operating normally.<br /><br />We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.</p><p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>18:05</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented necessary changes to address the issue impacting both new and in-progress App Platform Deployments. Our team is currently monitoring the situation. Users should now notice improvements in deployment performance.<br /><br />We appreciate your patience. We'll update once the issue is confirmed to be resolved.</p>

Details

Description

<p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>09:18</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with payments failure using PayNow. Users should not see any issues with making payments via PayNow and logging into the accounts on our platform. Services should now be operating normally.<br /><br />If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>07:16</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue with the suspended user's accounts being unable to access the accounts. During this time users may have experience issues signing in or accessing accounts and the failure in the payments. We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Description

<p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>22:34</var> UTC</small><br><strong>Resolved</strong> - Our Engineering has confirmed resolution of the issue. Users should no longer experience errors with attempting to deploy new static sites in NYC3 on App Platform.<br /><br />If you experience any further problems or have any questions, please open a support ticket within your account.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>22:06</var> UTC</small><br><strong>Update</strong> - Our Engineering team has deployed a fix for the issue. Users should no longer experience errors when attempting to deploy new static sites now in NYC3 for App Platform.<br /><br />We will post an update once we've confirmed that the issue is fully resolved.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>19:25</var> UTC</small><br><strong>Investigating</strong> - As of 17:45 UTC, our Engineering team is investigating reports of static site deployment failures in the NYC3 region on App Platform. Users may experience errors when attempting to deploy new static sites, resulting in failed deployments.<br /><br />The existing static sites are still accessible and functioning normally.<br /><br />Our team is actively working on identifying the root cause and implementing the fix.<br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Affected Regions

Description

<p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>21:34</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed full resolution of the issue. Users should no longer experience errors when making requests to the Cloud Control Panel or API.<br /><br />If you experience any further problems or have any questions, please open a support ticket within your account.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>18:46</var> UTC</small><br><strong>Investigating</strong> - As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services.<br /><br />At this point, the issue appears to be intermittent, and not all requests are being affected. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Description

<p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>16:19</var> UTC</small><br><strong>Resolved</strong> - From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.</p>

Details

Description

<p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>Resolved</strong> - From 18:57 UTC to 22:05 UTC, customers may have experienced issues accessing the Recovery Console due to a service interruption. During this time, Droplet functionality remained unaffected, and customers were still able to use the Recovery ISO option via SSH.<br /><br />Our Engineering team has confirmed that the issue is now fully resolved, and Recovery Console access has been fully restored and is operating normally.<br /><br />If you continue to experience any difficulties, please open a ticket with our Support team. We apologize for the inconvenience caused.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>22:43</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has deployed a fix to resolve the issue causing the Recovery Console to be unavailable.<br /><br />We are currently monitoring the situation to ensure access is fully restored and stable. Please note that Droplet functionality was not impacted by this issue.<br /><br />We will post another update once we confirm the issue is fully resolved.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>20:33</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is actively investigating an issue causing the Recovery Console to be unavailable. <br /><br />Droplet functionality is not impacted. If customers need recovery iso, they can still select the "Boot from Recovery ISO" option in the recovery tab as seen in the guide here https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-iso/ but will need to use SSH to access their droplets. <br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Description

<p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>17:43</var> UTC</small><br><strong>Scheduled</strong> - Start: 2025-12-10 18:00 UTC<br />End: 2025-12-10 20:00 UTC<br /><br /><br />During the above window, our Engineering team will be performing maintenance on principal infrastructure in order to improve reliability of the services. Please note that existing infrastructure will continue running without issue. This maintenance impacts create, read, update, and delete (CRUD) operations in all regions.<br /><br />Expected Impact:<br /><br />During the maintenance window, users may experience increased latency for the following platform operations:<br /><br />Cloud Control Panel and API operations<br />Event processing<br />Droplet creates, resizes, rebuilds, and power events<br />Managed Kubernetes reconciliation and scaling<br />Load Balancer operations<br />Container Registry operations<br />App Platform operations<br />Managed Database creation and scaling<br /><br />We expect to see two periods of 10 second impact, for a total of 20 seconds within the hour window. If unexpected impact occurs or continues for longer than expected, we will provide updates via our public status page.<br /><br />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<br /><br />Thank you,<br />Team DigitalOcean</p>

Details

Description

<p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>19:08</var> UTC</small><br><strong>Resolved</strong> - As of 18:15 UTC, our Engineering team has confirmed the issue impacting accessibility of App Platform static websites has been resolved. Service has been restored and are now functioning normally.<br /><br />We appreciate your patience and regret the inconvenience caused. If you continue to experience any issues, feel free to open a Support ticket for further investigation.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>18:41</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix impacting the availability of App Platform static websites. Users should now experience improved performance when accessing the sites. <br /><br />We are actively monitoring the situation and will provide an update once we can confirm the issue has been fully resolved.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>18:08</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is currently investigating an issue impacting App Platform static websites. During this period, users may notice 404 Not Found errors while accessing the sites. <br /><br />Our team is actively working on identifying the root cause and implementing the fix.<br /><br />We apologize for the inconvenience and will share an update once we have more information.</p>

Details

Description

<p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>12:21</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>21:26</var> UTC</small><br><strong>Scheduled</strong> - Hello, <br /><br />We are reaching out again to inform you that the core control plane infrastructure maintenance in SFO2 region which was previously scheduled to complete on 2025-12-02 09:00 UTC has been rescheduled to the following window:<br /><br />Start: 2025-12-10 09:00 UTC<br />End: 2025-12-10 15:00 UTC<br /><br />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.<br /><br />If you have questions or concerns about this maintenance, please reach out to us by opening up a ticket on your account.<br /><br />---BEGIN INITIAL MAINTENANCE NOTICE---<br /><br />Start: 2025-12-02 09:00 UTC<br />End: 2025-12-02 15:00 UTC<br /><br />Hello,<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure in SFO2. Please note that the existing infrastructure will continue running without issue.<br /><br />We do not anticipate any impact; however, there is a small possibility that control panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from within your account. We’re here to help.<br /><br />Thank you,<br /><br />Team DigitalOcean</p>

Details

Affected Regions