Snapshot 14896
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "grb2v0td1nq5",
"impact": "minor",
"message": "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. \n\nOur 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.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.",
"name": "Support Portal Service Disruption",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e09:48\u003c/var\u003e - \u003cvar data-var='time'\u003e21:09\u003c/var\u003e UTC"
},
{
"code": "1t16vfgq3zpx",
"impact": "minor",
"message": "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.",
"name": "Power Degradation impacting GPU Performance in ATL1",
"timestamp": "Sep \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e10:47\u003c/var\u003e - \u003cvar data-var='time'\u003e12:25\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "cnm4s0mdkh7l",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Rescheduled: Spaces Maintenance in BLR1",
"timestamp": "Aug \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e17:40\u003c/var\u003e UTC"
},
{
"code": "jtwb3n6wzky3",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Rescheduled: Spaces Maintenance in NYC3, SFO2 and SFO3",
"timestamp": "Aug \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e05:30\u003c/var\u003e - \u003cvar data-var='time'\u003e08:30\u003c/var\u003e UTC"
},
{
"code": "kxdpdcnrgsjp",
"impact": "maintenance",
"message": "The ongoing maintenance for Spaces has been cancelled and will be rescheduled for tomorrow. We apologize for any inconvenience and appreciate your understanding.",
"name": "[Scheduled] Rescheduled: Spaces Maintenance in BLR1",
"timestamp": "Aug \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:28\u003c/var\u003e UTC"
},
{
"code": "mw0kv1pvk6hm",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Rescheduled: Spaces Maintenance in AMS3, FRA1 and TOR1",
"timestamp": "Aug \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e06:00\u003c/var\u003e - \u003cvar data-var='time'\u003e09:00\u003c/var\u003e UTC"
},
{
"code": "4qwm6pzlx1z3",
"impact": "critical",
"message": "Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more. \n\nThank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account",
"name": "Cloud Control Panel and API",
"timestamp": "Aug \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e17:14\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e19:04\u003c/var\u003e UTC"
},
{
"code": "j0h39bqs3bdx",
"impact": "maintenance",
"message": "We are reaching out to inform you that the Spaces maintenance previously scheduled for 2026-08-26 05:30 UTC to 07:30 UTC in the NYC3, SFO2, and SFO3 regions has been cancelled.\n\nWe do not have a rescheduled date at this time. Once a new maintenance window is confirmed, we will send a follow-up notice to let you know. We apologize for any inconvenience this may cause and thank you for your patience.\n\nIf you have any questions or concerns, please reach out to us by opening a support ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket",
"name": "[Scheduled] Spaces Maintenance in NYC3, SFO2 and SFO3",
"timestamp": "Aug \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e06:57\u003c/var\u003e UTC"
},
{
"code": "tdz57gsr1j90",
"impact": "maintenance",
"message": "We are reaching out to inform you that the Spaces maintenance previously scheduled for 2026-08-25 05:30 UTC to 07:30 UTC in the AMS3, BLR1, FRA1 and TOR1 regions has been cancelled.\n\nWe do not have a rescheduled date at this time. Once a new maintenance window is confirmed, we will send a notice to let you know. We apologize for any inconvenience this may cause and thank you for your patience.\n\nIf you have any questions or concerns, please reach out to us by opening a support ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket",
"name": "[Scheduled] Spaces Maintenance in AMS3, BLR1, FRA1 and TOR1",
"timestamp": "Aug \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e05:30\u003c/var\u003e - \u003cvar data-var='time'\u003e06:32\u003c/var\u003e UTC"
},
{
"code": "zy2258kz0y91",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Maintenance Window Extended in LON1, SGP1, SYD1.",
"timestamp": "Aug \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e10:41\u003c/var\u003e - \u003cvar data-var='time'\u003e12:00\u003c/var\u003e UTC"
},
{
"code": "5sfkml29hl2m",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Spaces Maintenance in LON1, SGP1 and SYD1",
"timestamp": "Aug \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e05:30\u003c/var\u003e - \u003cvar data-var='time'\u003e07:30\u003c/var\u003e UTC"
},
{
"code": "r96y45y5sx59",
"impact": "minor",
"message": "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.\n\nOur 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/",
"name": "Managed Databases Creation",
"timestamp": "Aug \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e05:11\u003c/var\u003e - \u003cvar data-var='time'\u003e14:33\u003c/var\u003e UTC"
},
{
"code": "s0dyq97c5v72",
"impact": "minor",
"message": "Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. \n\nSpaces 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.\n\nIf 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.",
"name": "Container Registry and Spaces Accessibility",
"timestamp": "Aug \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e12:59\u003c/var\u003e - \u003cvar data-var='time'\u003e14:52\u003c/var\u003e UTC"
},
{
"code": "qd8v4wddyqjr",
"impact": "critical",
"message": "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.\n\nGPU 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.\n\nThank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.",
"name": "Major Service Interruption in MKC1",
"timestamp": "Aug \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e11:10\u003c/var\u003e - \u003cvar data-var='time'\u003e19:34\u003c/var\u003e UTC"
},
{
"code": "y3kn2w2qf5s4",
"impact": "none",
"message": "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.\n\nDuring this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources.\n\nBlock 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.\n\nWe 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.",
"name": "Volume Attach/Detach events in FRA1",
"timestamp": "Aug \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e14:59\u003c/var\u003e - \u003cvar data-var='time'\u003e14:59\u003c/var\u003e UTC"
},
{
"code": "2wql4f4sb13r",
"impact": "minor",
"message": "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.\n\nWe apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.",
"name": "Account Registration, Droplets, and Related Services",
"timestamp": "Aug \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e18:57\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e01:01\u003c/var\u003e UTC"
},
{
"code": "cg3q7h89dbnq",
"impact": "minor",
"message": "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.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.",
"name": "Functions on App Platform",
"timestamp": "Aug \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e19:01\u003c/var\u003e - \u003cvar data-var='time'\u003e21:05\u003c/var\u003e UTC"
},
{
"code": "vjm8qnbt45tb",
"impact": "none",
"message": "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.\n\nCustomers 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.\n\nThe services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues with any of these services, please don't hesitate to open a support ticket. Our team will be happy to assist you.",
"name": "Multiple Services Availability",
"timestamp": "Aug \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e16:33\u003c/var\u003e - \u003cvar data-var='time'\u003e16:33\u003c/var\u003e UTC"
},
{
"code": "l20hw5cfhksw",
"impact": "minor",
"message": "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.\n\nOur 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.",
"name": "Spaces Cold Storage Billing",
"timestamp": "Aug \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e16:13\u003c/var\u003e - \u003cvar data-var='time'\u003e21:42\u003c/var\u003e UTC"
},
{
"code": "3nt69xj3wkk9",
"impact": "minor",
"message": "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.",
"name": "Cloud Control Panel Access",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e13:58\u003c/var\u003e - \u003cvar data-var='time'\u003e17:59\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "rdfp2h4syxz8",
"impact": "minor",
"message": "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.",
"name": "Response Degradation Impacting Kimi-K3",
"timestamp": "Jul \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e17:56\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e06:15\u003c/var\u003e UTC"
},
{
"code": "fcfplv03vbwt",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Agent Platform Requests Returning HTTP 500 Errors",
"timestamp": "Jul \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e18:31\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e15:24\u003c/var\u003e UTC"
},
{
"code": "w53965shllfq",
"impact": "minor",
"message": "Between 07:46 UTC \u0026amp; 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.\n\nOur 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.\n\nWe 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.",
"name": "Network Connectivity from India to NYC",
"timestamp": "Jul \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e10:36\u003c/var\u003e - \u003cvar data-var='time'\u003e12:42\u003c/var\u003e UTC"
},
{
"code": "ym1lj8ww7cpz",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Llama-4-Maverick Model Availability",
"timestamp": "Jul \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e11:16\u003c/var\u003e - \u003cvar data-var='time'\u003e12:37\u003c/var\u003e UTC"
},
{
"code": "j6cjljphvgq7",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b",
"timestamp": "Jul \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e16:50\u003c/var\u003e - \u003cvar data-var='time'\u003e19:42\u003c/var\u003e UTC"
},
{
"code": "84v7d9gkkzzf",
"impact": "minor",
"message": "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.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.",
"name": "Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1",
"timestamp": "Jul \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e09:51\u003c/var\u003e - \u003cvar data-var='time'\u003e15:32\u003c/var\u003e UTC"
},
{
"code": "qzbsmdsw9lq8",
"impact": "minor",
"message": "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.",
"name": "Networking in BLR1",
"timestamp": "Jul \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e06:57\u003c/var\u003e - \u003cvar data-var='time'\u003e09:52\u003c/var\u003e UTC"
},
{
"code": "nfhvp4yhyrfl",
"impact": "minor",
"message": "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.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.",
"name": "Reserved IP routing in TOR1",
"timestamp": "Jul \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e13:39\u003c/var\u003e - \u003cvar data-var='time'\u003e17:24\u003c/var\u003e UTC"
},
{
"code": "8sjb7kmqnvk9",
"impact": "minor",
"message": "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.\nWe 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.",
"name": "Serverless Inference - Gemma4 Latency Issues Causing Timeouts \u0026 Slow Responses",
"timestamp": "Jul \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e19:04\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e21:46\u003c/var\u003e UTC"
},
{
"code": "2kxtxyvzzzk0",
"impact": "minor",
"message": "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.\n\nThe 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. \n\nIf you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.",
"name": "Kubernetes Deployments in NYC1",
"timestamp": "Jul \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e20:31\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e01:27\u003c/var\u003e UTC"
},
{
"code": "nckrrfnxf6pj",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] NYC2 Network Maintenance",
"timestamp": "Jul \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e10:30\u003c/var\u003e - \u003cvar data-var='time'\u003e15:30\u003c/var\u003e UTC"
},
{
"code": "wvj4t3y98gs7",
"impact": "major",
"message": "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.\n\nIf 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.",
"name": "Limited access to Deepseek V4 Pro model",
"timestamp": "Jul \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e22:13\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e00:53\u003c/var\u003e UTC"
},
{
"code": "7vmz1hmlzzrc",
"impact": "none",
"message": "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.\n\nWe 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.",
"name": "Droplet Actions in NYC3",
"timestamp": "Jul \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e14:42\u003c/var\u003e - \u003cvar data-var='time'\u003e15:10\u003c/var\u003e UTC"
},
{
"code": "rjfr3rbzxlx1",
"impact": "minor",
"message": "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.",
"name": "Managed Database Clusters",
"timestamp": "Jul \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e22:04\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e08:20\u003c/var\u003e UTC"
},
{
"code": "76l7xym7jd5m",
"impact": "none",
"message": "This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.",
"name": "Agent Timeouts While Retrieving Data from Knowledge Bases",
"timestamp": "Jul \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e06:25\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e03:38\u003c/var\u003e UTC"
},
{
"code": "phwpbgwcmkjn",
"impact": "minor",
"message": "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.",
"name": "DNS Lookup Failures for Managed Database",
"timestamp": "Jul \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e11:35\u003c/var\u003e - \u003cvar data-var='time'\u003e16:28\u003c/var\u003e UTC"
},
{
"code": "8mvnl6s4cmdt",
"impact": "none",
"message": "Our Engineering team has confirmed that the issue impacting Droplet resizes using the \"Downscale Anytime\" option has been fully resolved. Users can now resize their Droplets using the \"Downscale Anytime\" option without any issues.\n\nWe 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.",
"name": "Droplet Resize",
"timestamp": "Jul \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e11:13\u003c/var\u003e - \u003cvar data-var='time'\u003e13:28\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "m2shb5ks2rml",
"impact": "none",
"message": "Between 00:00 UTC \u0026amp; 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.\n\nOur 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.\n\nWe 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.",
"name": "Droplet Backup Service",
"timestamp": "Jun \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e18:24\u003c/var\u003e - \u003cvar data-var='time'\u003e18:24\u003c/var\u003e UTC"
},
{
"code": "psk2b3pgbblq",
"impact": "none",
"message": "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.\nIf you continue to experience problems, please open a ticket with our Support team so we can investigate further.\nWe apologize for any inconvenience this may have caused.",
"name": "Anthropic Inference Model Availability",
"timestamp": "Jun \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e04:43\u003c/var\u003e - \u003cvar data-var='time'\u003e05:15\u003c/var\u003e UTC"
},
{
"code": "xzrsyx9j7jx2",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] SFO1 Network Maintenance",
"timestamp": "Jun \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e09:30\u003c/var\u003e - \u003cvar data-var='time'\u003e12:30\u003c/var\u003e UTC"
},
{
"code": "nqkv7bnzr4l3",
"impact": "minor",
"message": "Between 13:22 \u0026amp; 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel.\n\nOur engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues viewing monitoring graphs, please create a support ticket for further analysis. Thank you for your patience and understanding",
"name": "Monitoring Graphs in the Cloud Control Panel",
"timestamp": "Jun \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e14:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:37\u003c/var\u003e UTC"
},
{
"code": "jcz8lx6qhg7y",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] SGP1 Network Maintenance",
"timestamp": "Jun \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e14:30\u003c/var\u003e - \u003cvar data-var='time'\u003e17:30\u003c/var\u003e UTC"
},
{
"code": "9dcyvb71b9gx",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance June 17, 2026, 09:00 UTC",
"timestamp": "Jun \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e18:00\u003c/var\u003e UTC"
},
{
"code": "bfsh34myw3bc",
"impact": "none",
"message": "The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.\nOur engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.",
"name": "Intermittent 500 Errors on Serverless/GenAI Inference API",
"timestamp": "Jun \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e22:00\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e00:29\u003c/var\u003e UTC"
},
{
"code": "505mwh53nwl2",
"impact": "major",
"message": "This incident has been resolved.",
"name": "DeepSeek V4 Pro is returning HTTP 429 \"Rate limit exceeded\"",
"timestamp": "Jun \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e14:24\u003c/var\u003e - \u003cvar data-var='time'\u003e17:42\u003c/var\u003e UTC"
},
{
"code": "c8hmbfzqwyjn",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] AMS2 Network Maintenance",
"timestamp": "Jun \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e15:30\u003c/var\u003e - \u003cvar data-var='time'\u003e18:30\u003c/var\u003e UTC"
},
{
"code": "nnt4rfbgn1y6",
"impact": "minor",
"message": "Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted.\n\nOur Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.",
"name": "DNS API Service",
"timestamp": "Jun \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e10:12\u003c/var\u003e - \u003cvar data-var='time'\u003e11:47\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "y3p9v8vm4tfn",
"impact": "minor",
"message": "Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. 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.\n\nIf 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.",
"name": "App Platform Deployments",
"timestamp": "May \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e00:14\u003c/var\u003e - \u003cvar data-var='time'\u003e07:58\u003c/var\u003e UTC"
},
{
"code": "55wh1mbv7vbs",
"impact": "minor",
"message": "Between 06:35 UTC \u0026amp; 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.",
"name": "Cloud Firewall",
"timestamp": "May \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e12:08\u003c/var\u003e - \u003cvar data-var='time'\u003e13:03\u003c/var\u003e UTC"
},
{
"code": "sv0tfb6jhqz8",
"impact": "minor",
"message": "Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident.",
"name": "Cloud Firewall",
"timestamp": "May \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e05:35\u003c/var\u003e - \u003cvar data-var='time'\u003e07:48\u003c/var\u003e UTC"
},
{
"code": "spgd2scvttth",
"impact": "minor",
"message": "From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.\n\nOur Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.",
"name": "Block Storage Volume Performance",
"timestamp": "May \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e01:05\u003c/var\u003e - \u003cvar data-var='time'\u003e05:13\u003c/var\u003e UTC"
},
{
"code": "c4r5y0txb8fb",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] SGP1 Network Maintenance 2026-05-19 14:30 UTC",
"timestamp": "May \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e14:30\u003c/var\u003e - \u003cvar data-var='time'\u003e17:30\u003c/var\u003e UTC"
},
{
"code": "yptcbq8w8181",
"impact": "maintenance",
"message": "The scheduled maintenance currently in progress has encountered unexpected roadblocks. As a result, we have made the decision to pause the maintenance at this time.\n\nWe will provide a further update with a specific time and date for the resumption and expected completion as soon as those details are finalized.\n\nWe apologize for any inconvenience and thank you for your understanding.\n\nIf you have questions or concerns about this maintenance, please reach out to us by opening up a ticket on your account.",
"name": "[Scheduled] Data-plane DOKS cluster in SYD1 region",
"timestamp": "May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e06:06\u003c/var\u003e - May \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e05:07\u003c/var\u003e UTC"
},
{
"code": "lrrw084g3whn",
"impact": "major",
"message": "As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.",
"name": "Anthropic reported outage that's impacting access to their Serverless Inference models",
"timestamp": "May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e01:21\u003c/var\u003e - \u003cvar data-var='time'\u003e02:00\u003c/var\u003e UTC"
},
{
"code": "gwgh41d5r0nz",
"impact": "minor",
"message": "As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.\n\nThe backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. \n\nWe apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality.\n\nHowever, 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.",
"name": "DNS service, Certificates and Managed MongoDB",
"timestamp": "May \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e13:57\u003c/var\u003e - \u003cvar data-var='time'\u003e20:46\u003c/var\u003e UTC"
},
{
"code": "bnq93nhgvtm6",
"impact": "major",
"message": "The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved.",
"name": "GradientAI: Agent Platform Playground Interaction Errors",
"timestamp": "May \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e10:24\u003c/var\u003e - \u003cvar data-var='time'\u003e11:37\u003c/var\u003e UTC"
},
{
"code": "7hb39w1wzmwf",
"impact": "minor",
"message": "Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.",
"name": "Control Panel Errors - Unable to Enable 2FA and Google/GitHub",
"timestamp": "May \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e11:15\u003c/var\u003e - \u003cvar data-var='time'\u003e14:42\u003c/var\u003e UTC"
},
{
"code": "p3zyn7c4jyx7",
"impact": "minor",
"message": "The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. \n\nWe appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.",
"name": "Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations",
"timestamp": "May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e20:46\u003c/var\u003e - \u003cvar data-var='time'\u003e21:54\u003c/var\u003e UTC"
},
{
"code": "h9t3sfjx36l3",
"impact": "minor",
"message": "Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.",
"name": "Multiple Services in NYC2",
"timestamp": "May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e18:01\u003c/var\u003e - \u003cvar data-var='time'\u003e19:59\u003c/var\u003e UTC"
},
{
"code": "0rq6c6jtw6ct",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance May 7, 2026, 15:00 UTC",
"timestamp": "May \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e15:20\u003c/var\u003e - \u003cvar data-var='time'\u003e21:00\u003c/var\u003e UTC"
},
{
"code": "fkk4qqns0c51",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance May 4th, 2026, 13:00 UTC",
"timestamp": "May \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e13:01\u003c/var\u003e - \u003cvar data-var='time'\u003e21:01\u003c/var\u003e UTC"
},
{
"code": "hjkhkdh7f8hv",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance May 4, 2026, 13:00 UTC",
"timestamp": "May \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e13:00\u003c/var\u003e - \u003cvar data-var='time'\u003e21:00\u003c/var\u003e UTC"
},
{
"code": "7rq8trdm1fsq",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] SFO2 Network Maintenance",
"timestamp": "May \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e13:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "4v4m8rywbtx2",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] FRA1 Network Maintenance",
"timestamp": "Apr \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:00\u003c/var\u003e UTC"
},
{
"code": "tl6xvjltgqx9",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] NYC1 Network Maintenance",
"timestamp": "Apr \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e10:00\u003c/var\u003e - \u003cvar data-var='time'\u003e12:00\u003c/var\u003e UTC"
},
{
"code": "nvt73942b9w7",
"impact": "maintenance",
"message": "During the dry-run for the scheduled SFO2 Network Maintenance , our team identified some potential risks that need to be addressed to ensure a smoother and safer implementation. As a result, we are cancelling the current maintenance window and will be rescheduling it to 2026-05-04 13:00-15:00 UTC.\n\nThank you for your understanding and patience as we work to improve performance and scalability.\n\nIf you have any questions related to this issue, please send us a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket",
"name": "[Scheduled] SFO2 Network Maintenance",
"timestamp": "Apr \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e06:43\u003c/var\u003e UTC"
},
{
"code": "fv80ch9p1ltj",
"impact": "maintenance",
"message": "During the dry-run for the scheduled Core Infrastructure Maintenance, our team identified some potential risks that need to be addressed to ensure a smoother and safer implementation. As a result, we are cancelling the current maintenance window and will be rescheduling it to 2026-05-04 13:00-21:00 UTC.\n\nThank you for your understanding and patience as we work to improve performance and scalability.\n\nIf you have any questions related to this issue, please send us a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket",
"name": "[Scheduled] Core Infrastructure Maintenance Apr 29, 2026, 13:00 UTC",
"timestamp": "Apr \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e13:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:29\u003c/var\u003e UTC"
},
{
"code": "z5fjzx3kp16z",
"impact": "minor",
"message": "All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.\n\nThank you for your patience while we worked to resolve this issue.",
"name": "Elevated 5xx “context canceled” errors impacting serverless inference",
"timestamp": "Apr \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e13:45\u003c/var\u003e - \u003cvar data-var='time'\u003e19:33\u003c/var\u003e UTC"
},
{
"code": "5gsk0hfctqp5",
"impact": "major",
"message": "The issue is resolved, and service is operating normally.",
"name": "Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models",
"timestamp": "Apr \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e10:38\u003c/var\u003e - \u003cvar data-var='time'\u003e11:37\u003c/var\u003e UTC"
},
{
"code": "1y9gxbdcqb71",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Intermittent errors impacting some Serverless Inference models in ATL1",
"timestamp": "Apr \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e22:26\u003c/var\u003e - \u003cvar data-var='time'\u003e23:51\u003c/var\u003e UTC"
},
{
"code": "2rby4tk1q6mm",
"impact": "minor",
"message": "Our Engineering team has confirmed that the issue impacting App Platform deployments and Kubernetes (DOKS) nodes has been fully resolved at 09:22 UTC. Users may already notice improvements while deploying apps and DOKS nodes.\n\nAll App Platform deployments are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf 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.",
"name": "App Platform Deployments",
"timestamp": "Apr \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e08:08\u003c/var\u003e - \u003cvar data-var='time'\u003e10:09\u003c/var\u003e UTC"
},
{
"code": "p1jbzg2bvhj9",
"impact": "minor",
"message": "Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.\n\nAll the services should be functioning as expected.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!",
"name": "Cloud UI for Managed Kubernetes",
"timestamp": "Apr \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e07:01\u003c/var\u003e - \u003cvar data-var='time'\u003e08:46\u003c/var\u003e UTC"
},
{
"code": "tc8w4zwkvkn7",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance in All Regions 2026-04-16 09:00 UTC",
"timestamp": "Apr \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e09:07\u003c/var\u003e - \u003cvar data-var='time'\u003e18:31\u003c/var\u003e UTC"
},
{
"code": "zjd34dpv45vr",
"impact": "minor",
"message": "Our Engineering team has resolved the issue that was impacting the DigitalOcean API and the Cloud Control Panel. The system is now operating normally.\n\nDuring the incident, users may have experienced difficulties accessing droplets, viewing the Droplets page, or performing CRUD (Create, Read, Update, Delete) operations via the API. We have verified that the issue has been fully resolved.\n\nWe apologize for the inconvenience this may have caused. If you continue to experience any issues, please submit a support ticket through the Cloud Control Panel so our team can assist you further.",
"name": "Cloud Control Panel and API",
"timestamp": "Apr \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e11:06\u003c/var\u003e - \u003cvar data-var='time'\u003e11:47\u003c/var\u003e UTC"
},
{
"code": "v6qdbpt1dcd3",
"impact": "minor",
"message": "Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected.\n\nWe apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.",
"name": "DNS Resolution for .co TLD",
"timestamp": "Apr \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e21:22\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e14:10\u003c/var\u003e UTC"
},
{
"code": "8whvfslclskl",
"impact": "none",
"message": "From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. 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.",
"name": "Spaces availability in NYC3",
"timestamp": "Apr \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e18:27\u003c/var\u003e - \u003cvar data-var='time'\u003e18:27\u003c/var\u003e UTC"
},
{
"code": "cxh9f0hgw934",
"impact": "minor",
"message": "From 23:20 UTC to 02:00 UTC, users may have experienced elevated error rates due to service instability, which resulted in intermittent HTTP 500 errors and terminated connections.\n\nOur Engineering team has confirmed full resolution of the issue, and all systems are now operating normally.\n\nIf you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.",
"name": "Serverless Inference",
"timestamp": "Apr \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e01:07\u003c/var\u003e - \u003cvar data-var='time'\u003e02:56\u003c/var\u003e UTC"
},
{
"code": "4cc9krk5gy9p",
"impact": "none",
"message": "From 16:07 to 16:50 UTC, Our Engineering team observed an issue with App Platform Deployments in all regions. During this time, App deployments of both new and existing apps would have been affected. Our team has fully resolved the issues as of 16:50 UTC. All new and existing App deployments should now be functioning as expected. 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.",
"name": "App Platform Deployments",
"timestamp": "Apr \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e17:57\u003c/var\u003e - \u003cvar data-var='time'\u003e17:57\u003c/var\u003e UTC"
},
{
"code": "8hj57rv32g6n",
"impact": "minor",
"message": "Our Engineering team has resolved the issue with resize operations for Managed Databases and should now be operating normally. 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.",
"name": "Managed Database Resizes",
"timestamp": "Apr \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e12:53\u003c/var\u003e - \u003cvar data-var='time'\u003e15:19\u003c/var\u003e UTC"
},
{
"code": "wjyr2cz6y3xb",
"impact": "none",
"message": "Our Engineering team has confirmed full resolution of the issue with creating Droplets in all regions. Users should be able to create Droplets without issue.\n\nWe apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.",
"name": "Droplet Availability in All Regions",
"timestamp": "Apr \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e20:32\u003c/var\u003e - \u003cvar data-var='time'\u003e21:06\u003c/var\u003e UTC"
},
{
"code": "27n83qgxzqcp",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] MongoDB Maintenance - BLR1, NYC3, SFO2, SGP1, SYD1, TOR1",
"timestamp": "Apr \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e18:00\u003c/var\u003e - \u003cvar data-var='time'\u003e22:51\u003c/var\u003e UTC"
},
{
"code": "njbgw45nywk1",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] MongoDB Maintenance - AMS3, ATL1, LON1, NYC1, NYC2, SFO3",
"timestamp": "Apr \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e18:00\u003c/var\u003e - \u003cvar data-var='time'\u003e22:25\u003c/var\u003e UTC"
},
{
"code": "3kr7638lkhy9",
"impact": "none",
"message": "Our Engineering team has resolved the control plane disruption that occurred from 17:06 to 17:18 UTC. During this time, users may have experienced intermittent issues with managing their resources through the Cloud Control Panel or DigitalOcean API. The root cause of the disruption was identified and addressed, and all services are now operating normally. \n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.",
"name": "Control Plane",
"timestamp": "Apr \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e17:49\u003c/var\u003e - \u003cvar data-var='time'\u003e17:49\u003c/var\u003e UTC"
},
{
"code": "bx60kdvsvtvb",
"impact": "minor",
"message": "Service has been fully restored, and the model is now operating normally. We have implemented improvements to enhance stability and reduce the likelihood of similar issues in the future.",
"name": "Serverless Inference - High error rates for open source models ( Qwen 3 32B)",
"timestamp": "Apr \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e12:49\u003c/var\u003e - \u003cvar data-var='time'\u003e15:50\u003c/var\u003e UTC"
},
{
"code": "grhp94sd84gd",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Serverless Inference Issue",
"timestamp": "Apr \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e12:28\u003c/var\u003e - \u003cvar data-var='time'\u003e18:02\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "df2vx9wzqfdz",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] FRA1 MongoDB Maintenance",
"timestamp": "Mar \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e19:00\u003c/var\u003e - \u003cvar data-var='time'\u003e23:16\u003c/var\u003e UTC"
},
{
"code": "p3ybkddb3wmm",
"impact": "major",
"message": "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.",
"name": "Gradient AI Platform agents and services Accessibility",
"timestamp": "Mar \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e08:50\u003c/var\u003e - \u003cvar data-var='time'\u003e14:14\u003c/var\u003e UTC"
},
{
"code": "lg35bbsgn1cp",
"impact": "minor",
"message": "The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 00:08am UTC \u0026amp; 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.\n\nWe confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding.\n\nHowever, 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.",
"name": "App platform seeing delays in deployments across FRA1 region",
"timestamp": "Mar \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e10:32\u003c/var\u003e - \u003cvar data-var='time'\u003e12:01\u003c/var\u003e UTC"
},
{
"code": "bx2zgwbwgltm",
"impact": "minor",
"message": "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.",
"name": "Gradient AI model availability",
"timestamp": "Mar \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:49\u003c/var\u003e UTC"
},
{
"code": "pypzpnnc373w",
"impact": "none",
"message": "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.",
"name": "Cloud Control Panel and API",
"timestamp": "Mar \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e17:39\u003c/var\u003e - \u003cvar data-var='time'\u003e17:39\u003c/var\u003e UTC"
},
{
"code": "9pns1qlx6hqc",
"impact": "minor",
"message": "The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally.\nContact support if issues persist.",
"name": "Degraded performance with BYOK Anthropic models",
"timestamp": "Mar \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e02:55\u003c/var\u003e - \u003cvar data-var='time'\u003e03:31\u003c/var\u003e UTC"
},
{
"code": "0bhc3myf4l0s",
"impact": "minor",
"message": "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.\n\nUsers should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.",
"name": "Delay in App Platform Deployments",
"timestamp": "Mar \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e21:30\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e01:47\u003c/var\u003e UTC"
},
{
"code": "hl6fx4s2ydm1",
"impact": "minor",
"message": "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.",
"name": "Newly Created Managed Kubernetes Nodes",
"timestamp": "Mar \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e11:26\u003c/var\u003e - \u003cvar data-var='time'\u003e16:35\u003c/var\u003e UTC"
},
{
"code": "cqn6lrhjd3tr",
"impact": "none",
"message": "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.",
"name": "Ubuntu/Debian Package Mirror Failure",
"timestamp": "Mar \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e19:23\u003c/var\u003e - \u003cvar data-var='time'\u003e19:23\u003c/var\u003e UTC"
},
{
"code": "k0cd863c8105",
"impact": "none",
"message": "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.\n\nWe 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/.",
"name": "HTTP 522 Error on App Platform",
"timestamp": "Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e21:22\u003c/var\u003e - \u003cvar data-var='time'\u003e21:22\u003c/var\u003e UTC"
},
{
"code": "rw6hzkyc1fh9",
"impact": "maintenance",
"message": "This scheduled maintenance is now complete across all regions. Thank you for your patience and understanding throughout this process.",
"name": "[Scheduled] Core Infrastructure Maintenance in All Regions 2026-03-03 10:00 UTC",
"timestamp": "Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e11:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:55\u003c/var\u003e UTC"
},
{
"code": "8c4s46c9r7m9",
"impact": "minor",
"message": "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.\n\nUsers should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.",
"name": "App Platform Deployments",
"timestamp": "Mar \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e23:28\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e01:12\u003c/var\u003e UTC"
},
{
"code": "c7z5d74zrdhp",
"impact": "minor",
"message": "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.\n\nOur Engineering team has confirmed full resolution of the issue, and Internal Load Balancers should now be functioning normally.\n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience caused.",
"name": "Internal Load Balancers Connectivity",
"timestamp": "Mar \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e00:23\u003c/var\u003e - \u003cvar data-var='time'\u003e01:52\u003c/var\u003e UTC"
},
{
"code": "ltxtzxhs12xt",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance in SFO2 and SFO3",
"timestamp": "Mar \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e13:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:00\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "7pxx131dr1qt",
"impact": "minor",
"message": "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.\n\nAll 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.\n\nIf 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.",
"name": "App Platform Deployments",
"timestamp": "Feb \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e17:14\u003c/var\u003e - Feb \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e04:55\u003c/var\u003e UTC"
},
{
"code": "1xs8w0shdkh2",
"impact": "minor",
"message": "Issue resolved.\nCause: A few requests made to the Llama 3.3-70B model caused issues.\nImpact: Intermittent errors when interacting with the model through serverless inference and/or with agents created using this model.\nContact support if issues persist.",
"name": "Intermittent Errors with Llama 3.3-70B",
"timestamp": "Feb \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e22:23\u003c/var\u003e UTC"
},
{
"code": "d60xpcw15jqc",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance in AMS3, FRA1, and LON1",
"timestamp": "Feb \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e20:00\u003c/var\u003e UTC"
},
{
"code": "hbh0dzgwz3s5",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance in BLR1 and SGP1",
"timestamp": "Feb \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e18:00\u003c/var\u003e UTC"
},
{
"code": "ktx53twsx7rc",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Network Maintenance - SFO1",
"timestamp": "Feb \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e21:28\u003c/var\u003e UTC"
},
{
"code": "5yj80hh32wrp",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance in SYD1",
"timestamp": "Feb \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e17:00\u003c/var\u003e UTC"
},
{
"code": "8qw62mg8crkh",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance NYC3",
"timestamp": "Feb \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e19:00\u003c/var\u003e - Feb \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e23:00\u003c/var\u003e UTC"
},
{
"code": "wcdry38l3ls5",
"impact": "minor",
"message": "The issue impacting the visibility of Cloud Panel has been confirmed to be resolved. Between approximately 16:08 PM \u0026amp; 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. \n\nOur 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. \n\nHowever, 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.",
"name": "Control Panel Visibility",
"timestamp": "Feb \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e17:34\u003c/var\u003e - \u003cvar data-var='time'\u003e18:42\u003c/var\u003e UTC"
},
{
"code": "l10ntywl5ssb",
"impact": "none",
"message": "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. \n\nAll operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account. \n\nThank you for your patience while we worked to resolve this issue.",
"name": "Spaces Availability in NYC3",
"timestamp": "Feb \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e07:36\u003c/var\u003e - \u003cvar data-var='time'\u003e10:58\u003c/var\u003e UTC"
},
{
"code": "t8b645wwhm7m",
"impact": "none",
"message": "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.\n\nIf you experience any further issues, please contact Support by creating a Support ticket from within your account.\n\nThank you for your patience while we worked to resolve this issue.",
"name": "Droplet Limit Increase Feature",
"timestamp": "Feb \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e06:38\u003c/var\u003e - \u003cvar data-var='time'\u003e09:24\u003c/var\u003e UTC"
},
{
"code": "wvx8hcnvynv0",
"impact": "minor",
"message": "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.\n\nUsers should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.\n\nHowever, 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.",
"name": "Delay in App Platform Deployments",
"timestamp": "Feb \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e19:06\u003c/var\u003e - \u003cvar data-var='time'\u003e19:34\u003c/var\u003e UTC"
},
{
"code": "ftlzzqf5vswr",
"impact": "minor",
"message": "Our Engineering team has confirmed the full resolution of the issue with MongoDB Clusters.\n\nThank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.",
"name": "MongoDB Cluster Creation",
"timestamp": "Feb \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e05:42\u003c/var\u003e - \u003cvar data-var='time'\u003e12:06\u003c/var\u003e UTC"
},
{
"code": "v86lxs9fkd3n",
"impact": "minor",
"message": "The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 08:52 UTC \u0026amp; 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.\n\nWe confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding.\n\nHowever, 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.",
"name": "App platform seeing delays in deployments across all regions.",
"timestamp": "Feb \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e11:50\u003c/var\u003e - \u003cvar data-var='time'\u003e13:08\u003c/var\u003e UTC"
},
{
"code": "vn66l2pfcr7l",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Network Maintenance - AMS2",
"timestamp": "Feb \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e17:00\u003c/var\u003e UTC"
},
{
"code": "l5cn824y23b3",
"impact": "minor",
"message": "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.\n\nIf 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.",
"name": "Cloud Control Panel",
"timestamp": "Feb \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e17:27\u003c/var\u003e - \u003cvar data-var='time'\u003e18:53\u003c/var\u003e UTC"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "7jwkcbg34qsp",
"impact": "minor",
"message": "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.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Kubernetes Clusters and Droplets in FRA1 region",
"timestamp": "Jan \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e11:27\u003c/var\u003e - \u003cvar data-var='time'\u003e17:37\u003c/var\u003e UTC"
},
{
"code": "3lq0zklcll0k",
"impact": "minor",
"message": "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.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Droplet Based Events in FRA1",
"timestamp": "Jan \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e00:45\u003c/var\u003e - \u003cvar data-var='time'\u003e04:27\u003c/var\u003e UTC"
},
{
"code": "4rdkylf7z0q0",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Network Maintenance - NYC3",
"timestamp": "Jan \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e13:00\u003c/var\u003e UTC"
},
{
"code": "fv4s9bqmq41q",
"impact": "major",
"message": "From 20:45 UTC to 21:06 UTC, users may have experienced issue affecting the Cloud Control Panel, API, and related services.\n\nOur Engineering team has confirmed that the issue is fully resolved, and all systems are now operating normally.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Cloud Control Panel and API",
"timestamp": "Jan \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e21:06\u003c/var\u003e - \u003cvar data-var='time'\u003e22:44\u003c/var\u003e UTC"
},
{
"code": "0n647pxkdmg8",
"impact": "minor",
"message": "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.\n\nWe appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.",
"name": "App Platform Deployments",
"timestamp": "Jan \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e18:05\u003c/var\u003e - \u003cvar data-var='time'\u003e18:25\u003c/var\u003e UTC"
},
{
"code": "pbkc3n1l5p69",
"impact": "minor",
"message": "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.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Account access and Payment",
"timestamp": "Jan \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e07:16\u003c/var\u003e - \u003cvar data-var='time'\u003e09:18\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "l6sjf6bftj1z",
"impact": "minor",
"message": "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.\n\nIf you experience any further problems or have any questions, please open a support ticket within your account.",
"name": "App Platform Static Websites in NYC3 Region",
"timestamp": "Dec \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e19:25\u003c/var\u003e - \u003cvar data-var='time'\u003e22:34\u003c/var\u003e UTC"
},
{
"code": "q39pqxrdmfxx",
"impact": "minor",
"message": "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.\n\nIf you experience any further problems or have any questions, please open a support ticket within your account.",
"name": "API and Cloud Requests",
"timestamp": "Dec \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e18:46\u003c/var\u003e - \u003cvar data-var='time'\u003e21:34\u003c/var\u003e UTC"
},
{
"code": "6d03lqrt8y1y",
"impact": "none",
"message": "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.",
"name": "Spaces Access Keys and DigitalOcean Container Registry",
"timestamp": "Dec \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e16:19\u003c/var\u003e - \u003cvar data-var='time'\u003e16:19\u003c/var\u003e UTC"
},
{
"code": "v45dn1l41w75",
"impact": "minor",
"message": "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.\n\nOur Engineering team has confirmed that the issue is now fully resolved, and Recovery Console access has been fully restored and is operating normally.\n\nIf you continue to experience any difficulties, please open a ticket with our Support team. We apologize for the inconvenience caused.",
"name": "Recovery Console Accessibility",
"timestamp": "Dec \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e20:33\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "95y35dth4w7g",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance 2025-12-10 18:00 UTC",
"timestamp": "Dec \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e18:00\u003c/var\u003e - \u003cvar data-var='time'\u003e20:00\u003c/var\u003e UTC"
},
{
"code": "fjkv8m6qphr7",
"impact": "minor",
"message": "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.\n\nWe 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.",
"name": "App Platform Static Websites",
"timestamp": "Dec \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e18:08\u003c/var\u003e - \u003cvar data-var='time'\u003e19:08\u003c/var\u003e UTC"
},
{
"code": "d8tqp9h5x8s9",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Rescheduled: Core Infrastructure Maintenance SFO2",
"timestamp": "Dec \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e12:21\u003c/var\u003e UTC"
},
{
"code": "lqyryfqpm9x5",
"impact": "minor",
"message": "From 18:02 UTC to 21:10 UTC, customers in the BLR1 region who had not previously created an app may have experienced DOCR (DigitalOcean Container Registry) access errors when attempting to create new apps.\n\nOur Engineering team has confirmed that the issue is fully resolved, and all systems are now operating normally.\n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for the inconvenience caused.",
"name": "DOCR Access Errors for New App Creation",
"timestamp": "Dec \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e20:41\u003c/var\u003e - \u003cvar data-var='time'\u003e22:08\u003c/var\u003e UTC"
},
{
"code": "f1n8ph6nyb4w",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance NYC3",
"timestamp": "Dec \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e12:00\u003c/var\u003e UTC"
},
{
"code": "kntljttrj9gt",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance FRA1",
"timestamp": "Dec \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e22:00\u003c/var\u003e UTC"
},
{
"code": "vx97nyr0q9ws",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance SFO3",
"timestamp": "Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e UTC"
},
{
"code": "528ghwz6806b",
"impact": "minor",
"message": "Our Engineering team has confirmed the full resolution of this issue. From approximately 08:51 UTC – 09:12 UTC, users may have experienced difficulties signing in or accessing resources through the Control Panel and API due to an upstream provider issue. The upstream provider has fixed the issue, and all services are now functioning normally. If you continue to experience problems, please open a ticket with our support team.\n\nThank you for your patience and we apologize for any inconvenience.",
"name": "Control Panel Access",
"timestamp": "Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e09:23\u003c/var\u003e - \u003cvar data-var='time'\u003e10:06\u003c/var\u003e UTC"
},
{
"code": "kw1ms7q9gqsx",
"impact": "minor",
"message": "From As of 16:34 to 19:47 UTC, may have encountered errors listing backup operations for their PostgreSQL, MySQL, OpenSearch, Redis and Kafa clusters through the API and UI. Our Engineering team has confirmed full resolution of the issue, users should no longer experience issues with listing backup operations. \n\nThank you for your patience, and we apologize for the inconvenience. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.",
"name": "Degradation in Managed Databases",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e18:03\u003c/var\u003e - \u003cvar data-var='time'\u003e22:04\u003c/var\u003e UTC"
},
{
"code": "64t0wg557331",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance AMS3",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:34\u003c/var\u003e UTC"
},
{
"code": "tjrfwt5bkwd9",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance NYC1",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:04\u003c/var\u003e UTC"
},
{
"code": "c248f883bkv0",
"impact": "none",
"message": "During the timeframe 06:24 UTC – 13:45 UTC, the Gradient AI platform experienced a period of degraded functionality affecting a limited set of features. While the platform remained accessible, the below components did not perform as expected.\n\nImpacted Areas:\n- Gradient Agent Evaluations\n- Agent trace visibility\n- Access management for traces\n- Agent deletion for agents with traces enabled\n\nOur Engineering team identified the underlying cause and restored full functionality across all affected components. The platform has remained stable since resolution, and monitoring confirms normal performance.",
"name": "Gradient AI Platform – Service Degradation",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e11:00\u003c/var\u003e - \u003cvar data-var='time'\u003e11:00\u003c/var\u003e UTC"
},
{
"code": "cbcfr9zc9vvd",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance SGP1",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:50\u003c/var\u003e UTC"
},
{
"code": "cc9hpt069n76",
"impact": "minor",
"message": "Our Engineering team has fully implemented and confirmed the effectiveness of the fix for the increased guardrail latency. System performance has returned to normal, and all affected services are operating as expected.\nWe have observed stable metrics during extended monitoring and have not detected any further latency or interruptions.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Guardrails Service Disruption Impacting Customers",
"timestamp": "Dec \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e20:55\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e15:45\u003c/var\u003e UTC"
},
{
"code": "4k500h2lyjhv",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance TOR1",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e14:07\u003c/var\u003e UTC"
},
{
"code": "cd85c79bnc0g",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance LON1",
"timestamp": "Dec \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e17:00\u003c/var\u003e - \u003cvar data-var='time'\u003e21:05\u003c/var\u003e UTC"
},
{
"code": "v337y6wwb7f0",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance SFO2",
"timestamp": "Dec \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "s8tnks7lpfsj",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Core Infrastructure Maintenance SYD1",
"timestamp": "Nov \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e21:41\u003c/var\u003e UTC"
},
{
"code": "hdl716jq8pxl",
"impact": "none",
"message": "From 18:55 to 19:32 UTC, Our Engineering team observed an issue with all control plane operations (Create, Scale, Fork, etc ) for all non-Mongo Managed Database clusters. During this time, users encountered long running requests made either through the Cloud Console UI or API, including provisioning new clusters, listing clusters, etc. Our team has fully resolved the issues as of 19:32 UTC All services for non-Mongo Managed Databases should now be operating normally. 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.",
"name": "Managed Databases",
"timestamp": "Nov \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e20:19\u003c/var\u003e - \u003cvar data-var='time'\u003e20:19\u003c/var\u003e UTC"
},
{
"code": "lgt5xs2843rx",
"impact": "minor",
"message": "Our Engineering team has confirmed that the external network incident affecting multiple DigitalOcean services has been fully mitigated. The impacted services including Gen AI tools, App Platform, Load Balancers, Spaces, and provisioning or management actions for new clusters have recovered and are now operating normally. All requests are completing successfully.\n\nThank you for your patience. If you continue to experience any issues, please open a support ticket from within your account.",
"name": "Multiple Services Disruption",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e12:26\u003c/var\u003e - \u003cvar data-var='time'\u003e20:39\u003c/var\u003e UTC"
},
{
"code": "h88jv8qz32v7",
"impact": "none",
"message": "From 16:59 to 17:34 UTC, our Engineering team observed an issue with block storage volumes in the NYC1 and AMS3 regions. During this time, users may have experienced failures when attempting create, snapshot, attach, detach, or resize volumes. There was no impact to performance or availability of existing volumes. Our team has fully resolved the issues as of 17:34 UTC and volumes should be operating normally. 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.",
"name": "Block Storage Volumes in NYC1 and AMS3",
"timestamp": "Nov \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e19:26\u003c/var\u003e - \u003cvar data-var='time'\u003e19:26\u003c/var\u003e UTC"
},
{
"code": "pq520421vl6z",
"impact": "minor",
"message": "Our Engineering team has confirmed full resolution of the issue with failed create events with their Spaces, App Platform, and DOCR services.\n\nFrom 06:15 UTC AM to 09:53 AM UTC, the Spaces, App Platform, and DOCR services were impacted and have since been restored to normal operation.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!",
"name": "Creation Events Failing for Spaces, App Platform, DOCR",
"timestamp": "Nov \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e08:31\u003c/var\u003e - \u003cvar data-var='time'\u003e11:05\u003c/var\u003e UTC"
},
{
"code": "x0jf50r0hq5k",
"impact": "minor",
"message": "Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region. Users should experience expected performance when accessing Droplets and other services. \n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Network Connectivity in BLR1",
"timestamp": "Nov \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e18:07\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e07:11\u003c/var\u003e UTC"
},
{
"code": "4vs70qvnykcy",
"impact": "none",
"message": "From 13:50 to 14:15 UTC, our Engineering team observed an issue with an upstream provider impacting network connectivity in the BLR1 region.\n\nDuring this time, users may have experienced increase in latency or packet loss when accessing Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters in BLR1 region. \n\nThe impact has now subsided and as of 14:15 UTC, users should already experience better performance when accessing Droplets and other services.\n\nWe apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account.",
"name": "Network connectivity in BLR1",
"timestamp": "Nov \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e15:15\u003c/var\u003e - \u003cvar data-var='time'\u003e15:15\u003c/var\u003e UTC"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "yq898vpw1nch",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Gradient AI Platform Agent Creation.",
"timestamp": "Oct \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e20:26\u003c/var\u003e - \u003cvar data-var='time'\u003e23:59\u003c/var\u003e UTC"
},
{
"code": "8ycq31pppzln",
"impact": "minor",
"message": "Our Engineering team has resolved the issue affecting Garbage Collection in container registries, and all services are operating normally.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Container Registry Garbage Collection",
"timestamp": "Oct \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e11:30\u003c/var\u003e - \u003cvar data-var='time'\u003e19:58\u003c/var\u003e UTC"
},
{
"code": "vzcy8ym8266d",
"impact": "none",
"message": "Between 14:28 PM \u0026amp; 14:35 PM UTC today, our Engineering team has identified an issue impacting the availability of multiple services, including Droplets, Volumes, Spaces, Kubernetes, Load Balancers, Managed Databases, etc. During this period, users might have noticed 500 Internal Server Errors or 503 Service Unavailable Errors when accessing these services and other dependent services.\n\nOur team has taken appropriate measures to address the issue. We can confirm that all services have been restored and are now functioning normally.\n\nWe regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.",
"name": "Availability Across Multiple Services",
"timestamp": "Oct \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e18:11\u003c/var\u003e - \u003cvar data-var='time'\u003e18:11\u003c/var\u003e UTC"
},
{
"code": "bbv2b24xjx8p",
"impact": "minor",
"message": "Our Engineering team has resolved the performance issue affecting Spaces. From approximately 15:42 UTC - 16:14 UTC, customers may have experienced slow performance or limited availability when accessing Spaces, its objects via the Control Panel or API. Accessing and creating Container Registry along with App builds were also affected during this time. All services should now be functioning normally. \n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "Spaces Availability, Container Registry creation and App builds",
"timestamp": "Oct \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e16:17\u003c/var\u003e - \u003cvar data-var='time'\u003e18:33\u003c/var\u003e UTC"
},
{
"code": "btbdfs0fgcxv",
"impact": "minor",
"message": "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.\n\nWe appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.",
"name": "App Platform Deployments",
"timestamp": "Oct \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e16:40\u003c/var\u003e - \u003cvar data-var='time'\u003e17:12\u003c/var\u003e UTC"
},
{
"code": "sxlrj088l11b",
"impact": "minor",
"message": "Between 08:00 UTC and 22:53 UTC, an issue with an upstream provider affected multiple DigitalOcean services, including SMS-based 2FA (causing code delivery failures), Docker Hub-hosted images (impacting Managed Kubernetes and App Platform deployments), and SnapShooter backup jobs. The issue has been resolved, and all services are now stable and operating normally. \n\nWe appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket from within the Cloud Control Panel for further analysis.",
"name": "Multiple Services Disruption",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e10:21\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e05:41\u003c/var\u003e UTC"
},
{
"code": "5439v2jmf61s",
"impact": "minor",
"message": "Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.",
"name": "IPv6 Connectivity in Multiple Regions",
"timestamp": "Oct \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e00:19\u003c/var\u003e - \u003cvar data-var='time'\u003e04:28\u003c/var\u003e UTC"
},
{
"code": "yq1ct2d6dhxj",
"impact": "minor",
"message": "Our Engineering team has resolved the issue affecting the creation of NVDIA GPU nodes on new Kubernetes clusters. Users will no longer encounter issues when creating NVDIA GPU nodes on new Kubernetes clusters. \n\nIf you continue to experience any issues, please open a support ticket. We sincerely apologize for the inconvenience caused and appreciate your understanding.",
"name": "GPU Node Creation on New Kubernetes Clusters",
"timestamp": "Oct \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e11:29\u003c/var\u003e - \u003cvar data-var='time'\u003e14:25\u003c/var\u003e UTC"
},
{
"code": "qnkmbbyfqzfl",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] NYC1 Network Maintenance",
"timestamp": "Oct \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e22:00\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "yz9lft840mtl",
"impact": "minor",
"message": "Our Engineering team has confirmed the full resolution of the issue with Managed Database Clusters.\n\nThank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.",
"name": "Managed Database Clusters",
"timestamp": "Oct \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e11:56\u003c/var\u003e - \u003cvar data-var='time'\u003e22:18\u003c/var\u003e UTC"
},
{
"code": "mywtgs9jfj5t",
"impact": "minor",
"message": "Our Engineering team has confirmed that the issue affecting Spaces access in the FRA1 region has been fully resolved.\n\nUsers should now be able to list and access their Spaces objects without any errors. We appreciate your patience and understanding while we worked to restore normal service.\n\nIf you experience any further problems or have any questions, please open a support ticket within your account.",
"name": "Spaces Access in FRA1",
"timestamp": "Oct \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e11:23\u003c/var\u003e - \u003cvar data-var='time'\u003e14:45\u003c/var\u003e UTC"
},
{
"code": "t673fy82j2s7",
"impact": "major",
"message": "Our Engineering team has resolved the issue affecting multiple services, including the Cloud Control Panel and API.\n\nUsers should now be able to access their accounts and use the API without any errors.\n\nIf you still encounter any issues, please launch a ticket with our Support team.",
"name": "Cloud Control Panel and Multiple Services",
"timestamp": "Oct \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e21:56\u003c/var\u003e - \u003cvar data-var='time'\u003e23:58\u003c/var\u003e UTC"
},
{
"code": "f152cz9k1jy4",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] SYD1 Network Maintenance",
"timestamp": "Oct \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e11:00\u003c/var\u003e - \u003cvar data-var='time'\u003e14:00\u003c/var\u003e UTC"
},
{
"code": "6fbdtmpjhbkg",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] NYC3 Network Maintenance",
"timestamp": "Oct \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e22:00\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "dnmqzlgnf2lz",
"impact": "minor",
"message": "Our Engineering team has resolved the issue impacting Managed Kubernetes clusters in our TOR1 region. We apologize for the inconvenience and appreciate your patience throughout this event. If you experience any further problems or have any questions, please open a support ticket within your account.",
"name": "Kubernetes Clusters in TOR1",
"timestamp": "Oct \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e18:15\u003c/var\u003e - \u003cvar data-var='time'\u003e19:11\u003c/var\u003e UTC"
},
{
"code": "ss2bxhr4j58c",
"impact": "none",
"message": "From 14:30 to 14:44 UTC, our Engineering team observed an issue impacting our API. \n\nDuring this time, users may have experienced intermittent errors when trying to use the public API at api.digitalocean.com or processing API requests. Users may have also experienced issues with processing Droplet and Kubernetes cluster creations and cluster actions.\n\nThe impact has now subsided and as of 14:44 UTC, users should no longer be experiencing issues with accessing the API and all services should now be functioning normally.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "API Availability",
"timestamp": "Oct \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e15:40\u003c/var\u003e - \u003cvar data-var='time'\u003e15:40\u003c/var\u003e UTC"
},
{
"code": "4pgsj30c2k1g",
"impact": "minor",
"message": "Our Engineering team has resolved the connectivity issue with Managed Database PostgreSQL clusters in all regions that are using PGBouncer and some legacy MD5 passwords.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.",
"name": "PostgreSQL Managed Database Connectivity",
"timestamp": "Oct \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e00:05\u003c/var\u003e - \u003cvar data-var='time'\u003e06:06\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}