When Supabase Goes Down: A Survival Guide for Your Team
Your app's login page suddenly shows a spinner that never stops. Users can't sign in, can't load their data, can't do anything. You check your code — nothing changed. You check your hosting — it's fine. The problem is your Supabase project: the database hit its connection limit 12 minutes ago, and every API request is timing out.
What Happens on Your Team
The Full-Stack Developer
Opens the browser console — every API call returns a 500. Checks Supabase dashboard — the project is active, but the database shows 60/60 connections used. Realizes a connection leak in the edge functions has been accumulating for hours.
The real cost: Supabase abstracts the database, but connection limits are real. When you hit the limit, every query fails simultaneously — auth, data, storage, everything. There's no graceful degradation. Your entire app breaks at once.
What they should have had: An HTTP monitor on the Supabase REST API endpoint. When connections are exhausted, API requests return 500s. The monitor catches the spike in errors before users start reporting login failures.
The Indie Hacker
Launches a side project on Supabase free tier. Doesn't use it for a week. Comes back, app is broken. The Supabase project paused due to inactivity. Has to log into the dashboard and manually unpause it.
The real cost: Free tier projects pause after 7 days of inactivity. If you have real users on a free tier project (during early validation), they see a broken app until you manually unpause. There's no automatic wake-up.
What they should have had: A monitor pinging the Supabase API endpoint every 5 minutes. If the project is active, the check keeps it alive. If it somehow pauses, the monitor detects the failure and alerts you immediately instead of waiting for a user complaint.
The Tech Lead
The team's app works fine locally. Production is broken. After 30 minutes of debugging, discovers that Supabase's auth service had a brief outage in their region. The auth health endpoint was returning 503s for 8 minutes.
The real cost: When your auth provider goes down, your entire app is effectively down — even if your servers are healthy. Users can't log in, tokens can't be refreshed, and protected routes return errors.
What they should have had: Separate monitors for the auth health endpoint and the REST API. When auth is down but the database is fine, you know the issue is isolated and can display a targeted error message instead of a blank page.
Why Monitor Supabase?
Supabase projects can pause after inactivity on the free tier, and even on paid plans, database connection limits, edge function cold starts, and auth service issues can silently break your app. Since Supabase powers your backend, an outage there means your entire application stops working.
What to Monitor
your-project.supabase.coYour Supabase project's API endpointyour-project.supabase.co/auth/v1/healthAuth service health checkyour-project.supabase.co/rest/v1/PostgREST API availabilityWhat You Should Actually Do
- 1Monitor your Supabase project's REST API endpoint — this is the core of your backend, and connection exhaustion or project pausing will show up here first
- 2Add a separate monitor for the auth health endpoint — auth outages break login flows even when the database is healthy
- 3Track response times — gradually increasing response times from Supabase usually indicate connection pool pressure or query performance issues
- 4Set up alerts to your phone — Supabase issues break your entire app, not just one feature, so fast detection is critical
- 5Check status.supabase.com during incidents — but remember it covers the platform, not your specific project's connection limits or configuration
Supabase's Official Status Page
Supabase publishes real-time status at status.supabase.com. Monitoristic doesn't replace this — it complements it. The official page tells you when Supabase reports an issue. Your own monitor tells you when your connection is affected, often before the status page updates. You also get push alerts instead of checking a webpage manually.
Supabase gives you a full backend in minutes, but that convenience means a single point of failure. When Supabase is down, your app is down — there's no fallback. External monitoring is how you find out about connection limits, auth outages, and project pauses before your users do.
Related Reading
Skip the panic. Know in 60 seconds.
Start Monitoring Supabase →Plans from $5/month · 14-day money-back guarantee