DigitalOcean Outage History

DigitalOcean is up right now

DigitalOcean had 90 outages in the last 2 years totaling 220h 56m of downtime — averaging 3.7 incidents per month.

There were 90 DigitalOcean outages since November 8, 2025 totaling 220h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.digitalocean.com

Minor September 16, 2026

Support Portal Service Disruption

Detected by Pingoru
Sep 16, 2026, 09:48 AM UTC
Resolved
Sep 16, 2026, 09:09 PM UTC
Duration
11h 21m
Affected: Support Center
Timeline · 3 updates
  1. investigating Sep 16, 2026, 09:48 AM UTC

    Our Support Portal is currently experiencing issues due to a third-party service disruption impacting our systems. During this time, customers may be unable to access the Support Portal or create new support tickets for their concerns. Existing support requests may also experience delayed responses from our Support team. As a workaround if you're unable to access the Support Portal or need to create a new support ticket, please submit your request via Support Contact form: https://www.digitalocean.com/company/contact/support. We apologize for the inconvenience and appreciate your patience while we work to resolve the issue. We'll provide another update as soon as we have more information.

  2. monitoring Sep 16, 2026, 02:07 PM UTC

    The Support Portal and ticket creation are now accessible. Our upstream provider has applied a fix, and we've verified ticket creation and review are working as expected. We'll continue monitoring for the next 2 hours to confirm full stability and will post a final update once the incident is closed. If you're still unable to access the portal, please use our Support Contact form as a backup: https://www.digitalocean.com/company/contact/support We apologize for the disruption and appreciate your patience.

  3. resolved Sep 16, 2026, 09:09 PM UTC

    From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Minor September 9, 2026

Power Degradation impacting GPU Performance in ATL1

Detected by Pingoru
Sep 09, 2026, 10:47 AM UTC
Resolved
Sep 09, 2026, 12:25 PM UTC
Duration
1h 38m
Affected: ATL1
Timeline · 3 updates
  1. investigating Sep 09, 2026, 10:47 AM UTC

    We are investigating a power issue affecting part of our ATL1 datacenter. Redundant power systems are keeping servers online, and we have not observed any server outages. However, available power capacity is reduced, which may cause degraded performance for some GPU workloads, particularly during periods of high utilization. Our datacenter and infrastructure teams are working to restore full power redundancy. We will provide an update as more information becomes available. We apologize for the inconvenience and appreciate your patience.

  2. monitoring Sep 09, 2026, 11:32 AM UTC

    The power issue affecting part of our ATL1 datacenter has been fully resolved. Power redundancy has been restored, and any potential customer impact has been mitigated. We will continue monitoring the environment to ensure continued stability.

  3. resolved Sep 09, 2026, 12:25 PM UTC

    This incident is now resolved. Power redundancy has been fully restored, and we have confirmed that customer impact has been mitigated. We are closing this incident.

Read the full incident report →

Minor August 23, 2026

Managed Databases Creation

Detected by Pingoru
Aug 23, 2026, 05:11 AM UTC
Resolved
Aug 23, 2026, 02:33 PM UTC
Duration
9h 21m
Affected: GlobalNYC1NYC3
Timeline · 4 updates
  1. investigating Aug 23, 2026, 05:11 AM UTC

    Our Engineering team has identified an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests. We apologize for the inconvenience and will share an update once we have more information.

  2. investigating Aug 23, 2026, 07:06 AM UTC

    We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions. During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API. Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.

  3. monitoring Aug 23, 2026, 11:30 AM UTC

    Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters. We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

  4. resolved Aug 23, 2026, 02:33 PM UTC

    Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally. Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/

Read the full incident report →

Minor August 21, 2026

Container Registry and Spaces Accessibility

Detected by Pingoru
Aug 21, 2026, 12:59 PM UTC
Resolved
Aug 21, 2026, 02:52 PM UTC
Duration
1h 52m
Affected: GlobalGlobal
Timeline · 3 updates
  1. investigating Aug 21, 2026, 12:59 PM UTC

    Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions. During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…" Our Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.

  2. monitoring Aug 21, 2026, 01:06 PM UTC

    Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied. Spaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal. We are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored.

  3. resolved Aug 21, 2026, 02:52 PM UTC

    Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images 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.

Read the full incident report →

Notice August 13, 2026

Volume Attach/Detach events in FRA1

Detected by Pingoru
Aug 13, 2026, 02:59 PM UTC
Resolved
Aug 13, 2026, 02:59 PM UTC
Duration
—
Affected: FRA1
Timeline · 1 update
  1. resolved Aug 13, 2026, 02:59 PM UTC

    Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters. During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources. Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this. We apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.

Read the full incident report →

Minor August 6, 2026

Functions on App Platform

