Datvero automation observatory · status.zapier.com
No. Zapier's status page reports all systems operational for Zapier: Instant Triggers, Polling Triggers, Zap Editor and 15 other components (checked November 6, 2026, 18:00 UTC; this page refreshes every 15 minutes).
Read from Zapier's official status API at November 6, 2026, 18:00 UTC. Datvero republishes what Zapier states; it is not an independent uptime measurement.
From May 20 to November 6, 2026, status.zapier.com lists 53 incidents: 0 critical, 5 major, 17 minor and 31 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.6 h. Longest: “Connection errors affecting Salesforce Pardot Zaps” (October 23, 2026), 3.5 days. In the last 30 days: 14 incidents, 2 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. Zapier's status page reports all systems operational for Zapier: Instant Triggers, Polling Triggers, Zap Editor and 15 other components (checked November 6, 2026, 18:00 UTC; this page refreshes every 15 minutes).
From May 20 to November 6, 2026, status.zapier.com lists 53 incidents: 0 critical, 5 major, 17 minor and 31 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.6 h. Longest: “Connection errors affecting Salesforce Pardot Zaps” (October 23, 2026), 3.5 days. In the last 30 days: 14 incidents, 2 of them major or critical.
Zapier publishes it at https://status.zapier.com/. This page republishes its public feed every 15 minutes with timestamps. Datvero is not affiliated with Zapier.
The status page lists what Zapier 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 Zapier succeeds.
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: Zapier's public status API (status.zapier.com/api/v2) is read every 15 minutes by Datvero's collector, which keeps each incident with its official timestamps since August 16, 2026. Durations run from the first post to the resolved post. Machine readable copy: services.json. Official source: https://status.zapier.com/.
Statuses, incident names and texts belong to Zapier. Datvero is not affiliated with Zapier. A green status page does not mean every workflow that calls Zapier succeeds.