Oct <var data-var='date'> 5</var>, <var data-var='time'>12:13</var> UTC Resolved - Our Engineering team fully resolved the VPC Networking disruption as of 10:29 UTC. Customers can now create and delete VPC peering connections, subnets, and routes as expected. Following the recovery, we monitored the affected systems and confirmed that VPC Networking operations remain stable. We apologize for any inconvenience this disruption may have caused. If you continue to experience unexpected behavior, please open a ticket with our Support team for further assistance. Oct <var data-var='date'> 5</var>, <var data-var='time'>11:02</var> UTC Monitoring - Our Engineering team has implemented a fix for the VPC Networking disruption. Customers should now be able to create and delete VPC peering connections, subnets, and routes as expected. Previously pending operations have been cleared, and VPC Networking operations are returning to normal. Our Engineering team is monitoring the affected systems to ensure continued stability and verify that operations remain healthy. We appreciate your patience and will provide another update once normal operation has been fully confirmed. Oct <var data-var='date'> 5</var>, <var data-var='time'>10:38</var> UTC Identified - Our Engineering team identified a disruption affecting VPC Networking operations that began at approximately 08:48 UTC. During this time, customers may have experienced delays or failures when creating or deleting VPC peerings, VPC Native DOKS clusters, or Private Network Connections (PNCs), as well as when adding cluster members. Creating routes and subnets may also have been affected. Operations are now returning to normal, and our Engineering team is monitoring the affected systems to ensure continued stability. Existing VPC resources and network connectivity remain unaffected. We will provide another update as soon as more information becomes available.

VPC Networking Availability

Oct <var data-var='date'> 3</var>, <var data-var='time'>14:51</var> UTC Resolved - From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unexpected behavior, please open a support ticket so our team can investigate and assist you.

A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)

Sep <var data-var='date'>16</var>, <var data-var='time'>21:09</var> UTC Resolved - From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience. Sep <var data-var='date'>16</var>, <var data-var='time'>14:07</var> UTC Monitoring - The Support Portal and ticket creation are now accessible. Our upstream provider has applied a fix, and we've verified ticket creation and review are working as expected. We'll continue monitoring for the next 2 hours to confirm full stability and will post a final update once the incident is closed. If you're still unable to access the portal, please use our Support Contact form as a backup: https://www.digitalocean.com/company/contact/support We apologize for the disruption and appreciate your patience. Sep <var data-var='date'>16</var>, <var data-var='time'>09:48</var> UTC Investigating - Our Support Portal is currently experiencing issues due to a third-party service disruption impacting our systems. During this time, customers may be unable to access the Support Portal or create new support tickets for their concerns. Existing support requests may also experience delayed responses from our Support team. As a workaround if you're unable to access the Support Portal or need to create a new support ticket, please submit your request via Support Contact form: https://www.digitalocean.com/company/contact/support. We apologize for the inconvenience and appreciate your patience while we work to resolve the issue. We'll provide another update as soon as we have more information.

Support Portal Service Disruption

Sep <var data-var='date'> 9</var>, <var data-var='time'>12:25</var> UTC Resolved - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>11:32</var> UTC Monitoring - The power issue affecting part of our ATL1 datacenter has been fully resolved. Power redundancy has been restored, and any potential customer impact has been mitigated. We will continue monitoring the environment to ensure continued stability. Sep <var data-var='date'> 9</var>, <var data-var='time'>10:47</var> UTC Investigating - We are investigating a power issue affecting part of our ATL1 datacenter. Redundant power systems are keeping servers online, and we have not observed any server outages. However, available power capacity is reduced, which may cause degraded performance for some GPU workloads, particularly during periods of high utilization. Our datacenter and infrastructure teams are working to restore full power redundancy. We will provide an update as more information becomes available. We apologize for the inconvenience and appreciate your patience.

Power Degradation impacting GPU Performance in ATL1

