Skip to content
OutageDeck

Incident detail

403 errors for PostgREST requests

Resolved incidentMajor

Timeline window

to

Get alerted the next time Supabase breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Supabase alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating 403 errors for PostgREST requests across multiple regions.

  2. Identified

    The issue has been identified and we are working on a fix.

  3. Identified

    We are continuing to work on a fix for this issue.

  4. Identified

    We are continuing to work on a fix. We’ll share further updates as progress is made.

  5. Monitoring

    The exceptions fix has been rolled out, and we are monitoring for continued stability.

  6. Resolved

    This is now resolved. Thank you for your patience while we worked to resolve this issue.

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.

← Older incident

Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

Newer incident →

Supavisor connectivity in eu-central-1

All Supabase incidentsSupabase live status