Provider
SupabaseIncident detail
Inadvertently disabled pg_graphql for some projects
Resolved incidentMinor
Timeline window
to
Outage alerts
Get alerted the next time Supabase breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.
Resolved
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 success@supabase.io
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.