Detected by Pingoru
Aug 06, 2026, 07:01 PM UTC
Resolved
Aug 06, 2026, 09:05 PM UTC
Duration
2h 3m
Affected: GlobalGlobal
Timeline · 3 updates
  1. investigating Aug 06, 2026, 07:01 PM UTC

    Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform. We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring Aug 06, 2026, 08:02 PM UTC

    Our Engineering team has implemented a fix for the issue affecting Functions on App Platform. Functions builds/deploys and requests to Functions endpoints should now be completing successfully. We are currently monitoring the situation to ensure the service has returned to normal operation and remains stable. We apologize for the inconvenience and will provide a further update once the incident is confirmed resolved.

  3. resolved Aug 06, 2026, 09:05 PM UTC

    Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.

Read the full incident report →

Minor August 4, 2026

Spaces Cold Storage Billing

Detected by Pingoru
Aug 04, 2026, 04:13 PM UTC
Resolved
Aug 04, 2026, 09:42 PM UTC
Duration
5h 29m
Affected: GlobalBilling
Timeline · 4 updates
  1. investigating Aug 04, 2026, 04:13 PM UTC

    Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.

  2. identified Aug 04, 2026, 06:52 PM UTC

    Our Engineering team has identified the issue affecting Spaces Cold Storage billing. The team is actively working on a fix to resolve the issue. We apologize for the inconvenience and will provide another update as soon as more information becomes available.

  3. monitoring Aug 04, 2026, 08:44 PM UTC

    Our Engineering team has implemented a fix for the issue affecting Spaces Cold Storage billing and is currently monitoring the situation. Customers with cold storage buckets should no longer see incorrect values reflected in their daily usage and current invoices. We will post an update as soon as the issue is fully resolved.

  4. resolved Aug 04, 2026, 09:42 PM UTC

    As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets. Our team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor August 3, 2026

Cloud Control Panel Access

Detected by Pingoru
Aug 03, 2026, 01:58 PM UTC
Resolved
Aug 03, 2026, 05:59 PM UTC
Duration
4h 1m
Affected: Cloud Control Panel
Timeline · 3 updates
  1. investigating Aug 03, 2026, 01:58 PM UTC

    Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating. We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available. 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

  2. monitoring Aug 03, 2026, 04:39 PM UTC

    We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved

  3. resolved Aug 03, 2026, 05:59 PM UTC

    Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.

Read the full incident report →

Minor July 29, 2026

Response Degradation Impacting Kimi-K3

Detected by Pingoru
Jul 29, 2026, 05:56 PM UTC
Resolved
Jul 30, 2026, 06:15 AM UTC
Duration
12h 19m
Affected: Model Services
Timeline · 3 updates
  1. investigating Jul 29, 2026, 05:56 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 29, 2026, 09:41 PM UTC

    Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3. At this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service. We apologize for the inconvenience and will share an update once we have more information.

  3. resolved Jul 30, 2026, 06:15 AM UTC

    Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Read the full incident report →

Major July 27, 2026

Agent Platform Requests Returning HTTP 500 Errors

Detected by Pingoru
Jul 27, 2026, 06:31 PM UTC
Resolved
Jul 28, 2026, 03:24 PM UTC
Duration
20h 52m
Affected: Agent Runtime
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:31 PM UTC

    We are currently investigating this issue.

  2. identified Jul 27, 2026, 07:44 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jul 28, 2026, 03:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2026

Network Connectivity from India to NYC

Detected by Pingoru
Jul 24, 2026, 10:36 AM UTC
Resolved
Jul 24, 2026, 12:42 PM UTC
Duration
2h 5m
Affected: NYC1
Timeline · 3 updates
  1. identified Jul 24, 2026, 10:36 AM UTC

    We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

  2. monitoring Jul 24, 2026, 11:45 AM UTC

    We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

  3. resolved Jul 24, 2026, 12:42 PM UTC

    Between 07:46 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.

Read the full incident report →

Minor July 23, 2026

Llama-4-Maverick Model Availability

Detected by Pingoru
Jul 23, 2026, 11:16 AM UTC
Resolved
Jul 23, 2026, 12:37 PM UTC
Duration
1h 20m
Affected: Inference
Timeline · 2 updates
  1. investigating Jul 23, 2026, 11:16 AM UTC

    Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference. We apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.

  2. resolved Jul 23, 2026, 12:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 19, 2026

Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1

Detected by Pingoru
Jul 19, 2026, 09:51 AM UTC
Resolved
Jul 19, 2026, 03:32 PM UTC
Duration
5h 41m
Affected: BLR1NYC1NYC3SGP1SYD1
Timeline · 5 updates
  1. investigating Jul 19, 2026, 09:51 AM UTC

    Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1 and NYC3 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.

  2. investigating Jul 19, 2026, 01:34 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 19, 2026, 01:36 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Jul 19, 2026, 02:52 PM UTC

    Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

  5. resolved Jul 19, 2026, 03:32 PM UTC

    Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Minor July 19, 2026

Networking in BLR1

