DigitalOcean Services Status

All Systems Operational
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
Dec 3, 2024

No incidents reported today.

Dec 2, 2024

No incidents reported.

Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024
Resolved - Our Engineering team has confirmed the full resolution of this issue. If you continue to experience problems, please open a ticket with our support team. Thank you for being so patient, and we apologize for any inconvenience.
Nov 29, 05:35 UTC
Monitoring - Our domain registrar has taken action and the digitaloceanspaces.com domain is now recovering. We have verified the domain is resolving and are seeing error rates dropping for all impacted services. Users should begin seeing services returning to normal operation.

Our Engineering teams are monitoring the situation to ensure complete recovery and we will post a final update soon.

Nov 29, 04:24 UTC
Update - Our Engineering team has identified additional downstream services seeing elevated failure rates and broken functionality. At this time, the following services are impacted:

- Spaces object accessibility in all regions with objects hosted under digitaloceanspaces.com.

- Requests to create, push, or pull to/from Container Registries

- Backups for the Mongo Managed Databases product are not successfully uploading, so users attempting to use those backups will see errors.

- Creates and resizes for Load Balancers in all regions

- New builds for App Platform in all regions

- Create or updating Functions in all regions

We are in active contact with our vendor to resolve this as quickly as possible. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved.

We will continue to provide updates as we have new information.

Nov 29, 03:47 UTC
Update - Our Engineering team has identified additional downstream services seeing elevated failure rates and broken functionality. At this time, the following services are impacted:

- Spaces object accessibility in all regions with objects hosted under digitaloceanspaces.com.

- Requests to create, push, or pull to/from Container Registries

- Backups for the Mongo Managed Databases product are not successfully uploading, so users attempting to use those backups will see errors.

- Creates and resizes for Load Balancers in all regions

- New builds for the App Platform in all regions

We are in active contact with our vendor to resolve this as quickly as possible. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved.

We will continue to provide updates as we have new information.

Nov 29, 03:36 UTC
Update - Spaces accessibility in all regions continues to be impacted and users will experience errors when attempting to interact with objects hosted under digitaloceanspaces.com. Container Registries are also impacted and users will experience errors when attempting to create, push, or pull containers. Backups for the Mongo Managed Databases product are also not successfully uploading, so users attempting to use those backups will see errors.

We are in active contact with our vendor to resolve this as quickly as possible. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved.

We will continue to provide updates as we have new information.

Nov 29, 03:04 UTC
Update - Spaces accessibility in all regions continues to be impacted and users will experience errors when attempting to interact with objects hosted under digitaloceanspaces.com. Backups for the Mongo Managed Databases product are also not successfully uploading, so users attempting to use those backups will see errors.

We have engaged with our upstream vendor to resolve this incident as quickly as possible and are awaiting a further update. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved.

We understand these are critical issues for our customers and are working as quickly as possible to resolve this.

Nov 29, 02:38 UTC
Update - Our Engineering team has successfully deployed a solution to bring the Cloud Control Panel back online. Please refresh the page a few times to clear your cache.

However, we are still experiencing issues with Spaces. We are engaging with our upstream vendor to resolve this incident as quickly as possible. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved. We understand this is a critical issue for our customers and are working as quickly as possible to resolve this.

Nov 29, 01:50 UTC
Identified - Our Engineering team has identified this as a domain registrar issue for the entire digitaloceanspaces.com domain. We are engaging with our upstream vendor to resolve this incident as quickly as possible. Any DNS record under digitaloceanspaces.com will continue to fail until this incident is resolved. We understand this is a critical issue for our customers.

Our Cloud Control Panel is dependent on our Spaces product and is also experiencing an outage due to this issue.

Due to the Cloud Control Panel being down, if users need to submit a support ticket, they may do so here: https://www.digitalocean.com/company/contact/support

Nov 29, 01:31 UTC
Update - Our Engineering team is continuing to investigate this issue and all possible paths to remediation, as well as confirm if this issue is related to an upstream provider outage. We understand this is a critical issue for our customers.

Due to the Cloud Control Panel being down, if users need to submit a support ticket, they may do so here: https://www.digitalocean.com/company/contact/support

Nov 29, 01:10 UTC
Update - We are continuing to investigate this issue.
Nov 29, 00:34 UTC
Investigating - Our Engineering team is currently investigating an issue affecting portions of the Cloud Panel across all regions. Additionally, some Space Buckets may be inaccessible via the CDN. Users may experience difficulties accessing the cloud control panel, encounter DNS-related problems, or face interruptions when managing or accessing Spaces and Spaces CDN through.

We apologize for the inconvenience and will share an update once we have more information.

