<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Digitalocean incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/digitalocean.html</link><description>Incidents from Digitalocean's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>Support Portal Service Disruption [investigating]</title><link>https://stspg.io/n6hr8jd64qjl</link><guid isPermaLink="false">digitalocean:2026-09-16T09:48:19.081Z</guid><pubDate>Wed, 16 Sep 2026 09:48:19 +0000</pubDate><description>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&#x27;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&#x27;ll provide another update as soon as we have more information.</description></item><item><title>Power Degradation impacting GPU Performance in ATL1 [resolved]</title><link>https://stspg.io/g4s2358yl9tt</link><guid isPermaLink="false">digitalocean:2026-09-09T10:47:40.428Z</guid><pubDate>Wed, 09 Sep 2026 10:47:40 +0000</pubDate><description>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.</description></item><item><title>Cloud Control Panel and API [postmortem]</title><link>https://stspg.io/8l5c24cxh3hr</link><guid isPermaLink="false">digitalocean:2026-08-24T17:14:43.701Z</guid><pubDate>Mon, 24 Aug 2026 17:14:43 +0000</pubDate><description>## 1. What happened

Between 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \(Volumes\) remained fully functional and unaffected throughout the event. No customer data loss occurred.

The event was initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a critical authorization query. In response to the elevated query latency, multiple upstream services init</description></item><item><title>Managed Databases Creation [resolved]</title><link>https://stspg.io/8ld5fpw01tg4</link><guid isPermaLink="false">digitalocean:2026-08-23T05:11:37.000Z</guid><pubDate>Sun, 23 Aug 2026 05:11:37 +0000</pubDate><description>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/</description></item><item><title>Container Registry and Spaces Accessibility [resolved]</title><link>https://stspg.io/2b4phnbmtm49</link><guid isPermaLink="false">digitalocean:2026-08-21T12:59:42.692Z</guid><pubDate>Fri, 21 Aug 2026 12:59:42 +0000</pubDate><description>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.</description></item><item><title>Major Service Interruption in MKC1 [resolved]</title><link>https://stspg.io/gdzqj0v18x0r</link><guid isPermaLink="false">digitalocean:2026-08-19T11:10:06.329Z</guid><pubDate>Wed, 19 Aug 2026 11:10:06 +0000</pubDate><description>Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally.

GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates.

Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.</description></item><item><title>Volume Attach/Detach events in FRA1 [resolved]</title><link>https://stspg.io/yldnj7859gcp</link><guid isPermaLink="false">digitalocean:2026-08-13T14:59:44.847Z</guid><pubDate>Thu, 13 Aug 2026 14:59:44 +0000</pubDate><description>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 Vol</description></item><item><title>Account Registration, Droplets, and Related Services [resolved]</title><link>https://stspg.io/grfh9nf5bp3f</link><guid isPermaLink="false">digitalocean:2026-08-08T18:57:49.228Z</guid><pubDate>Sat, 08 Aug 2026 18:57:49 +0000</pubDate><description>Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation.

We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.</description></item><item><title>Functions on App Platform [resolved]</title><link>https://stspg.io/7pm9l1jwpkr6</link><guid isPermaLink="false">digitalocean:2026-08-06T19:01:27.576Z</guid><pubDate>Thu, 06 Aug 2026 19:01:27 +0000</pubDate><description>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&#x27;t hesitate to raise a support ticket for further investigation.</description></item><item><title>Multiple Services Availability [resolved]</title><link>https://stspg.io/zscj6w048lfx</link><guid isPermaLink="false">digitalocean:2026-08-06T16:33:14.787Z</guid><pubDate>Thu, 06 Aug 2026 16:33:14 +0000</pubDate><description>Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing.

Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications.

