Is Supabase Down Right Now?
Developer-focused status guide for Supabase — check database, auth, realtime, and storage availability, with error codes and troubleshooting.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
Check Supabase Status
Supabase publishes an official status page. Check both official and third-party monitoring:
Supabase Service Components
Supabase is a multi-component platform. Each piece can fail independently — check which component is affected before debugging:
Managed Postgres with Row Level Security
Auto-generated REST API from database schema
Email, OAuth, phone, and magic link authentication
WebSocket-based realtime database subscriptions
Object storage for files and media
Deno-based serverless functions at the edge
Supabase management UI at app.supabase.com
Storage CDN and image transformation
Common Supabase Error Codes & Fixes
PGRST301Row-level security policy violationFix: Check your RLS policies in dashboard
503 Service UnavailablePostgREST API temporarily downFix: Wait and retry — usually resolves in minutes
Connection refused (5432)Direct database connection blocked or project pausedFix: Check if project is paused in dashboard
429 Too Many RequestsRate limit exceededFix: Add exponential backoff and request queuing
JWT expiredAuth session token has expiredFix: Call supabase.auth.refreshSession() or reauthenticate
schema "public" does not existDatabase migrations not applied or wrong schemaFix: Run migrations via Supabase CLI or dashboard
⚠️ Free Tier: Project Pausing
Supabase free tier projects auto-pause after 1 week of inactivity. This is the most common reason developers think Supabase is "down" when it's actually just their specific project that's paused.
Signs your project is paused: connection refused, "project not found" errors, or dashboard showing "Restore project" button.
How to Prevent Project Pausing
- • Upgrade to Pro plan ($25/month) — no auto-pausing
- • Set a GitHub Actions cron job to ping your Supabase REST API daily
- • Use Uptime Robot or a free monitoring service to ping
your-project.supabase.co/rest/v1/ - • Set up a simple health-check endpoint that calls a lightweight query
Troubleshooting Supabase Connection Issues
Check status.supabase.com first
The official status page shows live status for all regions and components. Most genuine outages are posted here within minutes.
Test with the Supabase CLI
Run supabase status to check project health locally. Use supabase db ping to test database connectivity.
Check connection pool limits
Free tier allows 60 direct connections. Use Supabase's built-in pooler (port 6543) instead of direct connections (port 5432) to handle connection limits gracefully. Set ?pgbouncer=true in your connection string.
Monitor with Better Stack
For production Supabase apps, use Better Stack to monitor your Supabase REST endpoint every 30 seconds. You'll get instant alerts before users report issues.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Supabase goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Supabase + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Related Developer Guides
Frequently Asked Questions
Is Supabase down right now?
To check if Supabase is down, visit the official Supabase status page at status.supabase.com. You can also check APIStatusCheck.com/api/supabase for third-party monitoring. Supabase publishes real-time incident updates on their status page, including affected components (Database, API, Auth, Realtime, Storage, Dashboard).
Why is my Supabase database connection failing?
Supabase database connection failures can be caused by: (1) Supabase service outage — check status.supabase.com, (2) Exceeded database connection pool limits — Supabase free tier allows 60 connections, (3) Project paused due to inactivity (free tier projects pause after 1 week of inactivity), (4) Network/firewall blocking port 5432 (PostgreSQL) or 443 (REST API), (5) Invalid connection string or rotated database password. Check your project dashboard for paused status first.
How do I wake up a paused Supabase project?
If your Supabase project is paused (free tier inactivity), go to your Supabase dashboard at app.supabase.com, navigate to your project, and click "Restore project." Restoration takes 2-5 minutes. To prevent future pauses, either upgrade to a paid plan or set up a scheduled task (cron job) that pings your database every few days to keep it active.
What is the Supabase rate limit and how do I know if I hit it?
Supabase enforces rate limits on their REST API and Auth endpoints. Free tier: 500 requests/second on the API, 4 signup requests/hour on Auth per IP. If you hit rate limits, you will receive a 429 Too Many Requests HTTP response. Solutions: implement request queuing, use the Supabase JS client (handles retries), or upgrade to a Pro plan for higher limits.
Does Supabase have planned maintenance windows?
Yes, Supabase performs planned maintenance, usually during low-traffic periods. They announce maintenance windows on status.supabase.com and via email to project owners. Most maintenance windows last 15-30 minutes. During maintenance, read operations may still work while write operations and auth may be interrupted.