At a glance
Project Uptime is the real-time availability state of your Supabase project: whether the database and its API surface are reachable and responding right now. It is the top-line “is it up?” signal an executive or on-call lead checks first, before drilling into the performance and capacity cards that explain any dip.
What it tracks
This card reports Project Uptime for the selected period as a real-time availability reading. In practice it reflects whether the project’s core services, the Postgres database and the PostgREST/API layer in front of it, are healthy and answering requests, surfaced as an up/down state and, over a period, as an availability percentage. A project can be technically “running” yet effectively unavailable to users if the API layer is erroring or the connection pool is exhausted, so uptime here is best read as reachability of the whole project rather than a single process being alive. There is no alert threshold on this card: it is the executive-overview headline, and the actionable detail lives in the cards it points to. When uptime dips, the cause is almost always visible in a related card: PostgREST 5xx Error Rate % for API failures, Supavisor Pool Saturation % for connection exhaustion, Database Disk Usage % for a project pushed into restricted mode by a full disk, or the Supabase Health Score composite for an at-a-glance summary.Reconciling against the source
Cross-check against the Supabase status page for your project’s region and the project’s own Reports / health view in the Supabase dashboard; a simple live probe such asSELECT 1; over the connection or a request to the project’s REST health endpoint confirms reachability from your side. Brief differences usually reflect probe timing and whether the dip was at the database layer or only the API layer in front of it.