Nov 29, 00:21 UTC
Nov 28, 2024

No incidents reported.

Nov 27, 2024
Resolved - Our Engineering team identified and resolved the networking issue in our SFO3 region.

From 10.02 UTC to 11:44 UTC, users may have experienced connectivity issues, latency, and timeout errors while interacting with Droplet-based services and App Platform.

The impact has been mitigated and services should be working normally at this time.

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.

Nov 27, 12:03 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, latency, and timeout errors while interacting with Droplet-based services and App Platform.

We will post an update as soon as the issue is fully resolved.

Nov 27, 11:44 UTC
Identified - As of 11:03 UTC, our Engineering team has identified the cause of the networking issue in our SFO3 region and is actively working on a fix. During this time users may experience connectivity issues, latency, and timeout errors while interacting with Droplet-based services and App Platform.

We will post an update as soon as additional information is available.

Nov 27, 11:31 UTC
Investigating - As of 10.02 UTC, our Engineering team is investigating an issue related to the SFO3 network maintenance here: https://status.digitalocean.com/incidents/rk0qtczt9j1c

During this time users may experience connectivity issues, latency, and timeout errors while interacting with Droplet-based services and App Platform.

We apologize for the inconvenience and will share an update once we have more information.

Nov 27, 11:03 UTC
Completed - The scheduled maintenance has been completed.
Nov 27, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 27, 10:00 UTC
Scheduled - Start: 2024-11-27 10:00 UTC
End: 2024-11-27 14:00 UTC

During the above window, our Networking team will be performing maintenance on core switches in our SFO3 datacenter as part of network upgrades.

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. Should an unexpected issue arise, a possible outcome would be temporary loss of connectivity or increased latency for a brief period of time. 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

Nov 25, 10:11 UTC
Completed - The scheduled maintenance has been completed.
Nov 27, 03:00 UTC
Update - Our Engineering team has decided to extend the maintenance window by an hour to monitor the situation.

Maintenance is still underway and we will update once the maintenance is fully completed.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding.

Nov 27, 01:52 UTC
Update - From 22:25 - 23:15 UTC, all event-related actions including creating or deleting resources, were temporarily disabled in NYC3.

Users attempting any event-based operations across products hosted in NYC3 would have encountered error messages. While we anticipated event failures and delays, this impact period was longer than expected. We are taking steps to ensure this does not happen in future maintenances.

As of now, maintenance is still underway and we will update once the maintenance is fully completed.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding.

Nov 27, 00:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 26, 22:00 UTC
Scheduled - Start: 2024-11-26 22:00 UTC
End: 2024-11-27 02:00 UTC

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

Nov 24, 22:03 UTC
Nov 26, 2024
Nov 25, 2024
Resolved - Our Engineering team is investigating an issue related to our ongoing SFO3 maintenance here: https://status.digitalocean.com/incidents/4kj7krrpyg3k

From 20:23 - 20:25 UTC, some services were impacted by a drop in networking. During that time, some Managed Kubernetes clusters experienced errors from the Kubernetes API and/or an increase in 5xx errors. Communication between other services and Block Storage Volumes may have been impacted as well.

The impact has been mitigated and services should be working normally at this time.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Nov 25, 22:05 UTC
Completed - The scheduled maintenance has been completed.
Nov 25, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 25, 16:30 UTC
Scheduled - Start: 2024-11-25 16:30 UTC
End: 2024-11-25 22: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:

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

Nov 23, 16:35 UTC
Resolved - Given the absence of outages for the Support Portal, we will now resolve this incident. Our Engineering team will continue to work with our vendor to ensure continued stability of this service. If we observe further outages, we will communicate those to our users via new updates on our status page.

We sincerely apologize and thank you for your patience as we worked through this issue. In case of any questions or concerns, please open a ticket with our Support team.

Nov 25, 19:20 UTC
Update - Our Engineering team continues to work with our vendor to find a solution, but we have not observed any further outages of our Support Portal over the last 48 hours. We will provide additional updates as information becomes available. If an outage does occur, users may still contact us via the form here: https://www.digitalocean.com/company/contact/support

Thank you for your patience. We will post an update as soon as more information becomes available.

Nov 25, 15:56 UTC
Update - Our Engineering team continues to work with our vendor in order to resolve the issue with users accessing the Support Portal. The issue has been escalated and we are awaiting feedback.

As a reminder, if users need to reach out, they can utilize the form here as a workaround:

https://www.digitalocean.com/company/contact/support

Thank you for your patience. We will post an update as soon as further information becomes available.

