Update - Our engineering team continues to investigate reports of errors occurring when some users attempt to access the cloud control panel. Users may be unable to login and access their account at this time. We appreciate your patience while we work to resolve this issue.
Apr 17, 13:32 UTC

Update - Our engineering team continues to investigate increased errors with Spaces in our AMS3 region. While this issue is being investigated users may be unable to connect to or use Spaces in this region. We appreciate your patience as we work to resolve this issue and apologize for the inconvenience.
Apr 16, 14:01 UTC

Update - Our engineering team continues to investigate increased errors with Spaces in our AMS3 region. During this time, users may be unable to connect to and use Spaces in this region. We appreciate your patience and will post an update as soon as additional information is available.
Apr 16, 12:50 UTC

Update - Our engineering team continues to work on issue with High CPU Droplet creates. We appreciate your patience and will post an update as soon as additional information is available.
Apr 15, 05:54 UTC

Update - Our engineering team is currently monitoring the issue causing some users to experience delays or timeout errors loading Spaces in the Cloud Control Panel. Some UI functionality, including the object count in each Space and the size of the Space in total, may intermittently fail to load while we continue to mitigate the issue. Please note S3 API functionality has not been affected. Our recent efforts should improve performance for users while we work towards a full resolution. We appreciate your patience and apologize for any inconvenience this has caused.
Apr 13, 12:21 UTC

Update - Our engineering team is continuing to investigate the issue causing delays or timeout errors loading Spaces in the Cloud Control Panel for some users. In order to improve performance for users while we work to identify the root cause and fully resolve the issue, we will disable some UI functionality, including the object count in each Space and the size of the Space in total. We apologize for any inconvenience and will continue to post updates as more information becomes available.
Apr 12, 19:04 UTC

Update - Our engineering team is continuing to investigate the issue causing delays or timeout errors loading Spaces in the Cloud Control Panel for some users. The issue has been narrowed down to slowness at a subset of endpoints in the NYC3 region; if users have Spaces in NYC3 and other regions, they may be impacted. We will provide updates as we work to confirm the root cause and to resolve the issue.
Apr 12, 16:24 UTC

Update - Our engineering team is continuing to work on the issue causing delays or timeout errors for users loading Spaces in the Cloud Control Panel. We will share an additional update as we have new information.
Apr 12, 13:21 UTC

Update - Our engineering team continues to investigate the issue related to viewing Spaces in the control panel in our NYC3 region. We appreciate your patience and will post an update as soon as additional information is available.
Apr 12, 10:29 UTC

Update - We have completed the scheduled hypervisor reboots in AMS2. We are continuing to work on rebooting the remaining hypervisors in NYC2.
Apr 12, 17:34 UTC

Update - We have completed the scheduled hypervisor reboots in AMS2. We are continuing to work on rebooting the remaining hypervisors in NYC2.
Apr 11, 19:42 UTC

Update - Our engineering team continues to investigate the issue with Snapshot and Backup failures across all regions. We appreciate your patience and will post an update as soon as additional information is available.
Apr 11, 09:05 UTC

Update - We have completed the scheduled hypervisor reboots in AMS2. We are continuing to work on rebooting the remaining hypervisors in NYC2.
Apr 10, 19:34 UTC

Update - Our engineering team continues to investigate the issue with intermittent slowness and errors on the Control Panel. During this time, it appears that some users with active Spaces may experience delays, or receive an error message, when logging into the Dashboard. We apologize for the inconvenience, and appreciate your patience as we work to resolve this issue.
Apr 9, 21:07 UTC

Update - Our engineering team continues to investigate the issue with intermittent slowness and errors on the Control Panel. During this time, some users may experience delays, or receive an error message when logging into the Dashboard. We apologize for the inconvenience and appreciate your patience as we work to resolve this issue.
Apr 9, 19:30 UTC

Update - Our engineering team continues to investigate the issue with intermittent slowness and errors on the Control Panel. We appreciate your patience and will post an update as soon as additional information is available.
Apr 9, 18:13 UTC

Update - Our Engineering and Trust & Safety teams took action to block TCP/8083 and stop outgoing traffic from affected Droplets. These mitigation efforts appear to have resolved the networking issues impacting our NYC1 datacenter, and we are monitoring the situation until it is fully resolved. We continue to work to resolve the issues impacting SFO2, and will post an update as soon as possible.
Apr 8, 20:26 UTC

Update - Our Engineering and Trust & Safety teams continue to work to resolve the incident impacting networking connectivity in our NYC1 and SFO2 regions. Our initial actions, including blocking TCP/8083 and stopping outgoing traffic from affected Droplets, appear to be helping to mitigate the issue, but the incident remains on-going.

We have identified users with potentially impacted Droplets and we are sending an email to these users detailing the actions we've taken to protect your Droplets from further exploitation, as well as steps you can take to ensure your Droplets are as secure as possible. For more details about the vulnerability, please refer to this Q&A: https://do.co/vesta-vuln
Apr 8, 20:00 UTC

Update - Our Engineering and Trust & Safety teams continue to work to resolve the incident impacting networking connectivity in our NYC regions. Our initial actions, including blocking TCP/8083 and stopping outgoing traffic from affected Droplets, appear to be helping to mitigate the issue, but the incident remains on-going.

We have identified users with impacted Droplets and will be sending emails detailing the actions we've taken to protect your Droplets from further exploitation, as well as steps you can take to ensure your Droplets are as secure as possible. Additionally, we will soon post a Q&A providing additional information and guidance for users, and will provide a link to that information once it has been posted.
Apr 8, 18:51 UTC

Update - Our Engineering and Trust & Safety teams continue to work to resolve the incident impacting networking connectivity in our NYC regions. Our initial actions, including blocking TCP/8083 and stopping outgoing traffic from affected Droplets, appear to be helping to mitigate the issue. We will provide additional updates as soon as more information is available.
Apr 8, 16:24 UTC

Update - Our engineering team continues to work to resolve the networking issue impacting our NYC regions. We believe a previously undisclosed vulnerability in software by some customers on their Droplets is allowing for denial of service (DoS) attacks against targets outside of DigitalOcean. Our Trust & Safety team is also engaged to resolve this incident; in an effort to protect unaffected Droplets, we will block inbound traffic to TCP/8083.

We will continue to post updates here as more information becomes available, and we will provide additional guidance for customers to determine whether their Droplets are impacted, and how to work around the block to continue to safely access their software.
Apr 8, 15:22 UTC

Update - Our engineering team continues to work on resolving the networking issue impacting our NYC regions. We apologize for any inconvenience and will post additional information here as it becomes available.
Apr 8, 13:37 UTC

Update - Our engineering team continues to investigate the issue with network that is currently impacting NYC regions. We appreciate your patience and will post an update as soon as additional information is available.
Apr 8, 10:45 UTC