Reading view

Gradient AI model availability

Mar 17, 19:49 UTC
Resolved - 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.

Mar 17, 15:00 UTC
Investigating - 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.

Additionally, Guardrails are not available, affecting associated agents, and users attempting to run inference on the Llama3.3-70b model will see degraded performance.

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

  •  

Cloud Control Panel and API

Mar 16, 17:39 UTC
Resolved - 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.

  •  

Degraded performance with BYOK Anthropic models

Mar 15, 03:31 UTC
Resolved - The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally.
Contact support if issues persist.

Mar 15, 02:55 UTC
Investigating - Our Engineering team is investigating an issue related to all Gradient AI agents and serverless inference that require BYOK Anthropic modles.
Impacted users may experience degraded performance.
We will provide an update as soon as possible

  •  

Delay in App Platform Deployments

Mar 14, 01:47 UTC
Resolved - 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.

Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.

However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.

Mar 13, 23:39 UTC
Monitoring - 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.

During this time, users should no longer experience issues with creating new apps and all the stalled creation events should provision completely.

We will post an update as soon as the issue is fully resolved.

Mar 13, 22:01 UTC
Identified - 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.

We again apologize for the inconvenience. We will post further updates once we have more information.

Mar 13, 21:30 UTC
Monitoring - Starting at 20:40 UTC, users may have seen delays with deploying new apps on App Platform.

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.

We apologize for the inconvenience. We'll post an update once the issue has been confirmed to be resolved.

  •  

Newly Created Managed Kubernetes Nodes

Mar 13, 16:35 UTC
Resolved - 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.

Mar 13, 13:55 UTC
Monitoring - 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.

We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.

Mar 13, 12:32 UTC
Identified - 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.

Mar 13, 11:26 UTC
Investigating - 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.

  •  

Ubuntu/Debian Package Mirror Failure

Mar 9, 19:23 UTC
Resolved - 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.

  •  

HTTP 522 Error on App Platform

Mar 6, 21:22 UTC
Resolved - 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.

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

  •  

App Platform Deployments

Mar 6, 01:12 UTC
Resolved - 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.

Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.

However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.

Mar 6, 00:32 UTC
Monitoring - 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.

We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.

Mar 5, 23:28 UTC
Investigating - 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.

We apologize for any inconvenience, and we'll share more information as it becomes available.

  •  

Internal Load Balancers Connectivity

Mar 5, 01:52 UTC
Resolved - 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.

Our Engineering team has confirmed full resolution of the issue, and Internal Load Balancers should now be functioning normally.

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

Mar 5, 01:19 UTC
Monitoring - 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.

We will provide a further update once we confirm the issue is fully resolved.

Mar 5, 00:23 UTC
Investigating - 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.

We apologize for the inconvenience and will share an update as soon as more information becomes available.

  •  

Core Infrastructure Maintenance in All Regions 2026-03-03 10:00 UTC

Mar 6, 15:55 UTC
Completed - This scheduled maintenance is now complete across all regions. Thank you for your patience and understanding throughout this process.

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

Mar 5, 13:05 UTC
Scheduled - Phase 2 maintenance is complete. Phase 3 is scheduled to begin at March 06, 11:00 UTC.

Mar 5, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Mar 3, 13:03 UTC
Scheduled - Phase 1 maintenance is complete. Phase 2 is scheduled to begin at March 05, 10:00 UTC.

Mar 3, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Mar 1, 10:44 UTC
Scheduled - Start: 2026-03-03 10:00 UTC
End: 2026-03-06 13:00 UTC

Hello,

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:

March 03, 10:00 to 13:00 UTC
March 05, 10:00 to 13:00 UTC
March 06, 11:00 to 13:00 UTC


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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

  •  

Core Infrastructure Maintenance in SFO2 and SFO3

Mar 2, 16:00 UTC
Completed - The scheduled maintenance has been completed.

Mar 2, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 28, 13:20 UTC
Scheduled - Start: 2026-03-02 13:00 UTC
End: 2026-03-02 16:00 UTC

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.

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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

  •  

Intermittent Errors with Llama 3.3-70B

Feb 26, 22:23 UTC
Resolved - Issue resolved.
Cause: A few requests made to the Llama 3.3-70B model caused issues.
Impact: Intermittent errors when interacting with the model through serverless inference and/or with agents created using this model.
Contact support if issues persist.

Feb 26, 21:52 UTC
Monitoring - Fix deployed. Monitoring resources related to the Llama 3.3-70B.
Users should no longer experience intermittent errors when making serverless inference requests via APIs and Agents . Awaiting confirmation before closure.

Feb 26, 16:00 UTC
Investigating - We are currently investigating an issue affecting the Llama 3.3-70B model.
Symptoms: Users may encounter intermittent errors when making serverless inference requests via APIs and Agents.
Current Status: Our engineering team is actively investigating the issue to determine the root cause.

  •  

App Platform Deployments

Feb 27, 04:55 UTC
Resolved - 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.

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.

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.

Feb 26, 17:14 UTC
Investigating - 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.

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:

https://docs.digitalocean.com/products/app-platform/how-to/migrate-nodejs-buildpack/

We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.

  •  

Core Infrastructure Maintenance in AMS3, FRA1, and LON1

Feb 26, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 26, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 24, 15:04 UTC
Scheduled - Start: 2026-02-26 16:00 UTC
End: 2026-02-26 20:00 UTC

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.

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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

  •  

Core Infrastructure Maintenance in BLR1 and SGP1

Feb 25, 18:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 25, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 23, 16:05 UTC
Scheduled - Start: 2026-02-25 15:00 UTC
End: 2026-02-25 18:00 UTC

Hello,

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.

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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

Thank you,
Team DigitalOcean

  •  

Core Infrastructure Maintenance in SYD1

Feb 24, 17:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 24, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 22, 15:12 UTC
Scheduled - Start: 2026-02-24 15:00 UTC
End: 2026-02-24 17:00 UTC

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.

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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

  •  

Network Maintenance - SFO1

Feb 24, 21:28 UTC
Completed - The scheduled maintenance has been completed.

Feb 24, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 22, 09:36 UTC
Scheduled - Start: 2026-02-24 09:00 UTC
End: 2026-02-24 22: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 SFO1 region.

Expected Impact:

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.

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

  •  

Control Panel Visibility

Feb 19, 18:42 UTC
Resolved - 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.

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.

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.

Feb 19, 18:05 UTC
Monitoring - 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.

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.

Feb 19, 17:34 UTC
Investigating - 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.

We apologize for the inconvenience and will share further updates as soon as more information becomes available.

  •  

Core Infrastructure Maintenance NYC3

Feb 20, 23:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 19, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 18, 10:16 UTC
Scheduled - Start: 2026-02-19 19:00 UTC
End: 2026-02-20 23:00 UTC

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.

Expected Impact:

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.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

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.

  •  

Spaces Availability in NYC3

Feb 16, 10:58 UTC
Resolved - 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.

All operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account.

Thank you for your patience while we worked to resolve this issue.

Feb 16, 07:36 UTC
Monitoring - 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.

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.

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.

If you continue to experience any issues, please contact our Support team.

  •  
❌