β Back to the carnage
SUPABASE
π Supabase APIs are ghosting connections from Mullvad VPN users and possibly others, serving up timeouts and rejections like a bouncer at an exclusive club. Engineers are investigating whether this is a Mullvad-only problem or if other VPNs caught the same plague. (Auto-resolved: no updates in 24h)
// The official story
Edge Traffic Issues
// Status page says
May 13 , 16:46 UTC Update - We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to
π Official status page (for the PR-approved version)
https://status.supabase.com/incidents/ybxpvtjys08wSupabase'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)