The services have recovered and are now operating normally. Customers should no lo</description></item><item><title>Spaces Cold Storage Billing [resolved]</title><link>https://stspg.io/qb6zv0kdjy50</link><guid isPermaLink="false">digitalocean:2026-08-04T16:13:35.593Z</guid><pubDate>Tue, 04 Aug 2026 16:13:35 +0000</pubDate><description>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.</description></item><item><title>Cloud Control Panel Access [resolved]</title><link>https://stspg.io/045lx5xqfdns</link><guid isPermaLink="false">digitalocean:2026-08-03T13:58:04.872Z</guid><pubDate>Mon, 03 Aug 2026 13:58:04 +0000</pubDate><description>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.</description></item><item><title>Response Degradation Impacting Kimi-K3 [resolved]</title><link>https://stspg.io/ynhlvpy6ctcm</link><guid isPermaLink="false">digitalocean:2026-07-29T17:56:51.011Z</guid><pubDate>Wed, 29 Jul 2026 17:56:51 +0000</pubDate><description>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.</description></item><item><title>Agent Platform Requests Returning HTTP 500 Errors [resolved]</title><link>https://stspg.io/54mh0lzk9733</link><guid isPermaLink="false">digitalocean:2026-07-27T18:31:40.584Z</guid><pubDate>Mon, 27 Jul 2026 18:31:40 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Network Connectivity from India to NYC [resolved]</title><link>https://stspg.io/y9g7qgc9qs6m</link><guid isPermaLink="false">digitalocean:2026-07-24T10:36:52.252Z</guid><pubDate>Fri, 24 Jul 2026 10:36:52 +0000</pubDate><description>Between 07:46  UTC &amp; 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&#x27;t hesitate to open a support ticket for further investigation; we&#x27;ll be happy to assist you further.</description></item><item><title>Llama-4-Maverick Model Availability [resolved]</title><link>https://stspg.io/9pxmkrlffl58</link><guid isPermaLink="false">digitalocean:2026-07-23T11:16:59.123Z</guid><pubDate>Thu, 23 Jul 2026 11:16:59 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b [resolved]</title><link>https://stspg.io/2fdnm4tns3f1</link><guid isPermaLink="false">digitalocean:2026-07-22T16:50:42.474Z</guid><pubDate>Wed, 22 Jul 2026 16:50:42 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1 [resolved]</title><link>https://stspg.io/wv68wmnz55ln</link><guid isPermaLink="false">digitalocean:2026-07-19T09:51:19.000Z</guid><pubDate>Sun, 19 Jul 2026 09:51:19 +0000</pubDate><description>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.</description></item><item><title>Networking in BLR1 [resolved]</title><link>https://stspg.io/8yc90q76srsl</link><guid isPermaLink="false">digitalocean:2026-07-19T06:57:41.458Z</guid><pubDate>Sun, 19 Jul 2026 06:57:41 +0000</pubDate><description>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.</description></item><item><title>Reserved IP routing in TOR1 [resolved]</title><link>https://stspg.io/x0s0pghvdcgv</link><guid isPermaLink="false">digitalocean:2026-07-16T13:39:47.134Z</guid><pubDate>Thu, 16 Jul 2026 13:39:47 +0000</pubDate><description>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.</description></item><item><title>Serverless Inference - Gemma4 Latency Issues Causing Timeouts &amp; Slow Responses [resolved]</title><link>https://stspg.io/rzs04wclgpfq</link><guid isPermaLink="false">digitalocean:2026-07-13T19:04:10.240Z</guid><pubDate>Mon, 13 Jul 2026 19:04:10 +0000</pubDate><description>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.</description></item><item><title>Kubernetes Deployments in NYC1 [resolved]</title><link>https://stspg.io/p8xctv4k5yjv</link><guid isPermaLink="false">digitalocean:2026-07-09T20:31:52.156Z</guid><pubDate>Thu, 09 Jul 2026 20:31:52 +0000</pubDate><description>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.</description></item><item><title>Limited access to Deepseek V4 Pro model [resolved]</title><link>https://stspg.io/wwsc9zft1lxd</link><guid isPermaLink="false">digitalocean:2026-07-04T22:13:45.293Z</guid><pubDate>Sat, 04 Jul 2026 22:13:45 +0000</pubDate><description>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.</description></item><item><title>Droplet Actions in NYC3 [resolved]</title><link>https://stspg.io/1ggj0xnb3n4v</link><guid isPermaLink="false">digitalocean:2026-07-04T14:42:47.881Z</guid><pubDate>Sat, 04 Jul 2026 14:42:47 +0000</pubDate><description>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.</description></item><item><title>Managed Database Clusters [resolved]</title><link>https://stspg.io/rpkck6zr7ht5</link><guid isPermaLink="false">digitalocean:2026-07-02T22:04:53.265Z</guid><pubDate>Thu, 02 Jul 2026 22:04:53 +0000</pubDate><description>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.</description></item><item><title>DNS Lookup Failures for Managed Database [resolved]</title><link>https://stspg.io/r6yw4xc720r8</link><guid isPermaLink="false">digitalocean:2026-07-01T11:35:28.934Z</guid><pubDate>Wed, 01 Jul 2026 11:35:28 +0000</pubDate><description>The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. 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.</description></item><item><title>Droplet Resize [resolved]</title><link>https://stspg.io/m6y2gmlz3jrv</link><guid isPermaLink="false">digitalocean:2026-07-01T11:13:21.135Z</guid><pubDate>Wed, 01 Jul 2026 11:13:21 +0000</pubDate><description>Our Engineering team has confirmed that the issue impacting Droplet resizes using the &quot;Downscale Anytime&quot; option has been fully resolved. Users can now resize their Droplets using the &quot;Downscale Anytime&quot; option 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.</description></item><item><title>Agent Timeouts While Retrieving Data from Knowledge Bases [resolved]</title><link>https://stspg.io/sp8b09xxqvjt</link><guid isPermaLink="false">digitalocean:2026-07-01T06:25:23.501Z</guid><pubDate>Wed, 01 Jul 2026 06:25:23 +0000</pubDate><description>This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.</description></item><item><title>Droplet Backup Service [resolved]</title><link>https://stspg.io/djw8kv2yfvcd</link><guid isPermaLink="false">digitalocean:2026-06-27T18:24:25.041Z</guid><pubDate>Sat, 27 Jun 2026 18:24:25 +0000</pubDate><description>Between 00:00 UTC &amp; 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets.  During this period, backups scheduled within this window may not have been created and may appear as missing.

Our team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.</description></item><item><title>Anthropic Inference Model Availability [resolved]</title><link>https://stspg.io/s2bx05f4wxkb</link><guid isPermaLink="false">digitalocean:2026-06-27T04:43:29.854Z</guid><pubDate>Sat, 27 Jun 2026 04:43:29 +0000</pubDate><description>Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues.
If you continue to experience problems, please open a ticket with our Support team so we can investigate further.
We apologize for any inconvenience this may have caused.</description></item></channel></rss>