Supabase outage: Project Resize Problems in US-West-2

Affected components

• us-west-2

1. resolvedJul 27, 2026, 20:47 UTC

   Project resizing has maintained expected performance in us-west-2.

2. monitoringJul 27, 2026, 19:01 UTC

   We have a mitigation in place for resizing issues for projects in us-west-2. We will be monitoring going forward. If your project is in us-west-2, and you experience issues resizing going forward, please open a support ticket so we can directly assist you.

3. identifiedJul 27, 2026, 18:11 UTC

   We have identified the cause of the resize issues and are evaluating options for mitigating the problem.

4. investigatingJul 27, 2026, 17:53 UTC

   We are continuing to investigate this issue.

5. investigatingJul 27, 2026, 17:42 UTC

   We have noticed an issue with project resizing in us-west-2 and are investigating.

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.

• Sentry: Error and profile ingestion issues in USCritical · Jul 27, 2026, 16:23 UTC
• dbt Cloud: Certificate errors affecting the dbt platformCritical · Jul 27, 2026, 18:25 UTC
• OVHcloud: [GRA11][Network] - Load Balancer incident notificationMajor · Jul 27, 2026, 12:52 UTC
• Discord: session starts, DM message delivery downMajor · Jul 27, 2026, 17:48 UTC
• DigitalOcean: Agent Platform Requests Returning HTTP 500 ErrorsMajor · Jul 27, 2026, 18:31 UTC
• Datadog: Synthetics Test Results DelayedMajor · Jul 27, 2026, 19:05 UTC
• RevenueCat: Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"Minor · Jul 27, 2026, 10:14 UTC
• Render: Degraded dashboard performanceMinor · Jul 27, 2026, 14:43 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