WhatBrokeToday
Today's Trends
mediumResolvedSupabase

Supabase: Intermittent 502/503 errors for pg_net calls to Edge Functions

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(current)

Executive summary

Supabase experienced intermittent 502 and 503 errors for pg_net calls to Edge Functions in the ap-southeast-1 region. The incident has since been resolved and services are operating normally.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Intermittent 502/503 errors for pg_net calls to Edge Functions(opens official status page in a new tab)

    Status: Resolved The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally. Affected components ap-southeast-1 (Operational)

    by supabase status

Timeline

  1. First report on status page

    Intermittent 502/503 errors for pg_net calls to Edge Functions

    Source
  2. Official statement

    Status: Resolved The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

    Source
  3. Status changed

    Status changed: new → resolved (official status page reports resolution).