Detected by Pingoru
Jul 19, 2026, 06:57 AM UTC
Resolved
Jul 19, 2026, 09:52 AM UTC
Duration
2h 54m
Affected: BLR1
Timeline · 4 updates
  1. investigating Jul 19, 2026, 06:57 AM UTC

    We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services. Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.

  2. identified Jul 19, 2026, 08:27 AM UTC

    Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution. Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1. We will provide another update once the issue has been fully resolved or when additional information becomes available.

  3. monitoring Jul 19, 2026, 09:31 AM UTC

    Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1. We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

  4. resolved Jul 19, 2026, 09:52 AM UTC

    Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Read the full incident report →

Minor July 16, 2026

Reserved IP routing in TOR1

Detected by Pingoru
Jul 16, 2026, 01:39 PM UTC
Resolved
Jul 16, 2026, 05:24 PM UTC
Duration
3h 44m
Affected: Reserved IPTOR1
Timeline · 4 updates
  1. investigating Jul 16, 2026, 01:39 PM UTC

    Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1. Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.

  2. identified Jul 16, 2026, 03:30 PM UTC

    Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1. Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.

  3. monitoring Jul 16, 2026, 05:01 PM UTC

    Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results. Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team. We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.

  4. resolved Jul 16, 2026, 05:24 PM UTC

    Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Read the full incident report →

Minor July 13, 2026

Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses

Detected by Pingoru
Jul 13, 2026, 07:04 PM UTC
Resolved
Jul 15, 2026, 09:46 PM UTC
Duration
2d 2h
Affected: Inference
Timeline · 5 updates
  1. identified Jul 13, 2026, 07:04 PM UTC

    We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts. Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place

  2. monitoring Jul 13, 2026, 10:24 PM UTC

    A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

  3. identified Jul 14, 2026, 11:07 AM UTC

    We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts. Our Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

  4. monitoring Jul 15, 2026, 10:06 AM UTC

    A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

  5. resolved Jul 15, 2026, 09:46 PM UTC

    The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels. We will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.

Read the full incident report →

Minor July 9, 2026

Kubernetes Deployments in NYC1

Detected by Pingoru
Jul 09, 2026, 08:31 PM UTC
Resolved
Jul 11, 2026, 01:27 AM UTC
Duration
1d 4h
Affected: NYC1
Timeline · 3 updates
  1. investigating Jul 09, 2026, 08:31 PM UTC

    Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time. We apologize for the inconvenience, we'll share new information on this page as soon as it is available.

  2. monitoring Jul 10, 2026, 01:18 AM UTC

    The issue affecting Kubernetes deployments in NYC1 has subsided. Workloads should now be functioning normally. Our Engineering team is continuing to monitor the affected systems to confirm full resolution. We'll update this page if any further action is needed. We apologize for the inconvenience this may have caused.

  3. resolved Jul 11, 2026, 01:27 AM UTC

    The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS. The affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas. If you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.

Read the full incident report →

Major July 4, 2026

Limited access to Deepseek V4 Pro model

Detected by Pingoru
Jul 04, 2026, 10:13 PM UTC
Resolved
Jul 05, 2026, 12:53 AM UTC
Duration
2h 39m
Affected: InferenceModel Services
Timeline · 3 updates
  1. investigating Jul 04, 2026, 10:13 PM UTC

    Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.

  2. monitoring Jul 04, 2026, 11:18 PM UTC

    Our Engineering team has implemented a fix for the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform. The model should now be operational, and users should no longer receive error 429 messages when attempting to use it. We are currently monitoring the situation to ensure the fix is successful and the model is functioning as expected. We will post an update if any further issues arise. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

  3. resolved Jul 05, 2026, 12:53 AM UTC

    Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors. 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.

Read the full incident report →

Notice July 4, 2026

Droplet Actions in NYC3

Detected by Pingoru
Jul 04, 2026, 02:42 PM UTC
Resolved
Jul 04, 2026, 03:10 PM UTC
Duration
27m
Affected: NYC3NYC3
Timeline · 2 updates
  1. monitoring Jul 04, 2026, 02:42 PM UTC

    Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region. During this time, customers may also have experienced errors when trying to create Droplets in this region. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

  2. resolved Jul 04, 2026, 03:10 PM UTC

    Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues. We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Read the full incident report →

Minor July 2, 2026

Managed Database Clusters

Detected by Pingoru
Jul 02, 2026, 10:04 PM UTC
Resolved
Jul 03, 2026, 08:20 AM UTC
Duration
10h 15m
Affected: GlobalGlobal
Timeline · 4 updates
  1. investigating Jul 02, 2026, 10:04 PM UTC

    Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API. We apologize for the inconvenience and will provide further updates as soon as more information is available.

  2. investigating Jul 03, 2026, 02:28 AM UTC

    Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters. We are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.

  3. monitoring Jul 03, 2026, 06:08 AM UTC

    Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

  4. resolved Jul 03, 2026, 08:20 AM UTC

    Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Read the full incident report →