Is Supabase down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

Run the live check at the top of this page - it tests supabase.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Supabase is reachable for everyone or only failing for you.

Run the live check at the top of this page - it tests supabase.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Supabase is reachable for everyone or only failing for you.

This is the single most important thing to understand about Supabase reliability: the main website and each individual project run on different infrastructure. supabase.com being reachable confirms the platform's shared front end and control plane are healthy, but your project lives on its own yourproject.supabase.co subdomain with its own database and API, which can fail independently. Testing your project's own subdomain directly, rather than judging by the main site, is the only way to know whether your specific project is actually up.

Often not - free-tier projects that see no activity for an extended period are automatically paused rather than kept running indefinitely, and a paused project simply stops answering API and database requests until it's manually resumed from the dashboard. This looks identical to an outage from the outside - timeouts or connection refusals - but it's a billing-tier behaviour rather than a platform incident. Checking the project's status in the dashboard settles it before assuming anything is broken.

Connection pool exhaustion is a common, project-specific cause that has nothing to do with Supabase's platform health. Each project's database accepts a limited number of simultaneous connections, and an application that opens more than it releases - a leak, or simply high traffic - can exhaust that pool and start refusing new connections while the platform and every other project remain completely unaffected. Reviewing connection usage in the dashboard is the right next step rather than treating it as a wider outage.

Yes, because auth and the database/storage layers are separate services that can fail independently. An incident in the auth service can block sign-in and token issuance while your project's database keeps answering queries fine for already-authenticated sessions, and the reverse is just as possible - working auth with a struggling database. Narrowing down which specific service is failing, rather than assuming the whole project is down, usually points straight at the cause.