Supabase incident

Elevated errors on Postgres change subscriptions

Minor Resolved Upstream link ↗

Started

June 24, 2026 at 11:52 PM UTC

Duration

2h 23m

Resolved

June 25, 2026 at 02:16 AM UTC

Updates timeline

  1. Investigating

    We are investigating an issue causing elevated errors for some customers using Postgres change subscriptions. Our team has identified the affected component and is actively working to determine the root cause and implement a fix. We will provide another update as soon as more information is available.

  2. Identified

    We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information or progress to share.

  3. Monitoring

    We have applied a fix and are monitoring the results to ensure the issue is fully resolved.

  4. Resolved

    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.

Live Supabase status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader