Datvero automation observatory · status.supabase.com
No. Supabase's status page reports all systems operational for Supabase: ap-east-1 (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
Read from Supabase's official status API at November 6, 2026, 18:10 UTC. Datvero republishes what Supabase states; it is not an independent uptime measurement.
From September 22 to November 6, 2026, status.supabase.com lists 30 incidents: 1 critical, 3 major, 18 minor and 8 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.3 h. Longest: “Intermittent latency in Eastern US” (September 29, 2026), 6.8 days. In the last 30 days: 20 incidents, 3 of them major or critical.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. Supabase's status page reports all systems operational for Supabase: ap-east-1 (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
From September 22 to November 6, 2026, status.supabase.com lists 30 incidents: 1 critical, 3 major, 18 minor and 8 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.3 h. Longest: “Intermittent latency in Eastern US” (September 29, 2026), 6.8 days. In the last 30 days: 20 incidents, 3 of them major or critical.
Supabase publishes it at https://status.supabase.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Supabase.
The status page lists what Supabase has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Supabase succeeds.
Datvero shows what Supabase’s public status feed publishes. That feed lists a single component and attaches no component to its incidents, so the components column of the incident table is empty. Open status.supabase.com for the full service view.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: Supabase's public status API (status.supabase.com/api/v2) is read every 5 minutes, its incident list every 15 minutes, and each incident is kept with its official timestamps. Durations run from the first post to the resolved post. Machine readable copy: services.json. Official source: https://status.supabase.com/.
Statuses, incident names and texts belong to Supabase. Datvero is not affiliated with Supabase. A green status page does not mean every workflow that calls Supabase succeeds.