Aug <var data-var='date'>27</var>, <var data-var='time'>17:40</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>27</var>, <var data-var='time'>16:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>26</var>, <var data-var='time'>18:36</var> UTC Scheduled - Start: 2026-08-27 16:00 UTC End: 2026-08-27 18:00 UTC Hello, During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the BLR1 region in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-26. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Rescheduled: Spaces Maintenance in BLR1

Aug <var data-var='date'>27</var>, <var data-var='time'>08:30</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>27</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>26</var>, <var data-var='time'>05:56</var> UTC Scheduled - Start: 2026-08-27 05:30 UTC End: 2026-08-27 08:30 UTC Hello, During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the NYC3, SFO2, and SFO3 regions in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-26. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket Thank you, Team DigitalOcean

Rescheduled: Spaces Maintenance in NYC3, SFO2 and SFO3

Aug <var data-var='date'>26</var>, <var data-var='time'>16:28</var> UTC Completed - The ongoing maintenance for Spaces has been cancelled and will be rescheduled for tomorrow. We apologize for any inconvenience and appreciate your understanding. Aug <var data-var='date'>26</var>, <var data-var='time'>16:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>26</var>, <var data-var='time'>05:42</var> UTC Scheduled - Start: 2026-08-26 16:00 UTC End: 2026-08-26 18:00 UTC Hello, During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the BLR1 region in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-25. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket Thank you, Team DigitalOcean

Aug <var data-var='date'>26</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>26</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>26</var>, <var data-var='time'>05:43</var> UTC Scheduled - Start: 2026-08-26 06:00 UTC End: 2026-08-26 09:00 UTC Hello, During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the AMS3, FRA1 and TOR1 regions in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-25. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket Thank you, Team DigitalOcean

Rescheduled: Spaces Maintenance in AMS3, FRA1 and TOR1

Aug <var data-var='date'>25</var>, <var data-var='time'>19:04</var> UTC Resolved - 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. Thank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account Aug <var data-var='date'>25</var>, <var data-var='time'>16:30</var> UTC Update - Our Engineering team has continued to monitor the health of all services and has observed no recurrence of impact over the past 12+ hours. We will continue to monitor services for a short period to confirm stability before we mark this incident resolved. We understand the impact this incident had for DigitalOcean users and we will publish a postmortem on the status page to provide further details on root cause and mitigation. Aug <var data-var='date'>25</var>, <var data-var='time'>00:54</var> UTC Monitoring - Our Engineering team has implemented mitigation measures to address the issue impacting the DigitalOcean public API and Cloud Control Panel. We are seeing improvements, and users should now be able to access the Cloud Control Panel and use the public API normally. We are continuing to monitor the service to ensure it remains stable and will provide further updates as more information becomes available. We appreciate your patience and understanding. Aug <var data-var='date'>24</var>, <var data-var='time'>22:27</var> UTC Investigating - Our Engineering team is investigating a recurrence of the issue impacting the DigitalOcean public API and Cloud Control Panel. This issue does not impact our data plane (i.e. running droplets). Users may experience difficulties accessing the Cloud Control Panel, along with elevated latency and intermittent errors when accessing the public API or Cloud Control Plane. We are actively investigating the issue and working to restore normal service. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience. Aug <var data-var='date'>24</var>, <var data-var='time'>19:14</var> UTC Monitoring - Our Engineering team has implemented mitigation measures to address the issue affecting the DigitalOcean public API and Cloud Control Panel. We are seeing requests succeed, and users should now be able to access the Cloud Control Panel and issue/receive API requests normally. We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. Aug <var data-var='date'>24</var>, <var data-var='time'>18:33</var> UTC Update - We are continuing to investigate the issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, we are seeing some improvement in latency/error rates and some users may now be able to access the Cloud Control Panel. Serverless Inference users may currently experience 403 and 503 errors when making API requests or accessing affected services. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience. Aug <var data-var='date'>24</var>, <var data-var='time'>17:14</var> UTC Investigating - Our Engineering team is investigating an issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, users will see elevated 5xx errors for all API requests, including things like creates for various products. Users may also be unable to access cloud.digitalocean.com. We are actively investigating the root cause and will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience.

