Resolved -
From 6:00 UTC to 17:45 UTC, users have experienced issues with Droplet creation and Droplet-based services in the NYC3 region.
Our Engineering team has fully resolved the issue impacting Droplet creation in the NYC3 region. Users can now create Droplets and Droplet-based services, including Managed Kubernetes, Managed Databases, Load Balancers, and snapshots, without any issues.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 25, 20:16 UTC
Monitoring -
Our Engineering team has implemented a fix to resolve the issue impacting the creation of Droplets in the NYC3 region. Users should now be able to create Droplets and Droplet-based services including Managed Kubernetes, Managed Databases, Load Balancers, and snapshots without any issues.
We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.
Feb 25, 18:43 UTC
Identified -
Our Engineering team has identified the reason behind the failed and delayed Droplet creates in the NYC3 region and implemented a partial mitigation to address this issue. As of now, customers may be able to create Droplets and Droplet-based services including Managed Kubernetes, Managed Databases, Load Balancers, and snapshots, however, there might be still some delay in the creates.
We apologize for the inconvenience and appreciate your patience as we work to resolve this issue. Further updates will be shared as they become available.
Feb 25, 16:02 UTC
Investigating -
Our Engineering team is investigating an issue with Droplet creation in the NYC3 region. During this time, users may see an elevated failure rate for the creation of Droplets and other Droplet-based products, such as Load Balancers, Managed Databases, or Kubernetes in the NYC3 region.
We apologize for the inconvenience and will share an update once we have more information.
Feb 25, 12:45 UTC
Resolved -
From 17:14 UTC to 17:34 UTC, users experienced issues accessing the Cloud Control Panel and API.
Our Engineering team has resolved the issue, and the Cloud Control Panel, API, and events should now be functioning normally.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 25, 18:28 UTC
Monitoring -
Our Engineering team has implemented a fix to resolve the issue impacting the Cloud Control Panel and API. Users should no longer experience issues with accessing the Cloud Control Panel and API.
We will continue to monitor the situation and post an update once this issue is fully resolved. Thank you for your patience.
Feb 25, 17:58 UTC
Identified -
Our Engineering team has identified the cause of the issue impacting our Cloud Control Panel and API and is actively working on implementing a fix. We are already seeing signs of recovery, and users should now have access to the Cloud Control Panel and API.
We will post an update as soon as additional information is available.
Feb 25, 17:44 UTC
Update -
We are continuing to investigate this issue.
Feb 25, 17:32 UTC
Investigating -
Our Engineering team is investigating an issue impacting our Cloud Control Panel and API.
During this time, users will experience errors when trying to use the public API at api.digitalocean.com or while accessing our Cloud Control Panel at https://cloud.digitalocean.com. Users may also see issues with processing Droplet and Kubernetes cluster creations along with Droplet-based events.
We are now confirming the full impact. We regret any inconvenience and will let you know as soon as more information is available.
Feb 25, 17:27 UTC
Resolved -
From February 6 21:28:35 UTC to February 19 23:14:00 UTC, users may have experienced issues receiving monitoring alerts for tagged resources.
Our Engineering team has resolved the issue, alerts for tagged resources are now working properly and users should now start receiving new alerts going forward.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 20, 00:20 UTC
Monitoring -
Our engineering team has implemented a fix for the issues that affect receiving monitoring alerts for tagged resources, and are currently monitoring the situation. Any alerts that should've been received beginning February 6th to today will not be received, but new alerts for tagged resources should work going forward.
We appreciate your patience, we will post an update once we've confirmed the issue is fully resolved.
Feb 19, 23:46 UTC
Investigating -
Our Engineering team is investigating reports that alerts are not received when alerts are configured with tags. Users may not receive email notification of alerts when using tags, although resources specified by name are still monitored and receiving alerts properly.
We apologize for the inconvenience and will share an update once we have more information.
Feb 19, 20:36 UTC
Feb 19, 2025
Feb 18, 2025
No incidents reported.
Feb 17, 2025
No incidents reported.
Feb 16, 2025
No incidents reported.
Feb 15, 2025
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
$('