Minor impactResolvedDatabases

Supabase incident: Upgrade Issues

Supabase reported this minor-impact incident on its official status page on Oct 6, 2026, 15:23 UTC. It was resolved after 2h 56m.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Oct 6, 2026, 15:23 UTC
started
Oct 6, 2026, 18:18 UTC
resolved
2h 56m
duration
Minor
impact
  1. resolvedOct 6, 2026, 18:18 UTC

    We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

  2. monitoringOct 6, 2026, 17:27 UTC

    The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.

  3. identifiedOct 6, 2026, 16:37 UTC

    A fix has been developed and we are going through the review and implementation process.

  4. identifiedOct 6, 2026, 16:03 UTC

    We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.

  5. investigatingOct 6, 2026, 15:23 UTC

    We have observed failures in attempted upgrades to 17.11.0.003. We 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.

How often does Supabase have incidents?

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