Cloud Control Panel and API

Aug <var data-var='date'>25</var>, <var data-var='time'>06:57</var> UTC Completed - 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. We 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. If 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 Aug <var data-var='date'>24</var>, <var data-var='time'>19:16</var> UTC Scheduled - Start: 2026-08-26 05:30 UTC End: 2026-08-26 07:30 UTC During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the NYC3, SFO2, and SFO3 regions in order to improve performance and reliability. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your storage. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Spaces Maintenance in NYC3, SFO2 and SFO3

Aug <var data-var='date'>25</var>, <var data-var='time'>06:32</var> UTC Completed - 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. We 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. If 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 Aug <var data-var='date'>25</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>23</var>, <var data-var='time'>18:05</var> UTC Scheduled - Start: 2026-08-25 05:30 UTC End: 2026-08-25 07:30 UTC During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the AMS3, BLR1, FRA1 and TOR1 regions in order to improve performance and reliability. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Spaces Maintenance in AMS3, BLR1, FRA1 and TOR1

Aug <var data-var='date'>24</var>, <var data-var='time'>12:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>24</var>, <var data-var='time'>10:41</var> UTC Update - Started: 2026-08-24 05:30 UTC End time: 2026-08-24 12:00 UTC (extended from 11:00 UTC) The scheduled maintenance being performed by our Storage Engineering team on the Spaces service is progressing as planned. The maintenance in the SGP1 region has been completed successfully. Work and post-upgrade validation are still in progress in the LON1 and SYD1 regions, and approximately one additional hour is required to complete the remaining work. We are therefore extending the maintenance window from 11:00 UTC to 12:00 UTC. Expected Impact: The maintenance remains low-impact. Customers may continue to experience brief network interruptions or momentary delays when accessing Spaces in the affected regions while the remaining work is completed. Service will resume normal operation automatically once the maintenance concludes, and no action is required. We will provide another update once the maintenance is fully completed. Aug <var data-var='date'>24</var>, <var data-var='time'>08:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>24</var>, <var data-var='time'>08:27</var> UTC Scheduled - Started: 2026-08-24 05:30 UTC End time: 2026-08-24 11:00 UTC (extended from 07:30 UTC) The maintenance our Storage Engineering team is performing on the Spaces service in the LON1, SGP1 and SYD1 regions is currently in progress and we are extending the window to complete the planned work and post-upgrade validation. The window will now run until 11:00 UTC instead of 07:30 UTC. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. This may continue until the maintenance concludes at 11:00 UTC. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket.

Maintenance Window Extended in LON1, SGP1, SYD1.

Aug <var data-var='date'>24</var>, <var data-var='time'>07:30</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>24</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>22</var>, <var data-var='time'>05:43</var> UTC Scheduled - Start: 2026-08-24 05:30 UTC End: 2026-08-24 07:30 UTC During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the LON1, SGP1 and SYD1 regions in order to improve performance and reliability. Expected Impact: This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your Spaces. Service will resume normal operation automatically, and no action is required on your part. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Spaces Maintenance in LON1, SGP1 and SYD1

Aug <var data-var='date'>23</var>, <var data-var='time'>14:33</var> UTC Resolved - Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally. Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/ Aug <var data-var='date'>23</var>, <var data-var='time'>11:30</var> UTC Monitoring - Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters.   We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. Aug <var data-var='date'>23</var>, <var data-var='time'>07:06</var> UTC Update - We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions. During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API. Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available. Aug <var data-var='date'>23</var>, <var data-var='time'>05:11</var> UTC Investigating - Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests. We apologize for the inconvenience and will share an update once we have more information.

Managed Databases Creation

