Minor impactResolvedDatabases

Supabase incident: Elevated errors on Postgres change subscriptions

Supabase reported this minor-impact incident on its official status page on Jun 24, 2026, 23:52 UTC. It was resolved after 2h 24m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jun 24, 2026, 23:52 UTC
started
Jun 25, 2026, 02:16 UTC
resolved
2h 24m
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedJun 25, 2026, 02:16 UTC

    We have confirmed that the fix has been successfully applied and the issue affecting Postgres Change subscriptions has been resolved. We will continue to monitor the service, but all systems are operating normally at this time.

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 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

← Previous: Degraded performance of the Shared Pooler cluster in ap-southeast-1 (Jun 24, 2026)Next: Upgrade Failures (Jun 25, 2026) →
Supabase incident on Jun 24, 2026: Elevated errors on Postgres change subscriptions · APIStatus.watch