Major impactResolvedDatabases

Supabase outage: Projects failing to load Supautils in multiple regions

Supabase reported this major-impact incident on its official status page on Aug 28, 2026, 16:18 UTC. It was resolved after under a minute.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Aug 28, 2026, 16:18 UTC
started
Aug 28, 2026, 16:18 UTC
resolved
under a minute
duration
Major
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedAug 28, 2026, 16:18 UTC

    PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 58 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 2h 1m. See Supabase's uptime and incident history

← Previous: Increased response times for requests (Aug 27, 2026)Next: Project Creation Failures (Aug 31, 2026) →