https://status.digitalocean.com/

[nt165cuvSg]


DigitalOcean Services Status

 
      x
Get email notifications whenever DigitalOcean creates, updates or
resolves an incident.
Email address: [                    ] [Subscribe via Email]
This site is protected by reCAPTCHA and the Google Privacy Policy and
Terms of Service apply.
Get text message notifications whenever DigitalOcean creates or
resolves an incident.
Country code:
[United States (+1)                    ]
Phone number: [                    ]
Change number Enter OTP: [                    ]

Resend OTP in: 30 seconds

Didn't receive the OTP? Resend OTP

[Subscribe via Text Message]
Message and data rates may apply. By subscribing you agree to the
Atlassian Terms of Service, and the Atlassian Privacy Policy. This
site is protected by reCAPTCHA and the Google Privacy Policy and
Terms of Service apply.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and
acknowledge Atlassian's Privacy Policy.
Follow @DOStatus or  view our profile.
Visit our support site.
Get the Atom Feed or RSS Feed.
Global Networking Subscribe
Monitoring - Our Engineering team has observed recovery of all
services. Some events for Droplets and Droplet-based services are
being processed, so users may still see lingering events until all
those events have been processed.

We are now monitoring the situation and will post a final update once
we confirm this incident is resolved.
Jan 10, 2024 - 22:39 UTC
Update - Our Engineering team has mitigated the issue with TOR1 event
processing and events are now flowing normally once again. Users
should be able to create, destroy, perform power actions, resize, etc
for Droplets and Droplet-based services.
Jan 10, 2024 - 22:21 UTC
Update - Our Engineering team has identified a lingering issue with
event processing in our TOR1 region. Users may see latency or
failures for events for Droplets and Droplet-based services in TOR1,
including create, power cycle, power off/on, resizes, etc.

We're working to return event processing to normal rates and will
share an update soon.
Jan 10, 2024 - 22:12 UTC
Update - Our Engineering team has taken action to improve the
situation and we are seeing recovery across all services. Event
processing, including actions like power cycle, power off/on, resize,
etc, was stalled, but has recovered and users should start seeing
those events process normally. Droplet and Droplet-based services
networking should also be returning to normal latency/error rates.

We are ensuring all services have recovered and will post an update
shortly.
Jan 10, 2024 - 21:48 UTC
Update - Our Engineering team continues to work on mitigation efforts
and is seeing a return of stability in some regions, including NYC
and SFO.

Services in SYD1 and TOR1 continue to be heavily impacted, as well as
increased error rates for our Cloud Control Panel/API,
www.digitalocean.com, DigitalOcean Community site, and latency/errors
in applying Cloud Firewall policies for Droplets and Droplet-based
services.
Jan 10, 2024 - 21:29 UTC
Identified - Our Engineering team has identified the root cause of a
global issue with networking and are working to mitigate the
situation. During this time, users may see a variety of timeouts or
errors, including, but not limited to, accessing our Cloud Control
Panel/API, Droplet and Droplet-based services network latency/
timeouts, App Platform deployment errors, and DNS resolution
timeouts.

We apologize for the disruption and will continue to provide updates
as they are available.
Jan 10, 2024 - 21:14 UTC
Investigating - Our Engineering team is currently investigating
multiple reports of issues, including increased error rates with our
Cloud Control Panel/API, Droplet networking, App Platform app
deployments/apps loading, and possible other impacts.

We are working to clarify impact and root cause and will post an
update as soon as possible.
Jan 10, 2024 - 20:59 UTC
x

Subscribe to Incident

Subscribe to updates for Global Networking via email and/or text
message. You'll receive email notifications when incidents are
updated, and text message notifications whenever DigitalOcean creates
or resolves an incident.

VIA EMAIL:
[                    ]
VIA SMS:
[United States (+1)                    ]
Enter mobile number
[                    ] Edit number Send OTP
Enter the OTP sent
[                    ] Resend OTP  in 30 seconds
To receive SMS updates, please verify your number. To proceed with
just email click 'Subscribe'
Subscribe to Incident 
Message and data rates may apply. By subscribing you agree to the
Atlassian Terms of Service, and the Atlassian Privacy Policy. This
site is protected by reCAPTCHA and the Google Privacy Policy and
Terms of Service apply.
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
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
Droplets 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
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Managed Databases 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
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
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
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
BLR1 Operational
Spaces CDN 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
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 10, 2024

Unresolved incident: Global Networking.

Jan 9, 2024
Managed Database Operations
Resolved - As of 12:30 UTC, our Engineering team has resolved the
issue impacting CRUD (create, read, update, delete) operations for
Managed Database Clusters in all the regions.

Everything should now be functioning normally. We appreciate your
patience throughout the process.

If you continue to experience problems, please open a ticket with our
support team.
Jan 9, 12:55 UTC
Monitoring - Our Engineering team has confirmed that the action taken
to mitigate the recurrence of the issue is successful. Users should
no longer experience errors in CRUD (create, read, update, delete)
operations for Managed Database Clusters in all regions, via both the
Cloud Control Panel and API requests.

We are actively monitoring the situation to ensure stability and will
provide an update once the incident has been fully resolved.
Jan 9, 10:17 UTC
Identified - Our Engineering team has observed recurrences of the
issue with CRUD (create, read, update, delete) operations for Managed
Database Clusters in all regions and is actively working on a fix.

During this time, users may experience errors in those operations,
via both the Cloud Control Panel and API requests. Mongo clusters
remain unaffected, and customers can continue to connect to their
existing databases.

We apologize for the inconvenience and will share an update once we
have more information.
Jan 9, 09:23 UTC
Monitoring - Our Engineering team has identified the root cause of
the issue with CRUD (create, read, update, delete) operations for
Managed Database Clusters in all regions, and is seeing error rates
drop. We are monitoring the situation and will post an update once we
confirm this incident is fully resolved. Mongo clusters remain
unaffected, and customers can continue to connect to their existing
databases
Jan 9, 02:04 UTC
Investigating - As of 00:15, our Engineering team is seeing an
increased error rate on CRUD (create, read, update, delete)
operations for Managed Database Clusters in all regions, excluding
Mongo clusters. During this time, users may experience errors in
those operations, via both the Cloud Control Panel and API requests.
Also, connectivity for existing clusters is fine.
We apologize for the inconvenience and will share an update once we
have more information.
Jan 9, 01:35 UTC
Jan 8, 2024
Container Registry and App Platform in Multiple Regions
Resolved - As of 15:00 UTC, Our engineering team has resolved the
issue impacting Container Registry and App platform builds in various
regions including AMS3, LON1 and FRA1 regions.

Everything should now be functioning normally. We appreciate your
patience throughout the process and if you continue to experience
problems, please open a ticket with our support team for further
review.
Jan 8, 15:57 UTC
Monitoring - Our Engineering team has implemented a fix to resolve
the issue impacting Container Registry App platform builds in AMS3,
LON1 and FRA1 regions. User should not be facing any issues while
interacting with their Container registries and also while building
their Apps.

We are actively monitoring the situation to ensure stability and will
provide an update once the incident has been fully resolved.

Thank you for your patience and we apologize for the inconvenience.
Jan 8, 15:13 UTC
Investigating - Our Engineering team is investigating an issue with
DigitalOcean Container Registry service in our AMS3 and LON1 regions.

During this time a subset of customers may experience latency while
interacting with the Container Registries. This is also impacting App
Platform builds and users may encounter delays in while building
their Apps and could potentially experience timeout errors in builds
as a result.

We apologize for the inconvenience and will share an update once we
have more information.
Jan 8, 14:15 UTC
Kubernetes Clusters - Authentication Errors
Resolved - Our Engineering team has confirmed the full resolution of
the issue with authentication failures on Managed Kubernetes
Clusters.

From 19:26 - 23:29 UTC, users saw errors accessing and performing
actions on Managed Kubernetes Clusters, due to authentication
failures. All services are now operating normally.

If you continue to experience problems, please open a ticket with our
support team. Thank you for your patience throughout this incident!
Jan 8, 00:32 UTC
Monitoring - Our Engineering team has confirmed that the action taken
to mitigate the impact of this incident is successful and customers
are no longer seeing issues accessing or performing actions on
Managed Kubernetes Clusters.

We'll monitor the situation for a short while and will post a final
update once we confirm full resolution.
Jan 8, 00:01 UTC
Identified - Our Engineering team has taken action to mitigate the
impact of this incident and internal tests on impacted clusters are
now passing. At this time, users should start to see recovery and be
able to access clusters normally.

We are still investigating root cause and ensuring this mitigation
will continue to be successful. We'll provide another update as soon
as possible.
Jan 7, 23:32 UTC
Investigating - Our Engineering team is investigating customer
reports of errors when trying to perform actions on Managed
Kubernetes Clusters using kubectl. At this time, customers may see
errors indicating that the API token is unauthorized or missing
credentials. We will provide an update as soon as we have more
information.
Jan 7, 22:02 UTC
Jan 7, 2024
Jan 6, 2024

No incidents reported.

Jan 5, 2024

No incidents reported.

Jan 4, 2024
Settings in Cloud Control Panel Unavailable
Resolved - From approximately 15:00 - 15:35 UTC, users saw a 404
error when navigating to the Settings page in our Cloud Control
Panel.

Our Engineering team has confirmed full resolution of the issue.

If you continue to experience issues, please open a Support ticket
from within your account.
Jan 4, 15:59 UTC
Monitoring - Our Engineering team has identified the root cause of
the issue with the Settings portion of our Cloud Control Panel
throwing a 404 and has implemented a fix. At this time, users should
be able to navigate to the Settings tab or directly to https://
cloud.digitalocean.com/account/team normally.

We are monitoring the fix and will post a final update once we
confirm full resolution.
Jan 4, 15:39 UTC
Investigating - Our Engineering team is investigating an issue with
the Settings portion of our Cloud Control Panel. At this time, users
navigating to the Settings tab or directly to https://
cloud.digitalocean.com/account/team will see a 404 error.

We apologize for the inconvenience and will share an update once we
have more information.
Jan 4, 15:24 UTC
Jan 3, 2024

No incidents reported.

Jan 2, 2024

No incidents reported.

Jan 1, 2024

No incidents reported.

Dec 31, 2023

No incidents reported.

Dec 30, 2023
Spaces Availability in SGP1
Resolved - Our Engineering team has resolved the issue impacting
Spaces Object Storage in our SGP1 region. From approximately 09:20
UTC - 11:31 UTC, users may have experienced an increased error rate
and low performance while using the Spaces system. Spaces should now
be operating normally.

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.
Dec 30, 12:23 UTC
Monitoring - From 09:20 UTC, our Engineering team observed an issue
with Spaces Object Storage availability in the SGP1 region.

During this time you may have experienced an increased error rate and
low performance while using the Spaces system. 

The impact has now subsided and users should no longer be
experiencing issues with accessing the Spaces Object Storage.

We apologize for the inconvenience and will share an update once we
have more information.
Dec 30, 11:53 UTC
Dec 29, 2023

No incidents reported.

Dec 28, 2023

No incidents reported.

Dec 27, 2023

No incidents reported.

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