Live  /  Supabase  /  Incident

Supabase: Elevated Error rates for All Supabase project APIs

Supabase · supabase.comMinor incidentResolved2026-11-12 23:31 UTC
Public — what happened

Summary

Supabase said that starting at 22:13 UTC on November 12, 2026, it saw slightly higher error rates on requests to its Data APIs, Auth, Storage and other web API routes in all regions. By 22:52 UTC the company said it had traced the errors to a single project sending an unusually large number of requests, and that there was no widespread problem as first suspected. Supabase said all API routes were back to normal and it kept watching to make sure things stayed stable. The incident was marked resolved at 23:31 UTC.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 →

More from Supabase

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

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