Nov 22, 03:49 UTC
Investigating - Our Engineering team has observed issues with our Support Portal. During brief, recurring outages, users are unable to access the Support Portal at https://cloudsupport.digitalocean.com/. We are aware of these events and our engineers are working with our vendor to resolve this.

As this issue is intermittent, we expect users will be able to log support tickets normally. However, during any periods of unavailability, as a temporary workaround, users may still contact us via the form here: https://www.digitalocean.com/company/contact/support

Thank you for your patience. We will post an update as soon as further information becomes available.

Nov 21, 15:40 UTC
Nov 24, 2024

No incidents reported.

Nov 23, 2024

No incidents reported.

Nov 22, 2024
Resolved - From 09:05 to 09:50 UTC (November 21), our Engineering team observed an issue with Droplet creation.

During this time, users may have experienced intermittent errors while creating the Droplets via the Cloud Panel and API. 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.

Nov 22, 17:44 UTC
Nov 21, 2024
Nov 20, 2024
Resolved - Our Engineering team has confirmed that the issue with displaying users for PostgreSQL Managed Databases across all regions has been fully resolved.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Nov 20, 01:54 UTC
Monitoring - Our Engineering team has rolled out a fix to resolve the issue with displaying users for PostgreSQL Managed Databases across all regions.

Users should no longer see errors while creating new users for PostgreSQL Managed Databases using Cloud Control Panel.

We will continue to monitor this at our end and will share an update once the problem is resolved completely.

Nov 20, 01:34 UTC
Investigating - Our Engineering team is investigating an issue with displaying users for PostgreSQL Managed Databases across all regions.

During this time, users are unable to see existing users in the Cloud Control Panel. Additionally, when creating users in the Cloud Control Panel, an error will be displayed, despite the user being created successfully.

Creating and listing users for PostgreSQL clusters via the API remains functional.

We apologize for the inconvenience and will share an update once we have more information.

Nov 20, 00:50 UTC
Nov 19, 2024

No incidents reported.

' }, showLink: false, cookie: { domain: '.digitalocean.com', expiryDays: '-1' }, onStatusChange: function(status) { onCookieConsentStatusChange(status); } }); }); } })(); const incidentStates = [ 'investigating' , 'identified' , 'monitoring' , 'resolved' ]; $(function() { // Add the twitter button $('@dostatus').appendTo('.updates-dropdown-container'); if ($('.status.incident').length == 1) { $('.components-affected').insertAfter('.page-title'); } if ($('.status.status-index').length == 1) { // Make the incident titles h3s and add links below the bodies $('.incident-container').each(function() { updateTitle($(this), 'h3', 'Incident Details'); }); $('.scheduled-maintenance').each(function() { $(this). children('.incident-title'). prepend('
'); updateTitle($(this), 'h3', 'Maintenance Details'); }); // move the outage to the header $('.page-status').appendTo('#header-incidents-inner-container'); // move the incidents to the header $('.unresolved-incidents').appendTo('#header-incidents-inner-container').removeClass('unresolved-incidents'); // move the scheduled maintenance to the header $('.scheduled-maintenances-container').appendTo('#header-incidents-inner-container'); // set the border-radius on second group $('.component-container').attr('style','border-radius:3px !important'); // add the icon div $('.unresolved-incident').each(function() { var state; $(this).children('.updates').children('.update').each(function() { state = $(this). children('strong'). text(). toLowerCase(); if (incidentStates.indexOf(state) !== -1) { return false; } }); $(this). children('.incident-title'). prepend('
'); updateTitle($(this), 'h2', 'Incident Details'); }); // rename "Past Incidents" to "Status History" $('.incidents-list .font-largest').html('Status History'); // rename "Incident History" to "Show History" $('.history-footer-link').html('Show History') // weird opacity trick i'm doing don't touch $('.layout-content').css('opacity',1); } else { $('#header-incidents-outer-container').remove(); $('.custom-header-container').addClass('bottom-padded'); } }); function updateTitle(element, type, linkText) { var titleCont = element.children('.incident-title'); var link = titleCont.children('a:not(.subscribe)'); var title = link.html(); $('<'+type+' class="title">'+title+''+type+'>').prependTo(titleCont); link.html(linkText); link.removeClass('actual-title'). removeClass('with-ellipsis'). addClass('incident-details'); link.appendTo(element); } $(function() { $('.component-container').toggleClass('closed') }); // Regional services layout $('
').prependTo('.components-section') $('

Regional Services Status

').appendTo('.regional') $('.components-container').appendTo('.regional') // Global services layout $('
').prependTo('.components-section') $('

Global Services Status

