Supabase incident

Elevated errors on Postgres change subscriptions

Minor Resolved View vendor source →

Supabase experienced a minor incident on June 24, 2026 affecting Realtime, lasting 2h 23m. The incident has been resolved; the full update timeline is below.

Started
Jun 24, 2026, 11:52 PM UTC
Resolved
Jun 25, 2026, 02:16 AM UTC
Duration
2h 23m
Detected by Pingoru
Jun 24, 2026, 11:52 PM UTC

Affected components

Realtime

Update timeline

  1. investigating Jun 24, 2026, 11:52 PM UTC

    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 Jun 24, 2026, 11:58 PM UTC

    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 Jun 25, 2026, 12:49 AM UTC

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

  4. resolved Jun 25, 2026, 02:16 AM 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.