
DigitalOcean Status
Real-time updates of DigitalOcean issues and outages
DigitalOcean status is Operational
DigitalOcean API
DigitalOcean Cloud Control Panel
New York
AMS3
AMS3
Active Incidents
No active incidents
Recently Resolved Incidents
As of 17:45 UTC, our Engineering team is investigating reports of static site deployment failures in the NYC3 region on App Platform. Users may experience errors when attempting to deploy new static sites, resulting in failed deployments.
The existing static sites are still accessible and functioning normally.
Our team is actively working on identifying the root cause and implementing the fix.
We apologize for the inconvenience and will share an update once we have more information.
As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services.
At this point, the issue appears to be intermittent, and not all requests are being affected.
We apologize for the inconvenience and will share an update once we have more information.
From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
DigitalOcean Outage Survival Guide
DigitalOcean Components
DigitalOcean API
As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services.
At this point, the issue appears to be intermittent, and not all requests are being affected.
We apologize for the inconvenience and will share an update once we have more information.
DigitalOcean Billing
DigitalOcean BYOIP
DigitalOcean Cloud Control Panel
As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services.
At this point, the issue appears to be intermittent, and not all requests are being affected.
We apologize for the inconvenience and will share an update once we have more information.
DigitalOcean Cloud Firewall
DigitalOcean Community
DigitalOcean DNS
DigitalOcean Support Center
DigitalOcean Reserved IP
DigitalOcean WWW
DigitalOcean GenAI Platform
DigitalOcean App Platform
Global
Amsterdam
Atlanta
Bangalore
Frankfurt
London
New York
As of 17:45 UTC, our Engineering team is investigating reports of static site deployment failures in the NYC3 region on App Platform. Users may experience errors when attempting to deploy new static sites, resulting in failed deployments.
The existing static sites are still accessible and functioning normally.
Our team is actively working on identifying the root cause and implementing the fix.
We apologize for the inconvenience and will share an update once we have more information.
San Francisco
Singapore
Sydney
Toronto
DigitalOcean Container Registry
Global
AMS3
From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
BLR1
FRA1
NYC3
SFO2
SFO3
SGP1
SYD1
DigitalOcean Droplets
Global
AMS2
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SFO1
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Event Processing
Global
AMS2
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SFO1
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Functions
Global
AMS3
BLR1
FRA1
LON1
NYC1
SFO3
SGP1
SYD1
TOR1
DigitalOcean GPU Droplets
Global
ATL1
NYC2
TOR1
DigitalOcean Managed Databases
Global
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Monitoring
Global
AMS2
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SGP1
SFO1
SFO2
SFO3
SYD1
TOR1
DigitalOcean Networking
Global
AMS2
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SFO1
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Network File Storage
ATL1
DigitalOcean Kubernetes
Global
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC3
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Load Balancers
Global
AMS2
AMS3
ATL1
BLR1
FRA1
LON1
NYC1
NYC2
NYC3
SFO1
SFO2
SFO3
SGP1
SYD1
TOR1
DigitalOcean Spaces
Global
AMS3
From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.