Supabase incident
Inadvertently disabled pg_graphql for some projects
Update timeline
- resolved Apr 29, 2026, 05:52 PM UTC
A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to disable pg_graphql for projects that had not seen usage in the last 30 days. Due to a misconfiguration, this targeted more projects than intended. We are deeply sorry for the inconvenience and have since addressed the issue. For those using pg_graphql actively, you may have seen pg_graphql extension is not enabled in the logs for your project and you can safely re-enable this. If you have been impacted, or you are unable to re-enable pg_graphql, please contact [email protected]
Looking to track Supabase downtime and outages?
Pingoru polls Supabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Supabase reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Supabase alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required