DigitalOcean Services Status

Latest AWS SDK/CLI updates incompatible with Spaces
Identified - DigitalOcean Spaces Customers using the latest versions (released on Jan 15, 2025) of the AWS CLI or any AWS SDK, or relying on a tool or application that depends on any of these versions of the AWS CLI or an AWS SDK, are experiencing failed uploads to Spaces buckets in all regions.

This is caused by a change made by AWS on January 15, 2024 to the AWS CLI and almost all AWS SDKs (including boto3) to require use of “Data Integrity Protections for Amazon S3” (https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html).

The currently recommended solution is to downgrade (roll back) to a version of the AWS CLI or AWS SDK released prior to January 15, 2025, or to an earlier version of tools or applications that do not depend on one of these versions of the AWS CLI or AWS SDK. The list of known impacted AWS client tools are:
AWS CLI v2.23.0 (workaround - move to last known good version: v2.22.35)
AWS SDK for Python (boto3) v1.36.0 (workaround - move to last known good version: 1.35.99)
AWS SDK for Go 2025-01-15 release (workaround - move to last known good release: 2025-01-14)
Jan 16, 2025 - 19:14 UTC
API Operational
Billing Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
App Platform Operational
Global Operational
Amsterdam Operational
Bangalore Operational
Frankfurt Operational
London Operational
New York Operational
San Francisco Operational
Singapore Operational
Sydney Operational
Toronto Operational
Container Registry Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
Droplets 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
SYD1 Operational
TOR1 Operational
Event Processing 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
SYD1 Operational
TOR1 Operational
Functions Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
GPU Droplets Operational
Global Operational
NYC2 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Monitoring Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SGP1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SYD1 Operational
TOR1 Operational
Networking 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
SYD1 Operational
TOR1 Operational
Kubernetes Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Load Balancers 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
SYD1 Operational
TOR1 Operational
Spaces Operational
Global Operational
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
BLR1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
VPC 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
SYD1 Operational
TOR1 Operational
Volumes 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
SYD1 Operational
TOR1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 17, 2025

No incidents reported today.

Jan 16, 2025

Unresolved incident: Latest AWS SDK/CLI updates incompatible with Spaces.

Jan 15, 2025
Network Connectivity in BLR and SFO Region
Resolved - From 11:29 to 12:31 UTC, our Engineering team observed a Networking issue in our BLR and SFO regions. During this time, users may have experienced Droplet connectivity issue, Users should no longer be experiencing these issues.
We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.
Jan 15, 12:54 UTC
Jan 14, 2025

No incidents reported.

Jan 13, 2025

No incidents reported.

Jan 12, 2025
NYC3 Network Maintenance
Completed - The scheduled maintenance has been completed.
Jan 12, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 11, 21:00 UTC
Scheduled - Start: 2025-01-11 21:00 UTC
End: 2025-01-12 24:00 UTC

Hello,

During the above window, our Networking team will be making changes to core networking infrastructure, to improve performance and scalability in the NYC3 region.

Expected impact:

During the maintenance window users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services including Droplets, Managed Kubernetes, Load Balancers, Container Registry, and App Platform. We will endeavor to keep this to a minimum for the duration of the change.

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
Jan 11, 20:25 UTC
Jan 11, 2025
Reconciling Kubernetes Clusters
Resolved - As of 18:55 UTC, our Engineering team has confirmed the full resolution of the issue that impacted Managed Kubernetes Clusters in all of our regions. All of the services should now be working normally.

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 apologise for any inconvenience.
Jan 11, 21:12 UTC
Investigating - Our Engineering team is currently investigating an issue with Managed Kubernetes clusters. During this time, some users may experience delays when provisioning Kubernetes clusters, specifically version 1.31.1-5.

We apologize for the inconvenience and will provide an update as soon as we have more information.
Jan 11, 18:29 UTC
Jan 10, 2025

No incidents reported.

Jan 9, 2025
Retro - Multiple services and API
Resolved - From 15:28 to 15:32 UTC, an internal service disruption may have resulted in users experiencing errors while using the Cloud Panel or API to manage Spaces Buckets, Apps, Managed Database Clusters, or Load Balancers as well as other actions due to impacted downstream services.

If you continue to experience problems, please open a ticket with our support team.

Thank you and we apologize for any inconvenience.
Jan 9, 18:01 UTC
Jan 8, 2025

No incidents reported.

Jan 7, 2025
Network Connectivity in SFO3 Region
Postmortem - Read details
Jan 16, 04:58 UTC
Resolved - From 13:09 - 14:48 UTC, we experienced an issue with IPv6 network connectivity in our SFO3 region. Our Engineering team was able to identify the root cause, revert changes, and resolve the issue.

During that time, connectivity via IPv6 to services in SFO3 was impacted. This included, in particular, connectivity to and provisioning of Load Balancers, control plane connectivity to Kubernetes clusters, and connectivity to App Platform Apps.

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.
Jan 7, 16:43 UTC
Monitoring - Our engineering team has implemented a fix to resolve the networking issue in our SFO3 region. Users should no longer encounter connectivity issues, provisioning Load Balancers, latency, and timeout errors while interacting with resources in the SFO3 region.

We will post an update as soon as the issue is fully resolved.
Jan 7, 15:51 UTC
Update - Our Engineering team is continuing to investigate the cause of the issue with networking in our SFO3 region and is taking action to mitigate this incident by reverting recent changes. In addition to connectivity issues, users may see failures with provisioning Load Balancers in SFO3.

We are seeing some services recover, but expect to see a few more short periods of network connectivity issues as the reverts progress.

We will continue to share updates as soon as we have new information.
Jan 7, 14:47 UTC
Investigating - Our engineering team is investigating an issue related to the SFO3 network maintenance here: https://status.digitalocean.com/incidents/lf0njg8ysj0w

During this time users may experience connectivity issues, latency, and timeout errors while interacting with resources in the SFO3 data center.

We apologize for the inconvenience and will share an update once we have more information.
Jan 7, 13:35 UTC
Error adding card details
Resolved - Our engineering team has resolved the issue preventing some users from adding new credit cards from the control panel. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 7, 14:14 UTC
Monitoring - Our engineering team has implemented a fix to resolve issues that some users experienced when attempting to add new credit cards to the Cloud Control Panel.

We are monitoring the situation and will post an update as soon as the issue is fully resolved.
Jan 7, 13:38 UTC
Investigating - Our engineering team is investigating reports of issues occurring when users attempt to add a new credit card in the billing settings page of the Cloud Control Panel.

During this time, some users may be unable to input card information. We apologize for the inconvenience and will share an update once we have more information.
Jan 7, 13:24 UTC
SFO3 Network Maintenance
Completed - The scheduled maintenance has been completed.
Jan 7, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 10:00 UTC
Scheduled - Start: 2025-01-07 10:00 UTC
End: 2025-01-07 14:00 UTC

During the above window, our Networking team will be making changes to core networking infrastructure, to improve performance and scalability in the SFO3 region.

Expected impact:

These upgrades are designed and tested to be seamless and we do not expect any impact to customer traffic due to this maintenance. If an unexpected issue arises, affected Droplets and Droplet-based services may experience increased latency or a brief disruption in network traffic. We will endeavor to keep any such impact to a minimum.

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
Jan 5, 10:15 UTC
Jan 6, 2025

No incidents reported.

Jan 5, 2025

No incidents reported.

Jan 4, 2025

No incidents reported.

Jan 3, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage
DigitalOcean Home API Docs Community