SUPABASE

🔴 SUPABASE - Upgrade Shared Pooler V1 to V2 for eu-west-1 region. (Auto-resolved: no updates in 24h)

⏰ May 18, 2026 Fixed (for now) spotted via status_rss

// The official story

Upgrade Shared Pooler V1 to V2 for eu-west-1 region

// Status page says

THIS IS A SCHEDULED EVENT May 27 , 13:00 - 15:00 UTC May 18 , 02:52 UTC Scheduled - There will be a scheduled maintenance on 2026-05-27 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable durin

🔗 Official status page (for the PR-approved version)

https://status.supabase.com/incidents/3t293hpd545z

Supabase's Greatest Hits

🟢 SUPABASE 1d ago

🟡 Supabase's logging service decided to ghost its own data. Logs are either fashionably late or taking an indefinite sabbatical. The irony of your observability tool becoming unobservable is not lost on anyone. (Auto-resolved: no updates in 24h)

🟢 SUPABASE Sep 16, 2026

🔴 Supabase's auth service decided selective amnesia was a personality trait. Some projects can't log in because apparently credentials are just vibes now. Engineers are frantically searching the couch cushions for the fix. (Auto-resolved: no updates in 24h)

🟢 SUPABASE Sep 10, 2026

🟡 Supabase projects decided to ghost their users, but engineers found the off switch and flipped it back. Global rollout underway—turns out the fix was just turning it off and on again. Your database's 'contemplation phase' is now optional. (Auto-resolved: no updates in 24h)

🟢 SUPABASE Aug 28, 2026

🔴 PostgreSQL 15 threw a tantrum because some ancient GLIBC version went missing. Database access got ghosted across multiple regions. Engineers performed emergency archaeology and rolled back the chaos. We're all friends again now. (Auto-resolved: no updates in 24h)