Zapier is down: what we know so far
This page is live and updates as StatusBird re-checks Zapier, every 2 minutes. First non-operational reading 10:51 UTC on October 23, 2026.
StatusBird began recording non-operational readings for Zapier at 10:51 UTC on 23 October 2026. The worst state we measured was major. We have logged 30 non-operational readings, polling every 2 minutes, covering 1 hour so far. The service had not recovered when this was written, so the problem was still running. Zapier's status page showed no incident at that point.
Incident at a glance
| Service | Zapier |
|---|---|
| Date | October 23, 2026 |
| StatusBird first saw it | 10:51 UTC |
| Vendor posted an incident | Not published |
| Recovery observed | Not yet |
| Duration | 2 hours 57 minutes and counting |
| Worst status observed | major |
| Non-operational readings | 89 |
All times UTC. StatusBird polls Zapier every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was Zapier down on October 23, 2026?
Yes. StatusBird recorded Zapier as major from 10:51 UTC, and it was still non-operational 2 hours 57 minutes later at the most recent reading. 89 consecutive checks came back non-operational.
Workflow automations may be failing.
What caused the Zapier outage?
The cause is not known. Zapier had posted no incident on its status page when this was written, and it has published no cause. StatusBird reports only what its own checks measured, so we will not guess at what went wrong inside the service.
The cause has not yet been published by Zapier. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if Zapier publishes a root cause.
How long was Zapier down?
2 hours 57 minutes so far, measured from the first non-operational reading at 10:51 UTC to the most recent reading, which was still non-operational. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 10:51 UTC | StatusBird records its first non-operational reading |
| 10:54 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 13:48 UTC | Still non-operational at the last reading |
Who and what was affected
This affects any store that relies on Zapier to move data between its shop, its email tool, its spreadsheets and its support desk. Workflow automations may be failing, so order confirmations, stock updates, customer tagging and accounting handoffs may not have run during this window. Because the problem was still running when this was written, more automation runs may be missed after the measured hour.
How StatusBird detected it
StatusBird recorded its first non-operational reading for Zapier at 10:51 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on Zapier's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.
Method: StatusBird reads Zapier's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Check your Zapier task history for the window from 10:51 UTC on 23 October 2026 onward and replay any runs that did not fire.
- Do not rely on a vendor status page alone, as Zapier had posted nothing while our checks were failing.
- Keep a manual fallback for the automations that touch money or stock, so orders can still be processed by hand.
- Set alerts on your own side for automations that stop running, rather than assuming silence means success.
The longer version, with the checks specific to this service, is in the Zapier outage playbook.
Frequently asked questions
Was Zapier down on October 23, 2026?
Yes. StatusBird recorded Zapier as major from 10:51 UTC on October 23, 2026. The incident was still running 2 hours 57 minutes later when this page last updated.
How long was Zapier down?
2 hours 57 minutes, measured from the first non-operational reading at 10:51 UTC to the most recent reading, which was still non-operational. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the Zapier outage?
The cause has not yet been published by Zapier. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if Zapier publishes a root cause.
How was this Zapier outage detected?
StatusBird recorded its first non-operational reading for Zapier at 10:51 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on Zapier's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.
Was my store affected?
If your store calls Zapier during checkout or fulfillment, the requests to check are the ones made between 10:51 UTC and now on October 23, 2026. Workflow automations may be failing.
Monitor Zapier with StatusBird
This page exists because StatusBird was already watching. It checks Zapier and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 10:51 UTC.