Supabase outage: Network connectivity in us-east-1-az4

1. resolvedMay 9, 2026, 04:49 UTC

   Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase'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.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Upstash: QStash US Region Service DisruptionCritical · May 8, 2026, 09:46 UTC
• Convex: Intermittent Impact from AWS OutageMajor · May 8, 2026, 00:16 UTC
• Cursor: Investigating Service DegradationMajor · May 8, 2026, 00:43 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Anthropic: Elevated errors across Claude ModelsMajor · May 8, 2026, 09:49 UTC
• GitBook: Degraded database performanceMajor · May 8, 2026, 15:52 UTC
• Shippo: Intermittent UPS rate quote and label failuresMajor · May 8, 2026, 16:46 UTC
• Elasticsearch: Issues with Email AlertsMajor · May 8, 2026, 18:10 UTC

How often does Supabase have incidents?

Supabase reported 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history