DigitalOcean incident: Control Panel Errors - Unable to Enable 2FA and Google/GitHub

Affected components

• Cloud Control Panel

1. resolvedMay 9, 2026, 14:42 UTC

   Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled. Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally. We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.

2. monitoringMay 9, 2026, 13:51 UTC

   Our Engineering team has implemented necessary changes to address the issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. Our team is currently monitoring the situation to ensure stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. investigatingMay 9, 2026, 11:15 UTC

   Our Engineering team is investigating an issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this time, users may encounter errors while enabling these authentication methods and could also experience issues accessing teams with secure sign-in enabled. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

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
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• MongoDB Atlas: AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMinor · May 8, 2026, 02:24 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 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