Isitreallydown?
// Incident Post-MortemDRN-0334AFF5

DigitalOcean outage on May 9, 2026

Minor severityResolved45 minCloud
Started · UTC
May 09, 11:15 AM
3d ago
Resolved · UTC
May 09, 12:00 PM
3d ago
Duration
45 min
End-to-end
Peak confidence
45.00
17 snapshots
// What happened

Nothing's wrong that we can see: all 7 DigitalOcean regions are currently healthy and there are no regional network anomalies detected, but Isitreallydown? does not yet have fresh synthetic probe or DNS measurements to confirm end-to-end connectivity (Telemetry confidence: medium). DigitalOcean’s official status page is reporting a major incident affecting the Gradient AI component (“GradientAI: Agent Platform Playground Interaction Errors”), and with otherwise quiet signals this looks component-specific rather than a broad platform disruption.

Cached · Tue, May 12, 2026, 12:33 PM UTC · scope: service signals

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Control Panel Errors - Unable to Enable 2FA and Google/GitHub.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 60.00 while the service was marked Operational.

// Signals by source1 sources
  • Official status

    Status.Digitalocean.Com reported an open incident — Control Panel Errors - Unable to Enable 2FA and Google/GitHub (Cloud Control Panel) · impact: minor

    11:30 AM UTC
// Aggregate evidence

Confidence scoring

45.00

The incident reached 45.00 peak confidence across 17 stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Sat, May 09, 2026, 12:00 PM UTC.

// User impact

DigitalOcean users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.