Skip to main content
Zapier logo

Is Zapier Down?

No — Zapier is up

Reachable from all 8 checked regions

Average response time: 404ms

Last checked · checks run every 6 hours

Official status page: https://status.zapier.com

Zapier uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
470ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 64 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

64-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 38 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 31 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 30 checks
Sep 25: 100.00% uptime, 31 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
296ms
DNS 0ms TCP 2ms TLS 3ms TTFB 295ms
fra
330ms
DNS 1ms TCP 1ms TLS 4ms TTFB 330ms
gru
471ms
DNS 0ms TCP 2ms TLS 3ms TTFB 471ms
iad
337ms
DNS 1ms TCP 2ms TLS 5ms TTFB 337ms
jnb
829ms
DNS 4ms TCP 1ms TLS 6ms TTFB 823ms
lax
280ms
DNS 0ms TCP 2ms TLS 4ms TTFB 280ms
lhr
304ms
DNS 0ms TCP 2ms TLS 4ms TTFB 304ms
nrt
385ms
DNS 2ms TCP 1ms TLS 3ms TTFB 385ms

What Zapier does

Zapier connects applications so that an event in one triggers work in another, without code. Its own status page now lists Zaps alongside newer products: Tables, Canvas, Forms, Chatbots, Agents, MCP and Copilot. Because a Zap usually sits between two systems a business already depends on, a Zapier fault stops work in tools that are themselves healthy.

What an outage looks like

Zaps stop firing with no error anywhere the user would look, because the trigger simply never runs. Records that should have been created downstream are missing, and Zap history shows runs stuck or absent rather than failed. The editor may refuse to save or test a step, and webhook-triggered Zaps return errors to the calling system while scheduled ones quietly skip.

What to do about it

Check status.zapier.com, which lists Website, Zaps, Tables, Forms, Agents and the Developer Platform separately. Do not rebuild a Zap that stopped firing until the Zaps line is clear. Zapier records failed runs in Zap history and lets you replay them manually on every plan, including Free; Autoreplay retries errored runs automatically on Professional, Team and Enterprise, but will not replay safely halted ones.

Is it down for everyone, or just you?

If this page says Zapier is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Zapier outage FAQ

Is Zapier down or is it my connected app?
This is the hard part of a Zapier incident, because a Zap fails identically either way. Start at status.zapier.com and read the Zaps line rather than the top banner. If Zapier reads healthy, open Zap history: a run that errored on a specific step names the app that failed, whereas a Zapier-side fault usually shows as runs that never started at all.
Will my Zaps run after the outage ends, or are those triggers lost?
Errored runs are recorded in Zap history and can be replayed. Manual replay is available on every plan including Free, and Autoreplay retries errored runs automatically on Professional, Team and Enterprise. Autoreplay does not cover safely halted runs, so those need attention by hand. Triggers that never fired at all are the gap to check, since there is no history row to replay.
Does a Zapier outage affect Tables, Forms and Chatbots too?
Not necessarily. Zapier reports Zaps, Tables, Canvas, Forms, Chatbots, Agents, MCP and Copilot as separate components, and the newer products do not share every backend path with the automation engine. During an incident, read the specific line for the product you are using. The overall banner summarises the whole platform and will understate a fault confined to one product.
Why did my webhook Zap return an error to the calling system?
A webhook trigger is a live HTTP call into Zapier, so when Zapier is unavailable the caller gets an error immediately rather than a delayed failure. That means the sending system, not Zapier, is holding the only record of the event. Check whether that system retries failed webhooks, because those retries, not Zap history, are what recover the missed events.

How we measure this

  • We request Zapier's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Zapier publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Zapier goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required