Supabase Down | Server Status Maintenance

As of Monday, November 24, 2025, there are no active widespread outages reported for Supabase. All major systems (Database, Auth, Storage, and API) are listed as Operational.

However, Supabase just completed a major scheduled maintenance window yesterday (Nov 23). If you are currently unable to connect, you are likely experiencing a local configuration issue or a “Paused Project.”

Here is the step-by-step guide to troubleshooting this, ranked from the most likely cause to the least.

1. The “Paused Project” Check (Most Common)

If you are on the Free Tier and haven’t used your project in a few days, Supabase automatically “pauses” the database to save resources.

• The Symptom: Your app throws “Connection Refused” or “500” errors, but the Supabase dashboard works fine.

• The Fix:

  1. Log in to the Supabase Dashboard.

  2. If your project has a “PAUSED” badge next to it, click it.

  3. Click “Restore Project”. This takes about 2-5 minutes to spin back up.

2. The “IPv4 vs IPv6” Connection Error

Supabase recently migrated many databases to IPv6-only to save costs. If your local network or ISP (or specific VPN) does not support IPv6, you will get a “Connection Timed Out” error.

• The Fix: You must use the Supavisor (Connection Pooler) URL, which supports IPv4.

  • Go to Settings > Database > Connection Pooling.

  • Copy the “Transaction Mode” connection string (Port 6543).

  • Replace your current direct connection string (Port 5432) with this one.

Also Read : ICEGATE Sea IGM Status | Quick Access Guide

3. Restart the Database

Sometimes the database process gets stuck or hits a memory limit (common on the Free Tier with heavy queries), making it appear “down.”

• The Fix:

  1. Go to Settings > Database in the dashboard.

  2. Scroll to the bottom to the “Restart Database” section.

  3. Click Restart. This takes about 60 seconds and clears almost all “stuck” connection issues.

4. Check Recent Maintenance Logs

Since there was urgent maintenance on the Management API from Nov 21–23, 2025, your specific project region might be lagging in updates.

• Check the official Supabase Status Page specifically for your region (e.g., us-east-1 or eu-central-1) to ensure there isn’t a minor degradation listed there.

Summary Checklist

• [ ] Is your project paused? (Check Dashboard)

• [ ] Are you using Port 6543? (Fixes IPv6 issues)

• [ ] Have you restarted the instance? (Clears memory hangs)