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
SGP1 Operational
TOR1 Operational
Services Operational
API Operational
Billing Operational
Block Storage Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Droplets Operational
Event Processing Operational
Kubernetes Operational
Load Balancers Operational
Managed Databases Operational
Monitoring Operational
Networking Operational
Spaces Operational
Support Center Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 3, 2020

No incidents reported today.

Apr 2, 2020

No incidents reported.

Apr 1, 2020
Resolved - Our Engineering team has resolved the issue with possible new account registration failures. New account registrations should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Apr 1, 10:35 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue with possible new account registration failures from past few hours and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Apr 1, 09:42 UTC
Completed - The scheduled maintenance has been completed and event processing is re-enabled.
Apr 1, 02:24 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 1, 01:00 UTC
Scheduled - During the above window our Engineering team will be performing maintenance on our core systems to improve reliability and allow for future upgrades in our FRA1 region.

Expected Impact:

Event processing will briefly be disabled in FRA1 while this maintenance is performed. Event processing includes, but is not limited to events such as Droplet creates, destroys, and resizes. We will endeavor to keep this to a minimum for the duration of the change.

If you have any questions or concerns, please reach out to us by opening up a support ticket on your account.
Mar 31, 00:14 UTC
Mar 31, 2020
Resolved - Our Engineering team has resolved the issue preventing new cards from being added to Team accounts, and users should now be able to update payment methods successfully. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 31, 22:12 UTC
Monitoring - Our Engineering team has identified an issue preventing new cards from being added to Team accounts, and has implemented a fix. We are monitoring the situation, and will post an update as soon as the issue is fully resolved.
Mar 31, 21:01 UTC
Resolved - Our Engineering team has resolved the issue with resetting the root password. Root password reset should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 31, 07:02 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue with resetting the root password and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Mar 31, 06:44 UTC
Identified - Our Engineering team has identified the cause of the issue with resetting root password and is actively working on a fix. We will post an update as soon as additional information is available.
Mar 31, 06:29 UTC
Investigating - Our Engineering team is investigating an issue with resetting the root password. During this time, you may experience errors on the backend while trying to reset the password. Meanwhile as a workaround, you can try setting up the password using our API. We apologize for the inconvenience and will share an update once we have more information.
Mar 31, 06:17 UTC
Mar 30, 2020

No incidents reported.

Mar 29, 2020
Resolved - Our engineering team has resolved the issue with domains in the Cloud Control Panel. The Cloud Control Panel should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 29, 00:06 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with domains in the Cloud Control Panel and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Mar 28, 23:21 UTC
Investigating - Our engineering team is investigating an issue preventing the domains section of the Cloud Control Panel from operating normally. During this time, you may not be able to manage your domains using the Cloud Control Panel. We apologize for the inconvenience and will share an update once we have more information.
Mar 28, 23:04 UTC
Mar 28, 2020
Resolved - Our engineering team has resolved the issue impacting the Cloud Firewall, and all services should now be functioning normally. If you experience any further problems at all then please contact support. We apologize for the inconvenience, and thank you for your patience throughout this process.
Mar 28, 16:30 UTC
Monitoring - Our engineering team has implemented a fix for the issue impacting the Cloud Firewall and is monitoring the situation closely. Thank you for your patience, and we will share an update once the matter is fully resolved.
Mar 28, 15:26 UTC
Investigating - Our engineering team is currently investigating an issue impacting the Cloud Firewall product. During this time, users may experience errors when interacting with Cloud Firewall via the Cloud control panel and API. We apologize for the inconvenience, and we'll post an update once more information is available.
Mar 28, 15:12 UTC
Mar 27, 2020

No incidents reported.

Mar 26, 2020
Resolved - Our Engineering team has resolved the issue with impacting block storage Volume in BLR1 regio]. Block storage Volumes should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 26, 08:52 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue with impacting block storage Volume in BLR1 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Mar 26, 07:45 UTC
Identified - Our Engineering team has identified the cause of the issue with impacting block storage Volume in BLR1 region and is actively working on a fix. We will post an update as soon as additional information is available.
Mar 26, 07:33 UTC
Investigating - Our Engineering team is currently investigating an issue impacting block storage Volume in BLR1 region. During this time, users may experience in creates, resize and performece degration. We apologize for the inconvenience and will share an update once we have more information.
Mar 26, 07:00 UTC
Mar 25, 2020

No incidents reported.

Mar 24, 2020

No incidents reported.

Mar 23, 2020
Completed - The scheduled maintenance has been completed.
Mar 23, 20:48 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 23, 16:48 UTC
Scheduled - Our Engineering team has identified issues affecting Block Storage Volumes in our FRA1 region. During this time, our team will be performing maintenance to ensure continued stability and performance. There may be brief dips in Block Storage performance, including increased latency, as the maintenance progresses although no major impact is expected. If you do experience issues please open a Support ticket.
Mar 23, 16:47 UTC
Mar 22, 2020

No incidents reported.

Mar 21, 2020

No incidents reported.

Mar 20, 2020
Resolved - Our engineering team has resolved the issue impacting block storage Volume resizes in all regions. Volumes should now resize normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 20, 21:53 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue impacting block storage Volume resizes. While investigating and implementing this fix, our team determined this issue affected all regions, rather than just FRA1. The fix has been deployed to all regions, and we are monitoring the situation closely. A subset of Volumes which were resized during this period may have experienced some corruption, and we will be reaching out directly to any users impacted by this. Thanks again for your patience, and we'll share an update once we believe the matter to be fully resolved.
Mar 20, 18:21 UTC
Identified - Our engineering team has identified the cause of issues impacting block storage Volume resize events in the FRA1 region, and are actively working on a fix. Thank you for your patience, and we'll share an update once more information is available.
Mar 20, 16:00 UTC
Investigating - Our engineering team is currently investigating an issue impacting block storage Volume resize events in the FRA1 region. During this time, users may experience FRA1 Volumes not resizing correctly, and/or FRA1 Volumes becoming read-only after a resize has completed. We apologize for the inconvenience and will share an update once we have more information.
Mar 20, 13:54 UTC
Resolved - Our Engineering team has resolved the issue impacting Spaces CDN subdomains, and requests to these subdomains should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Mar 20, 04:01 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue impacting Spaces CDN subdomains and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Mar 20, 03:28 UTC
Identified - Our Engineering team has identified the cause of the issue impacting Spaces CDN subdomains and is actively working on a fix. The error is strictly regarding custom subdomains used for Spaces CDN. We will post an update as soon as additional information is available.
Mar 20, 02:27 UTC
Investigating - Our Engineering team is investigating an issue with Spaces CDN subdomains. During this time, user may encounter errors when making requests to their CDN subdomains. We apologize for the inconvenience and will share an update once we have more information.
Mar 20, 01:27 UTC