← Back to the carnage
SUPABASE

🟑 Supabase's DNS API decided to ghost new project creation attempts. Engineers are frantically checking if they unplugged the right cable this time. The irony of a backend service making backends inaccessible is not lost. (Auto-resolved: no updates in 24h)

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

// The official story

DNS Api failures impacting project creation

// Status page says

Jun 18 , 06:39 UTC Investigating - We are investigating DNS Api outage impacting project creation. Impact and details are under review.

πŸ”— Official status page (for the PR-approved version)

https://status.supabase.com/incidents/72nly8q8062v

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)