Is Supabase down?
Right now
No. Supabase is operational.
No incidents reported.
Read from status.supabase.com · every 60s
For agents
proceed
Proceed.
GET upbutler.com/status/supabase/status.agent.json
MCP: upstream_status {"service":"supabase"}
Postgres, Auth, Storage, Realtime and Edge Functions.
What Supabase reports
Operational
Taken as is from Supabase's own status page API. Incident titles and component names below are theirs.
Open status.supabase.comUpButler's independent probe
Management API is answeringHTTP 401 · 74 ms
One request without credentials to api.supabase.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:24 UTC
Open at Supabase
- Scheduled Platform Maintenance 07/02scheduled maintenance
Starts
We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades. Maintenance Window: • Start time: 03:00 UTC on July 2, 2026 • End time: 04:00 UTC on July 2, 2026 Impact: • Various platform operations will be delayed during this window • These may include project creation and initial configuration/setup • All affected operations will be rescheduled at the end of the window to ensure no operation is dropped
Text written by Supabase, shown unchanged.
Supabase components
1 operational
- ap-east-1Operational
Supabase incidents, last 90 days
4 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted 2 h 56 min; the longest 7 days.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Upgrade Issues | none | 2 h 56 min | |
| Increased errors on management api leading to project operation failures | minor | 1 h 10 min | |
| Intermittent latency in Eastern US | minor | 7 days | |
| Log Ingestion Degradation | none | 49 min |
Tell your outage from Supabase's
Declare that your project depends on Supabase. When one of your monitors fails while Supabase has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- supabasecurl -s https://upbutler.com/status/supabase/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "supabase",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Supabase down right now?
- No. As of 2026-10-10 05:10 UTC, Supabase is operational. This page reads the status again every 60 seconds.
- Where does this status come from?
- From Supabase's own status page API at https://status.supabase.com. UpButler reads it once for everyone (not once per visitor) every 60 seconds with conditional requests, and shows it unchanged: incident titles and component names are Supabase's words.
- What does UpButler's own Supabase check prove?
- Every two minutes UpButler sends one request without credentials to the Supabase Management API (api.supabase.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Supabase reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Supabase status?
- Fetch https://upbutler.com/status/supabase/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"supabase"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Supabase's?
- Add "supabase" to the dependencies of your UpButler workspace. When one of your monitors fails while Supabase has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in databases and data
UpButler is not affiliated with Supabase. Status and incident text belong to Supabase and are read from their public status source; the probe result is UpButler's own measurement.