Loading status…
Zapier status · SaaS · checked (4s ago)
Also searched as Zaps, Zapier Tables, Zapier Agents.
No — Zapier is not down. All Zapier systems are reported operational.
According to Zapier's official status page, Zapier was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Zapier's feed reported no outage in 100.00% of our checks.
Everything above is read from Zapier's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Zapier in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Zapier connects thousands of applications with automated workflows — a trigger in one service causing actions in others — and is the glue behind a great deal of operations work that nobody has written code for.
The status page separates the Zapier platform from the individual app integrations, and that distinction is the whole story: most Zap failures are caused by the app on one end of the Zap rather than by Zapier, and those are reported per-integration when they are reported at all. A green Zapier with a broken Google Sheets integration is a very ordinary situation.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Zapier's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Zapier was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 4s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Zapier's status endpoint.
Zapier has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Zapier posted itself — not every problem users hit.
resolved · Sep 9, 05:51 PM (10d ago)
resolved · Sep 8, 02:06 PM (11d ago)
resolved · Sep 1, 12:03 PM (18d ago)
resolved · Aug 28, 02:35 PM (22d ago)
resolved · Aug 26, 04:55 PM (24d ago)
resolved · Aug 21, 11:48 PM (29d ago)
resolved · Aug 21, 09:40 AM (29d ago)
resolved · Aug 19, 04:07 PM (31d ago)
resolved · Aug 18, 11:50 PM (32d ago)
resolved · Aug 18, 05:21 PM (32d ago)
resolved · Aug 17, 08:49 PM (33d ago)
resolved · Aug 6, 09:01 AM (44d ago)
resolved · Jul 28, 01:34 PM (53d ago)
resolved · Jul 22, 06:32 PM (59d ago)
resolved · Jul 22, 02:19 PM (59d ago)
resolved · Jul 21, 01:35 PM (60d ago)
resolved · Jul 21, 09:25 AM (60d ago)
resolved · Jul 13, 01:33 PM (68d ago)
resolved · Jul 11, 10:10 PM (70d ago)
resolved · Jul 8, 08:08 PM (73d ago)
Check the Zap history for the specific run — a failed step names the app that rejected it. Polling triggers run on an interval set by your plan, so a Zap that looks stuck may simply not have polled yet. Task limits pause Zaps at the end of a billing period, and a reconnected account with changed permissions fails on the next run rather than immediately.