').appendTo('.global') $('.components-container').clone().appendTo('.global') // build layout table for global services with three rows var global_containers = $('.global > .components-container').find('.component-container'); global_containers.each(function(){ if($(this).find('.status-red').length || $(this).find('.status-yellow').length || $(this).find('.status-orange').length || $(this).find('.status-blue').length){ $(this).prependTo('.global > .components-container'); } if($(this).find('.child-components-container').length){ $(this).remove(); } }); $(function() { $('.components-container').toggleClass('one-column').toggleClass('three-columns') }); // build layout table for regional services var regional_containers = $('.regional > .components-container').find('.component-container'); regional_containers.each(function(){ if($(this).find('.status-red').length || $(this).find('.status-yellow').length || $(this).find('.status-orange').length || $(this).find('.status-blue').length){ $(this).find('.child-components-container > .component-inner-container').each(function(){ if(!$(this).hasClass('status-green')) { this.style.setProperty('background-color', 'rgba(243, 245, 249, 0.97)','important'); this.style.setProperty('margin-bottom', '0','important'); } }); $(this).prependTo('.regional > .components-container'); } if($(this).find('.child-components-container').length == 0){ $(this).remove(); } }) // remove uptime $(function() { $('.components-section > .components-uptime-link').remove(); }); // tooltips for status images in incident header $(function() { $('.icon-indicator.investigating').attr('title','Investigating'); $('.icon-indicator.identified').attr('title','Issue Identified'); $('.icon-indicator.monitoring').attr('title','Monitoring'); $('.icon-indicator.maintenance').attr('title','Maintenance'); }); // add aria-labels $(function() { $('.fa-check').attr('aria-label','Operational'); $('.fa-minus-square').attr('aria-label','Degraded Performance'); $('.fa-exclamation-triangle').attr('aria-label','Partial Outage'); $('.fa-times').attr('aria-label','Major Outage'); $('.fa-wrench').attr('aria-label','Maintenance'); $('.component-statuses-legend').attr('aria-label','Statuses Legend'); $('.container > .logo > img').attr('alt','DigitalOcean logo'); }); // spacer to visually separate main page legend $(function() { $('
').prependTo('.container > .components-section > .component-statuses-legend'); }); // add legend to history page $(function() { if ($('[data-react-class=HistoryIndex]').length) { $('
Impact levels• Critical • Major • Minor • Maintenance • Retroactive
').insertAfter('.pagination'); } }); // Filter button UX improvements function resetSelection() { $("input:checkbox").each(function() { if(this.checked == true) { this.click(); } }); } $(function() { if ($('[data-react-class=HistoryIndex]').length) { window.addEventListener('click', function(e) { if($(event.target).closest('.grouped-items-selector').length === 0 && $(event.target).closest('.component-selector').length === 0 && $(event.target).closest('.cc-window').length === 0 ){ if ($('.grouped-items-selector').length) { $('.component-selector > span').click(); e.stopImmediatePropagation(); } } else { if ($('.grouped-items-selector').length && !$('#reset-selection').length) { $('
  - Clear selection
').prependTo('.grouped-items-selector'); $('#reset-selection').click(resetSelection); e.stopImmediatePropagation(); } } }); } }); $(function() { $('* Note: Incidents before May 10th, 2023 were backfilled and don\'t support the filter feature.').prependTo('.months-container'); }); $(function() { if (/Android|iPhone/i.test(navigator.userAgent)) { $( '.component-container' ).each(function () { this.style.setProperty( 'width', '95%', 'important' ); }); } }); // Shorten header incident describtions function revealTruncated (incidentID) { let truncateDivName = "#truncate_" + incidentID; let expandLinkDivName = "#expand_" + incidentID; let truncateLink = " [less] " $(truncateDivName).css('display','inline'); $(expandLinkDivName).insertAfter(truncateDivName) $(expandLinkDivName).html(truncateLink); } function hideTruncated (incidentID) { let truncateDivName = "#truncate_" + incidentID; let expandLinkDivName = "#expand_" + incidentID; let truncateLink = " [...] " $(truncateDivName).css('display','None'); $(expandLinkDivName).insertBefore(truncateDivName) $(expandLinkDivName).html(truncateLink); } $('.update > span.whitespace-pre-wrap').each(function() { let textLength = $(this).text().split(/\s+/).length; if (textLength > 81){ // get incident ID let incidentUrl = $(this).closest('.unresolved-incident').find('a')[0]; let incidentID = (String(incidentUrl)).split("incidents/")[1]; let firstPart = $(this).html().split(/\s+/).slice(0,80).join(' '); let secondPart = ''; let expandLink = "
 [...] 
" $(this).html(firstPart + expandLink + secondPart); } });