Aug <var data-var='date'>21</var>, <var data-var='time'>14:52</var> UTC Resolved - Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience. Aug <var data-var='date'>21</var>, <var data-var='time'>13:06</var> UTC Monitoring - Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied. Spaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal. We are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored. Aug <var data-var='date'>21</var>, <var data-var='time'>12:59</var> UTC Investigating - Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions. During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…" Our Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.

Container Registry and Spaces Accessibility

Aug <var data-var='date'>19</var>, <var data-var='time'>19:34</var> UTC Resolved - Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally. GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates. Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account. Aug <var data-var='date'>19</var>, <var data-var='time'>18:59</var> UTC Monitoring - At this time, the regional control plane is fully healthy. CPU Droplets, Managed databases, Load balancers, Block storage and Spaces are operating normally. Droplet create, resize and other management operations are working. Kubernetes (DOKS) control planes are reachable. Our teams are continuing to work with the facility to restore all equipment. GPU Droplets in MKC1 remain offline or unreachable. DOKS GPU worker nodes may remain NotReady, and GPU-backed inference endpoints in this region may be unavailable. We will monitor the regional control plane for a short time and then resolve this incident. GPU customers will receive personalized updates with more information in lieu of this status page. If you have questions about your affected resources, contact support and reference this incident. Aug <var data-var='date'>19</var>, <var data-var='time'>15:28</var> UTC Update - Our Engineering team continues to work on the issue affecting the MKC1 region. We are actively working to restore connectivity and bring the impacted nodes back online. We will provide another update as soon as we have more information. Aug <var data-var='date'>19</var>, <var data-var='time'>12:22</var> UTC Identified - We have identified the root cause of the issue in the MKC1 region affecting multiple racks and nodes. Our Engineering team is actively implementing remediation steps to restore connectivity and bring the impacted nodes back online. During this time, customers may continue to experience disruptions to GPU workloads and Serverless Inference. Kubernetes (DOKS) worker nodes may also remain in a NotReady state, and customers may be unable to reach Kubernetes API endpoints or perform cluster-management operations in affected clusters. We will provide another update as soon as we have more information. Aug <var data-var='date'>19</var>, <var data-var='time'>11:10</var> UTC Investigating - Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes. During this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state. Our team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.

Major Service Interruption in MKC1

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

Volume Attach/Detach events in FRA1

Aug <var data-var='date'> 9</var>, <var data-var='time'>01:01</var> UTC Resolved - Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation. We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account. Aug <var data-var='date'> 9</var>, <var data-var='time'>00:31</var> UTC Monitoring - Our Engineering team has implemented a fix for the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions, and is currently monitoring the situation. At this time, customers should no longer experience errors with: New account registration Droplet creation Reserved IP allocation Automated Backups and Snapshots operations Droplet Autoscale scaling operations DOKS cluster operations GenAI services Access to the Droplet console Database cluster creation We will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved. Aug <var data-var='date'> 8</var>, <var data-var='time'>22:02</var> UTC Update - Our Engineering team continues to work on implementing and rolling out a fix for the issue affecting multiple services across multiple regions, including new account registration, Droplets, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet console, and Database cluster creation. Customers may continue to experience the previously reported service disruptions while remediation efforts remain in progress. We will provide another update as soon as more information becomes available. Aug <var data-var='date'> 8</var>, <var data-var='time'>20:02</var> UTC Identified - Our Engineering team has identified the root cause of the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions. Customers may experience the following: Unable to create new accounts Unable to create Droplets Unable to allocate Reserved IPs Failures with Automated Backups and Snapshots operations Droplet Autoscale scaling operations not working as expected DOKS cluster operations failing GenAI services impacted Unable to access the Droplet console Database clusters stuck in a "Creating" state Our Engineering team is working on implementing a fix and we will provide another update as soon as more information becomes available. Aug <var data-var='date'> 8</var>, <var data-var='time'>19:38</var> UTC Update - Our Engineering team is continuing to investigate reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions. During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected. Further investigation has found that GenAI services are also affected due to this issue, customers may also be unable to access the Droplet console, and Database clusters may be stuck in a "Creating" state. Our Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available. Aug <var data-var='date'> 8</var>, <var data-var='time'>18:57</var> UTC Investigating - Our Engineering team is currently investigating reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions. During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected. Our Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.

