Supabase – Realtime Postgres Changes degraded

Dec 3, 17:04 UTC
Resolved – This incident has been resolved.

Dec 3, 14:15 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Dec 3, 14:15 UTC
Identified – We have determined Postgres Changes was using an incorrect number of connections to check RLS policies.
This caused the system to reuse the same replication slot, leading to failed connections against Postgres Changes.

The issue has been identified and we’re deploying corrective measures.

Dec 3, 14:03 UTC
Investigating – We are currently investigating this issue.