Visit our support site.
All Systems Operational
Regions
Operational
Global
Operational
AMS2
Operational
AMS3
Operational
BLR1
Operational
FRA1
Operational
LON1
Operational
NYC1
Operational
NYC2
Operational
NYC3
Operational
SFO1
Operational
SFO2
Operational
SFO3
Operational
SGP1
Operational
TOR1
Operational
SYD1
Operational
Services
Operational
API
Operational
App Platform
Operational
Billing
Operational
Block Storage
Operational
Cloud Control Panel
Operational
Cloud Firewall
Operational
Community
Operational
Container Registry
Operational
DNS
Operational
Droplets
Operational
Event Processing
Operational
Floating IP
Operational
Kubernetes
Operational
Load Balancers
Operational
Managed Databases
Operational
Monitoring
Operational
Networking
Operational
Spaces
Operational
Support Center
Operational
Spaces CDN
Operational
VPC
Operational
WWW
Operational
Functions
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 28, 2023
No incidents reported today.
Jan 27, 2023
Resolved -
As of 23:40 UTC, We've confirmed the issue impacting the API and Cloud Control Panel is fully resolved. Thank you for your patience. If you continue to experience any problems, please open a support ticket from within your account.
Jan 27, 00:10 UTC
Jan 27, 00:10 UTC
Monitoring -
Our Engineering team has identified the cause of the issue with our Cloud Control Panel and API. As of 22:58 UTC, users should no longer be experiencing errors with loading Cloud or issuing API requests. We are monitoring the situation to ensure there is no recurrence.
We will post another update once we confirm the issue is fully resolved.
Jan 26, 23:36 UTC
We will post another update once we confirm the issue is fully resolved.
Jan 26, 23:36 UTC
Investigating -
Our Engineering team is investigating an issue with our Cloud Control Panel and API. Beginning at approximately 22:40 UTC, users may be experiencing intermittent issues with loading the Cloud Control Panel and issuing API requests.
We will share an update as soon as we have more information.
Jan 26, 23:00 UTC
We will share an update as soon as we have more information.
Jan 26, 23:00 UTC
Jan 26, 2023
Jan 25, 2023
No incidents reported.
Jan 24, 2023
Resolved -
As of 14:10 UTC, our Engineering team has confirmed full resolution of the issue that impacted the reachability of App Platform URLs. All services 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.
Jan 24, 15:06 UTC
Jan 24, 15:06 UTC
Monitoring -
Our Engineering team has observed normal resolution of new App Platform URLs and are monitoring the situation closely. We will post an update as soon as the issue is fully resolved.
Jan 24, 14:21 UTC
Jan 24, 14:21 UTC
Update -
As of 10:30UTC, our Engineering team is currently investigating an issue with App Platform URLs not resolving correctly for any newly deployed Apps. Existing Apps should not face any issues.
At this time, users may experience inaccessibility with App Platform URLs. Unfortunately, adding custom domains currently for the impacted Apps is also affected and cannot be used as a workaround.
We apologize for the inconvenience and will share an update once we have more information.
Jan 24, 10:34 UTC
At this time, users may experience inaccessibility with App Platform URLs. Unfortunately, adding custom domains currently for the impacted Apps is also affected and cannot be used as a workaround.
We apologize for the inconvenience and will share an update once we have more information.
Jan 24, 10:34 UTC
Investigating -
As of 08:17 UTC, our Engineering team is investigating an issue with App Platform URLs not resolving correctly for any newly deployed Apps. Existing Apps should not face any issues.
At this time, users may experience inaccessibility with App Platform URLs. We apologize for the inconvenience and will share an update once we have more information.
Jan 24, 08:56 UTC
At this time, users may experience inaccessibility with App Platform URLs. We apologize for the inconvenience and will share an update once we have more information.
Jan 24, 08:56 UTC
Jan 23, 2023
No incidents reported.
Jan 22, 2023
Resolved -
As of 10:00 UTC, our Engineering team has confirmed the full resolution of the issue that impacted network reachability in the SGP1 region. All services and resources should now be fully reachable.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
Jan 22, 10:08 UTC
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
Jan 22, 10:08 UTC
Monitoring -
Our Engineering team has been able to mitigate the issue with networking in our SGP1 region. Users in the region should no longer experience packet loss/latency, timeouts, and related issues with Droplet-based services in SGP1, including Droplets, Managed Kubernetes, and Managed Database.
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 22, 09:22 UTC
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 22, 09:22 UTC
Identified -
Our Engineering team has identified that our Network providers are experiencing packet loss/ latency on their end and we have implemented workarounds for this issue. Users in the region may experience packet loss/latency, timeouts, and related issues with Droplet-based services in SGP1, including Droplets, Managed Kubernetes, and Managed Database.
We will post an update as soon as additional information is available.
Jan 22, 06:40 UTC
We will post an update as soon as additional information is available.
Jan 22, 06:40 UTC
Investigating -
As of 04.30 UTC, our Engineering team is investigating reports of networking connectivity issues in our SGP1 region. Users from the North American region may have experienced packet loss/latency, timeouts, and related issues with Droplet-based services in SGP1, including Droplets, Managed Kubernetes, and Managed Database. We will share an update once we have further information.
Jan 22, 05:28 UTC
Jan 22, 05:28 UTC
Jan 21, 2023
Resolved -
Our Engineering team has confirmed that the issue impacting payments made on the DigitalOcean platform has been fully resolved. Between 08:00 UTC and 15:34 UTC customer accounts may have been temporarily suspended even after successful payment of their monthly bill was remitted.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 21, 17:00 UTC
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 21, 17:00 UTC
Monitoring -
Our Engineering team has put a fix in place for the issue impacting payments made on the DigitalOcean platform. At this time users should no longer experience any issues with Accounts being suspended after successful payment remittance. We will continue to monitor the situation and provide a final update once we confirm the issue has been fully resolved. Thank you for your patience and we apologize for the inconvenience.
Jan 21, 15:49 UTC
Jan 21, 15:49 UTC
Identified -
Our Engineering team has identified the cause of the issue with payments made on the DigitalOcean platform and is actively working on a fix. During this time, users may experience issues with Accounts being suspended even after successful payment. We will post an update as soon as additional information is available
Jan 21, 12:53 UTC
Jan 21, 12:53 UTC
Investigating -
Our Engineering team is investigating an issue with payments made on the DigitalOcean platform. As of 08:00 UTC, users may experience issues with Accounts being suspended even after successful payment. We apologize for the inconvenience and will share an update once we have more information.
Jan 21, 12:21 UTC
Jan 21, 12:21 UTC
Resolved -
As of 02:45 UTC, our Engineering team has confirmed the full resolution of the issue that impacted network reachability and event processing in the LON1 and SFO3 regions. All services and resources should now be fully reachable and operational.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 21, 03:08 UTC
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 21, 03:08 UTC
Monitoring -
After further investigation, our Engineering teams have confirmed there was a concurrent event in SFO3 which caused impact to our internal network. This resulted in multiple monitoring systems alerting, as well as impacted users trying to perform events in SFO3, such as Droplet creates, power on/off, etc.
Confirmed impact:
01:35 - 01:50 UTC: Network connectivity loss in LON1 to Droplets and Droplet-based services like Managed Databases, Load Balancers, and Kubernetes Clusters, as well as unavailability to App Platform Apps and Functions. Users were also unable to perform events in LON1 during this time.
01:32 - 01:40 UTC: Users unable to perform events in SFO3 during this time.
All services are now operating normally and we will update the title of this incident to accurately reflect this outage.
We appreciate your patience and will post an update once we are confident the issue is fully resolved.
Jan 21, 02:29 UTC
Confirmed impact:
01:35 - 01:50 UTC: Network connectivity loss in LON1 to Droplets and Droplet-based services like Managed Databases, Load Balancers, and Kubernetes Clusters, as well as unavailability to App Platform Apps and Functions. Users were also unable to perform events in LON1 during this time.
01:32 - 01:40 UTC: Users unable to perform events in SFO3 during this time.
All services are now operating normally and we will update the title of this incident to accurately reflect this outage.
We appreciate your patience and will post an update once we are confident the issue is fully resolved.
Jan 21, 02:29 UTC
Update -
Our Network Engineering team has confirmed an unexpected issue occurred in our LON1 region, which led to a loss of network connectivity in LON1 from 01:35 - 01:56 UTC. Network traffic began to recover at 01:56 UTC to all services in LON1.
We are continuing to investigate impact in other regions and will post an update soon.
Jan 21, 02:03 UTC
We are continuing to investigate impact in other regions and will post an update soon.
Jan 21, 02:03 UTC
Investigating -
At approximately 01:36 UTC, we received multiple alerts for services in multiple regions. So far, we've confirmed issues in LON1, NYC1, NYC3, SFO2, SFO3, AMS3, and FRA1. We are working to determine impact and are seeing some services self-recovering.
Users may have experienced and may still be experiencing issues with network connectivity to Droplets and Droplet-based services, event failures like Droplet creates and power on/off, Functions unavailability, and other issues with DigitalOcean services.
As soon as we have further information to share, we'll post an update here.
Jan 21, 01:54 UTC
Users may have experienced and may still be experiencing issues with network connectivity to Droplets and Droplet-based services, event failures like Droplet creates and power on/off, Functions unavailability, and other issues with DigitalOcean services.
As soon as we have further information to share, we'll post an update here.
Jan 21, 01:54 UTC
Jan 20, 2023
Resolved -
As of 06:51 UTC, our Engineering team has resolved the issue with Spaces in our AMS3 region. The Spaces system should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 20, 07:38 UTC
Jan 20, 07:38 UTC
Monitoring -
Our engineering team has implemented a fix to resolve the issue with Spaces in our AMS3 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Jan 20, 06:59 UTC
Jan 20, 06:59 UTC
Identified -
Our Engineering team has identified the cause of the issue with Spaces in our AMS3 region and is actively working on a fix. During this time, users may experience issues with accessing Spaces and see request errors. We will post an update as soon as additional information is available.
Jan 20, 06:39 UTC
Jan 20, 06:39 UTC
Investigating -
Our Engineering team is investigating an issue with Spaces in our AMS3 region. As of 20:44 UTC, users may experience issues with accessing Spaces and see request errors. We apologize for the inconvenience and will share an update once we have more information.
Jan 19, 22:18 UTC
Jan 19, 22:18 UTC
Jan 19, 2023
Completed -
The scheduled maintenance has been completed.
Jan 19, 23:00 UTC
Jan 19, 23:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 19, 19:00 UTC
Jan 19, 19:00 UTC
Scheduled -
Start: 2023-01-19 19:00 UTC
End: 2023-01-19 23:00 UTC
During the above window, we will be performing maintenance on Droplets in our SGP1 data center as part of network upgrades.
Expected Impact:
These upgrades are designed and tested to be seamless and we do not expect any impact on customer traffic due to this maintenance. Should an unexpected issue arise, a possible outcome would be disruption to internet connectivity for the Droplets during the maintenance period.
If you have any questions related to this issue please send us a ticket from within your Cloud Control Panel. https://cloudsupport.digitalocean.com/s/createticket
Jan 19, 18:11 UTC
End: 2023-01-19 23:00 UTC
During the above window, we will be performing maintenance on Droplets in our SGP1 data center as part of network upgrades.
Expected Impact:
These upgrades are designed and tested to be seamless and we do not expect any impact on customer traffic due to this maintenance. Should an unexpected issue arise, a possible outcome would be disruption to internet connectivity for the Droplets during the maintenance period.
If you have any questions related to this issue please send us a ticket from within your Cloud Control Panel. https://cloudsupport.digitalocean.com/s/createticket
Jan 19, 18:11 UTC
Jan 18, 2023
Resolved -
As of 13:53 UTC, our Engineering team has confirmed the full resolution of the issue that impacted Kubernetes Clusters in our AMS3 region. All resources should now be fully reachable.
If you continue to experience problems, please open a ticket with our Support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 18, 14:10 UTC
If you continue to experience problems, please open a ticket with our Support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 18, 14:10 UTC
Monitoring -
Our Engineering team has successfully mitigated the issue and the remaining clusters have been remediated.
At this time, all Kubernetes Clusters which were affected in AMS3 are operational. Users should be able to access their Kubernetes Clusters without any problem.
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 18, 13:11 UTC
At this time, all Kubernetes Clusters which were affected in AMS3 are operational. Users should be able to access their Kubernetes Clusters without any problem.
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 18, 13:11 UTC
Update -
As of 10:00 UTC January 18, our Engineering team has made progress toward internal recovery, although it might take some time for the Clusters to be fully operational and accessible. Some Kubernetes Clusters in AMS3 remain impacted and may be inaccessible. Our Engineering team is continuing to work to mitigate the issue as soon as possible.
We will post another update as soon as we have new developments.
Jan 18, 10:28 UTC
We will post another update as soon as we have new developments.
Jan 18, 10:28 UTC
Update -
As of 09:00 UTC January 18, our Engineering team has made progress toward internal recovery, although it might take some time for the Clusters to be fully operational and accessible.
At this point, 7% out of the total 21% of Kubernetes Clusters have been remediated and approximately 14% of Kubernetes Clusters in AMS3 remain impacted and may be inaccessible. Our Engineering team is continuing to work to mitigate the issue as soon as possible.
We will post another update by 10:00 UTC.
Jan 18, 09:09 UTC
At this point, 7% out of the total 21% of Kubernetes Clusters have been remediated and approximately 14% of Kubernetes Clusters in AMS3 remain impacted and may be inaccessible. Our Engineering team is continuing to work to mitigate the issue as soon as possible.
We will post another update by 10:00 UTC.
Jan 18, 09:09 UTC
Update -
Our Engineering team has continued work to mitigate this issue and additional clusters have been remediated.
The total percentage of Kubernetes Clusters impacted by this incident was determined to be approximately 21%.
From 11:41 - 18:00 UTC January 17, approximately 7% out of the total 21% of Kubernetes Clusters in AMS3 experienced issues and were remediated.
At this point, approximately 14% of Kubernetes Clusters in AMS3 remain impacted and may be inaccessible.
We will post another update by 09:00 UTC.
Jan 18, 03:02 UTC
The total percentage of Kubernetes Clusters impacted by this incident was determined to be approximately 21%.
From 11:41 - 18:00 UTC January 17, approximately 7% out of the total 21% of Kubernetes Clusters in AMS3 experienced issues and were remediated.
At this point, approximately 14% of Kubernetes Clusters in AMS3 remain impacted and may be inaccessible.
We will post another update by 09:00 UTC.
Jan 18, 03:02 UTC
Update -
Our Engineering team is continuing to troubleshoot this issue with the main priority of getting Kubernetes clusters available for users. A fix has now been pushed for a subset of clusters. Unfortunately, there are still some clusters that remain impacted at this time and users could still be facing issues with loading the dashboard as well as cluster accessibility.
We will provide further updates as investigation and mitigation efforts continue. Thank you for your patience.
Jan 17, 22:53 UTC
We will provide further updates as investigation and mitigation efforts continue. Thank you for your patience.
Jan 17, 22:53 UTC
Investigating -
Our Engineering team is investigating an issue with Kubernetes clusters in the AMS3 region. During this time, a subset of users may experience errors while communicating with their clusters in the AMS3 region. Specifically, as of 00:18 UTC, users may be unable to load the Kubernetes Dashboard in the Cloud Control Panel, see errors when accessing via kubectl, and/or see unauthorized errors when attempting to establish connectivity.
We apologize for the inconvenience and will share an update once we have more information.
Jan 17, 18:28 UTC
We apologize for the inconvenience and will share an update once we have more information.
Jan 17, 18:28 UTC
Jan 17, 2023
Jan 16, 2023
No incidents reported.
Jan 15, 2023
Resolved -
As of 06:00 UTC, our Engineering team has confirmed the full resolution of the issue that impacted network reachability in the TOR1 region. All services and resources should now be fully reachable.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 15, 06:50 UTC
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 15, 06:50 UTC
Monitoring -
Our Engineering team has mitigated an issue that impacted network connectivity to the TOR1 region. Between 2:16 - 2:48 UTC, users may have noticed network connectivity issues with Droplets and Droplet-based services, in the region.
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 15, 02:59 UTC
We are monitoring the situation and will post an update once we confirm the issue is fully resolved.
Jan 15, 02:59 UTC
Investigating -
Our Engineering team is investigating an issue with network connectivity in our TOR1 region, beginning at 02:16 UTC. At this time, users may see high amounts of packet loss, network timeouts, or increased latency to Droplets and Droplet-based services.
Jan 15, 02:36 UTC
Jan 15, 02:36 UTC
Jan 14, 2023
Resolved -
Our Engineering team has confirmed that the issue impacting network connectivity in the SGP1 region has been fully resolved. Customers may have encountered packet loss, network timeouts, or increased latency between 18:34 UTC - 18:49 UTC.
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 14, 20:49 UTC
If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.
Jan 14, 20:49 UTC
Monitoring -
Our Engineering team has identified the root cause of the network connectivity issues in SGP1 and applied a fix. We will continue to monitor for stability and provide a final update once we confirm that the situation is fully resolved.
Thank you for your patience and we apologize for the inconvenience.
Jan 14, 19:54 UTC
Thank you for your patience and we apologize for the inconvenience.
Jan 14, 19:54 UTC
Update -
Our Engineering team has determined that this issue is isolated to the SGP1 region and has not impacted any customers in the BLR1 region. Our metrics indicate that the connection issues subsided at 18:49 UTC, however we are continuing to investigate the root cause and will provide an update as soon as more information is available.
Jan 14, 19:23 UTC
Jan 14, 19:23 UTC
Investigating -
Our Engineering team is investigating an issue with network connectivity in our SGP1 and BLR1 region, beginning 18:41 UTC. At this time, users may see high amounts of packet loss, network timeouts, or increased latency to Droplets and Droplet-based services.
We'll post an update as soon as we have further information.
Jan 14, 18:52 UTC
We'll post an update as soon as we have further information.
Jan 14, 18:52 UTC