Account Registration, Droplets, and Related Services

Aug <var data-var='date'> 6</var>, <var data-var='time'>21:05</var> UTC Resolved - Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. Aug <var data-var='date'> 6</var>, <var data-var='time'>20:02</var> UTC Monitoring - Our Engineering team has implemented a fix for the issue affecting Functions on App Platform. Functions builds/deploys and requests to Functions endpoints should now be completing successfully. We are currently monitoring the situation to ensure the service has returned to normal operation and remains stable. We apologize for the inconvenience and will provide a further update once the incident is confirmed resolved. Aug <var data-var='date'> 6</var>, <var data-var='time'>19:01</var> UTC Investigating - Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform. We apologize for the inconvenience and will share an update once we have more information.

Functions on App Platform

Aug <var data-var='date'> 6</var>, <var data-var='time'>16:33</var> UTC Resolved - Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing. Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications. The services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing. We 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.

Multiple Services Availability

Aug <var data-var='date'> 4</var>, <var data-var='time'>21:42</var> UTC Resolved - As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets. Our team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused. Aug <var data-var='date'> 4</var>, <var data-var='time'>20:44</var> UTC Monitoring - Our Engineering team has implemented a fix for the issue affecting Spaces Cold Storage billing and is currently monitoring the situation. Customers with cold storage buckets should no longer see incorrect values reflected in their daily usage and current invoices. We will post an update as soon as the issue is fully resolved. Aug <var data-var='date'> 4</var>, <var data-var='time'>18:52</var> UTC Identified - Our Engineering team has identified the issue affecting Spaces Cold Storage billing. The team is actively working on a fix to resolve the issue. We apologize for the inconvenience and will provide another update as soon as more information becomes available. Aug <var data-var='date'> 4</var>, <var data-var='time'>16:13</var> UTC Investigating - Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.

Spaces Cold Storage Billing

Aug <var data-var='date'> 3</var>, <var data-var='time'>17:59</var> UTC Resolved - 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. Aug <var data-var='date'> 3</var>, <var data-var='time'>16:39</var> UTC Monitoring - We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved Aug <var data-var='date'> 3</var>, <var data-var='time'>13:58</var> UTC Investigating - Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating. We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Cloud Control Panel Access

Jul <var data-var='date'>30</var>, <var data-var='time'>06:15</var> UTC Resolved - 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. Jul <var data-var='date'>29</var>, <var data-var='time'>21:41</var> UTC Update - Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3. At this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service. We apologize for the inconvenience and will share an update once we have more information. Jul <var data-var='date'>29</var>, <var data-var='time'>17:56</var> UTC Investigating - We are currently investigating this issue.

Response Degradation Impacting Kimi-K3

Jul <var data-var='date'>28</var>, <var data-var='time'>15:24</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>27</var>, <var data-var='time'>19:44</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'>27</var>, <var data-var='time'>18:31</var> UTC Investigating - We are currently investigating this issue.

Agent Platform Requests Returning HTTP 500 Errors

Jul <var data-var='date'>24</var>, <var data-var='time'>12:42</var> UTC Resolved - Between 07:46  UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further. Jul <var data-var='date'>24</var>, <var data-var='time'>11:45</var> UTC Monitoring - We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. Jul <var data-var='date'>24</var>, <var data-var='time'>10:36</var> UTC Identified - We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

Is Digital Ocean down?

Digital Ocean status is UP

Lastest published events

VPC Networking Availability

A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)

Support Portal Service Disruption

Digital Ocean Services, Components and Regions

Recent Digital Ocean events

VPC Networking Availability

A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)

Support Portal Service Disruption

Power Degradation impacting GPU Performance in ATL1

Rescheduled: Spaces Maintenance in BLR1

Rescheduled: Spaces Maintenance in NYC3, SFO2 and SFO3