Supabase: Edge Function Latency

Supabase · supabase.comImpact: minorResolved2026-09-16 09:38 UTC

Public — what happened

Summary

Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors.

Timeline

Started — 2026-09-16 09:24 UTC
Last update — 2026-09-16 09:38 UTC
Resolved — 2026-09-16 12:31 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see

Customers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Supabase report →

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.