Zapier had a major outage on October 16, 2026 that lasted about 1 hour 14 minutes. StatusBird's own monitoring recorded the first non-operational reading at 14:10 UTC and the first clear reading at 15:24 UTC, a measured window of 74 minutes.
StatusBird checks Zapier every 2 minutes from its own infrastructure, so the timeline below is what an independent observer saw rather than what the vendor's status page said afterwards. Every figure on this page comes from those readings.
When did Zapier go down and when did it recover?
| Event | Observation |
|---|---|
| First non-operational reading | 14:10 UTC, October 16, 2026 |
| Worst status observed | major |
| Recovery observed | 15:24 UTC, October 16, 2026 |
| Duration | 74 minutes |
| Non-operational readings | 37 |
Across the window StatusBird recorded 37 non-operational readings (37 major). Readings are taken every 2 minutes, so the true start and end may sit up to 2 minutes either side of the times above. All times are UTC.
How unusual is this for Zapier?
In the last 90 days StatusBird recorded 4 major or critical Zapier incidents, 208 minutes of combined downtime, and 99.84% availability. That makes this incident longer than the 52 minute average for Zapier over the same period.
| Date | Started | Duration | Worst status |
|---|---|---|---|
| October 5, 2026 | 18:56 UTC | 50 minutes | major |
| September 9, 2026 | 17:53 UTC | 110 minutes | major |
| August 18, 2026 | 23:51 UTC | 8 minutes | major |
Each of those windows was measured the same way as the one above, from the first non-operational reading to the first reading that cleared it. The full record, including the reliability grade, is on the Zapier reliability page.
What does a Zapier outage affect?
For online stores using Zapier, workflows connecting store tools silently stop running, so orders, inventory, and data stop syncing. The size of the loss depends on when the window landed: 74 minutes across a weekday peak is a different number from the same window overnight, which is why the start time above matters more than the duration alone.
What should a store do when Zapier goes down?
The response that matters happens in the first few minutes, before the vendor has posted anything on its own status page. In order:
- Confirm the problem is the vendor and not your own integration, by checking whether the failure affects every request or only yours.
- Tell your support team what is happening and what to say, before the tickets arrive rather than after.
- Pause any automated job that retries against the failing service, so a backlog does not fire twice on recovery.
- Write down the start time. Most vendor SLA credit claims require the window, and reconstructing it later from memory rarely works.
The longer version, with the checks specific to this service, is in what to do when Zapier goes down.
Knowing before your customers do
StatusBird detected this incident automatically and alerted affected store owners by SMS, email, and Slack within minutes of the first non-operational reading. It monitors Zapier alongside the other third-party services online stores depend on, and paid plans watch your own storefront as well. Start monitoring free.
Frequently asked questions
How long was the Zapier outage on October 16, 2026?
About 1 hour 14 minutes. StatusBird observed the first non-operational reading at 14:10 UTC and the first clear reading at 15:24 UTC, for a measured window of 74 minutes.
How bad did it get?
The worst status observed during the window was major. StatusBird normalizes every vendor status page onto the same four levels, operational, degraded, major and critical, so that severity means the same thing across services.
How often does Zapier go down?
In the last 90 days StatusBird recorded 4 major or critical Zapier incidents and 99.84% availability, with the average incident running 52 minutes. The current figure is always on the Zapier reliability page.
Was my store affected?
If your store calls Zapier during checkout or fulfillment, requests made between 14:10 UTC and 15:24 UTC on October 16, 2026 are the ones to check. Orders created in that window without a matching downstream record are the usual casualty.
Where does this data come from?
StatusBird checks Zapier every 2 minutes from its own infrastructure and records each reading. These figures are those readings, not a restatement of the vendor's own incident report. The method is documented at statusbird.io/methodology, and live status is at statusbird.io/status/zapier.