Supabase Status · History · Incident #6782
RESOLVEDProjects failing to load Supautils in multiple regions
Major · Started Aug 28, 2026 · 4:18 PM
Supabase Status · History · Incident #6782
RESOLVEDMajor · Started Aug 28, 2026 · 4:18 PM
Duration
< 1m
Severity
Major
Detection lead
—
User reports
—
Summary
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.
Started
Aug 28, 2026 · 4:18 PM
Resolved
Aug 28, 2026 · 4:18 PM
Duration
< 1m
Severity
Major
Event timeline
Resolved
Aug 28 · 4:18 PM SupabasePostgreSQL 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.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.