Who is down right now

20 down now · 248 this week

Supabase · Data and observabilityApr 26, 2026, 17:52 UTC 6 months ago

Inadvertently disabled pg_graphql for some projects

InformationalConfig changeUpdated 46d ago
Apr 26, 17:52 UTCApr 26, 17:52 UTC
Duration
0m
Impact
Informational
Root cause
Config change
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Status page

Final update

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

Timeline

  1. Resolved · Apr 26, 17:52 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 success@supabase.io

More from Supabase

Full history

Also caused by configuration change

All