Supabase outage: Projects in stuck state in EU-CENTRAL-1 (Frankfurt)

1. resolvedJul 16, 2026, 11:35 UTC

   The mitigation work for this incident has been completed, and we have not observed any further impact following the restoration of affected projects. This incident is now resolved. If you continue to experience issues that you believe are related to this incident in eu-central-1 (Frankfurt), please open a support ticket and our team will investigate.

2. monitoringJul 16, 2026, 10:14 UTC

   All impacted projects have now been successfully restarted, and functionality has been restored. We are moving this incident to Monitoring for an additional hour while we continue to ensure stability. If you believe your project in eu-central-1 (Frankfurt) is still impacted by this issue, please open a support ticket and we'll work with you directly to investigate.

3. identifiedJul 16, 2026, 09:16 UTC

   The majority of impacted projects have now been recovered, and functionality has been restored for most customers. Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible. We will continue to provide updates as this work progresses.

4. identifiedJul 16, 2026, 07:42 UTC

   The majority of impacted projects have now been recovered, and functionality has been restored for most customers. Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible. We will continue to provide updates as this work progresses.

5. identifiedJul 16, 2026, 07:02 UTC

   We are continuing to work on a fix for this issue.

6. identifiedJul 16, 2026, 07:00 UTC

   Our infrastructure provider experienced a connectivity issue in the EU-CENTRAL-1 (Frankfurt) Region, between 4:11 PM PDT and 6:24 PM PDT, which has now been resolved. As a result of this incident, a number of Supabase projects were left in a stuck state. Our team is actively working through the list of impacted projects to restore normal functionality as quickly as possible. We will continue to provide updates as restoration work progresses.

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.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Tailscale: Admin console and pkgs.tailscale.com are unavailableCritical · Jul 16, 2026, 08:13 UTC
• Vercel: SAML Single Sign-On (SSO) errorsMajor · Jul 16, 2026, 08:39 UTC
• Plaid: Elevated dashboard.plaid.com error ratesMajor · Jul 16, 2026, 08:48 UTC
• RevenueCat: Some users unable to login via single-sign-on (SSO)Major · Jul 16, 2026, 09:13 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Confluent Cloud: Kafka cluster performance degradation for clusters in AWS region eu-central-1Minor · Jul 15, 2026, 23:33 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Vercel: Missing Build CPU Minutes Usage DataMinor · Jul 16, 2026, 06:07 UTC
• Clerk: Increased latency on our APIsMinor · Jul 16, 2026, 07:56 UTC

How often does Supabase have incidents?

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