Is Zapier down in the US?
Vendor reports no incidentWhat Zapier reports
Zapier reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:15 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn, San Jose, and Chicago
All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked Zapier at Nov 5, 2026, 5:19 PM UTC.
Over the last 24 hours we completed 109 checks from Ashburn, San Jose, and Chicago and 109 answered cleanly, 100.00% availability.
Of the 7 other regions we check Zapier from, all 7 read checks passing right now.
Email me when Zapier reports an incident on its status page, and again when it reports it resolved.
What our Ashburn, San Jose, and Chicago probes measured
Last checked Nov 5, 2026, 5:19 PM UTC.
Zapier from Ashburn, San Jose, and Chicago over the last 30 days
Over the last 30 days, Zapier answered our Ashburn probe in 873 ms on average, and 1 check in 20 took longer than 1,282 ms.
Over the last 30 days, Zapier answered our Chicago probe in 1,038 ms on average, and 1 check in 20 took longer than 1,511 ms.
Over the last 30 days, Zapier answered our San Jose probe in 1,059 ms on average, and 1 check in 20 took longer than 1,633 ms.
Ranked by average response time across the 10 cities we check Zapier from, Ashburn 3rd, Chicago 5th, San Jose 6th; Frankfurt was fastest at 622 ms and Sydney slowest at 2,093 ms.
From Ashburn, San Jose, and Chicago we ran 3,540 checks of Zapier in 30 days, and 3,540 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Zapier was slowest around 7 PM, at 1,368 ms on average over the last 14 days, and quickest around 10 PM, at 1,083 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 78 | 100.00% | 1,490 ms |
| Wed, Nov 4 | 110 | 100.00% | 1,834 ms |
| Tue, Nov 3 | 108 | 100.00% | 2,067 ms |
| Mon, Nov 2 | 115 | 100.00% | 1,469 ms |
| Sun, Nov 1 | 119 | 100.00% | 1,489 ms |
| Sat, Oct 31 | 120 | 100.00% | 1,384 ms |
| Fri, Oct 30 | 120 | 100.00% | 1,243 ms |
| Thu, Oct 29 | 120 | 100.00% | 1,246 ms |
| Wed, Oct 28 | 120 | 100.00% | 1,083 ms |
| Tue, Oct 27 | 120 | 100.00% | 704 ms |
| Mon, Oct 26 | 120 | 100.00% | 862 ms |
| Sun, Oct 25 | 120 | 100.00% | 871 ms |
| Sat, Oct 24 | 120 | 100.00% | 751 ms |
| Fri, Oct 23 | 123 | 100.00% | 1,003 ms |
Zapier outages measured from the US
Our Ashburn, San Jose, and Chicago probes measured no confirmed Zapier outage in the last 90 days.
How the other regions read right now
Of the 7 other regions we check Zapier from, all 7 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 34 checks |
| Tokyo | Checks passing | 100.00% of 21 checks |
| Toronto | Checks passing | 100.00% of 24 checks |
| London | Checks passing | 100.00% of 23 checks |
| Singapore | Checks passing | 100.00% of 24 checks |
| Sydney | Checks passing | 100.00% of 24 checks |
| São Paulo | Checks passing | 100.00% of 24 checks |
Other countries we check Zapier from
How we measured this
The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against Zapier's public endpoints. They are not user reports, and they are not Zapier's own status page.
See Zapier's full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter