Supabase incident

Inadvertently disabled pg_graphql for some projects

Notice Resolved View vendor source →

Supabase experienced a notice incident on April 26, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 26, 2026, 05:52 PM UTC
Resolved
Apr 26, 2026, 05:52 PM UTC
Duration
—
Detected by Pingoru
Apr 26, 2026, 05:52 PM UTC

Update timeline

  1. 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]