DigitalOcean incident: Cloud Firewall

Affected components

• Cloud Firewall

1. resolvedMay 20, 2026, 07:48 UTC

   Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident.

2. monitoringMay 20, 2026, 07:15 UTC

   Our Engineering team has implemented a fix to resolve the issue causing incorrect Cloud Firewall rules to display on the cloud panel. At this time, the user interface is functioning as expected, and we are actively monitoring the situation to ensure continued stability. We will provide a final update once we have verified that the issue is fully resolved.

3. investigatingMay 20, 2026, 05:35 UTC

   We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking. We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in DigitalOcean's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 UTC
• Twilio: Delay in Getting Twilio/flows Templates Approved on WhatsappMinor · May 18, 2026, 18:42 UTC
• Snyk: Supply Chain Compromise on  @antv being investigated for more than 300 packages in npm ecosystemMinor · May 19, 2026, 05:29 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Twilio: SMS Delivery Delays From Twilio to Multiple Networks in Multiple Countries in EuropeMinor · May 19, 2026, 13:21 UTC
• Snyk: Jira Integration DegradedMinor · May 19, 2026, 14:19 UTC

How often does DigitalOcean have incidents?

DigitalOcean reported 20 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 5h 35m. See DigitalOcean's uptime and incident history