Skip to content

Outage tracker / Zapier

Is Zapier down?

I'm having a problem
our independent probeslive · checked Sep 3, 2026, 1:22 AM UTC
US-East721 msOperational
US-West386 msOperational
Europe204 msOperational
Asia-Pacific1040 msOperational
their status pagetheir claim, not our reading

Zapier reports: All systems operational (“All Systems Operational”)

from Zapier's own status page, checked Sep 3, 2026, 12:48 AM UTC

Zapier reports an active incident: Freshservice - Webhook delivery disruption (all systems operational, since Sep 1, 2026, 12:03 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

Our probes and Zapier's own status page agree: both show Zapier as reachable right now.

Zapier's own component breakdown, as they publish it

  • TablesOperational
  • CanvasOperational
  • Developer PlatformOperational
  • Lead RouterOperational
  • LoginOperational
  • FormsOperational
  • Zap HistoryOperational
  • CopilotOperational
  • MCPOperational
  • SupportOperational
  • FunctionsOperational
  • WebsiteOperational
  • Polling TriggersOperational
  • Zap EditorOperational
  • ChatbotsOperational
  • Searches & WritesOperational
  • AgentsOperational
  • Instant TriggersOperational

These are Zapier's components, named and scored by Zapier. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Zapier's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Zapier response time, by region

US-East
708msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 759ms2026-08-21 UTC: p95 782ms2026-08-22 UTC: p95 728ms2026-08-23 UTC: p95 775ms2026-08-24 UTC: p95 709ms2026-08-25 UTC: p95 803ms2026-08-26 UTC: p95 731ms2026-08-27 UTC: p95 624ms2026-08-28 UTC: p95 977ms2026-08-29 UTC: p95 520ms2026-08-30 UTC: p95 535ms2026-08-31 UTC: p95 554ms2026-09-01 UTC: p95 606ms2026-09-02 UTC: p95 1.0s2026-09-03 UTC: p95 708ms
Aug 5Aug 19Sep 3
US-West
450msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 561ms2026-08-21 UTC: p95 708ms2026-08-22 UTC: p95 557ms2026-08-23 UTC: p95 591ms2026-08-24 UTC: p95 671ms2026-08-25 UTC: p95 651ms2026-08-26 UTC: p95 873ms2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 625ms2026-08-29 UTC: p95 886ms2026-08-30 UTC: p95 728ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 664ms2026-09-02 UTC: p95 902ms2026-09-03 UTC: p95 450ms
Aug 5Aug 19Sep 3
Europe
342msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 337ms2026-08-21 UTC: p95 344ms2026-08-22 UTC: p95 387ms2026-08-23 UTC: p95 415ms2026-08-24 UTC: p95 544ms2026-08-25 UTC: p95 475ms2026-08-26 UTC: p95 453ms2026-08-27 UTC: p95 450ms2026-08-28 UTC: p95 325ms2026-08-29 UTC: p95 376ms2026-08-30 UTC: p95 488ms2026-08-31 UTC: p95 467ms2026-09-01 UTC: p95 515ms2026-09-02 UTC: p95 501ms2026-09-03 UTC: p95 342ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.0sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 928ms2026-08-21 UTC: p95 1.0s2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 1.0s
Aug 5Aug 19Sep 3

Is it Zapier, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Zapier -- it cannot diagnose Zapier's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 721msstatus code: 200checked: Sep 3, 2026, 12:43 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Zapier normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 386msstatus code: 200checked: Sep 3, 2026, 1:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Zapier normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 204msstatus code: 200checked: Sep 3, 2026, 1:22 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Zapier normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 1040msstatus code: 200checked: Sep 3, 2026, 12:53 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Zapier normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionZapier is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Zapier, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Zapier yet, which is not evidence that nothing is wrong.

Recent outages

Freshservice - Webhook delivery disruptiondeclared on their status page2026-09-01
Tables, Chatbots, and Forms not loading for some customers, 1h 1mdeclared on their status page2026-08-28
Intermittent instant trigger failures, 4h 46mdeclared on their status page2026-08-26
403 errors when trying to connect or reconnect to ActiveCampaign, 2h 31mdeclared on their status page2026-08-21
Salesforce integration - trigger and connection disruptions, 100h 39mdeclared on their status page2026-08-21
Errors related to Pipedrive invalid IDs, 3h 29mdeclared on their status page2026-08-19
Zapier Functions temporarily unavailable, 8mdeclared on their status page2026-08-18
Sales Contact forms are not loading, 25h 15mdeclared on their status page2026-08-18

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Zapier since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Zapier covering any window you pick, with our measurements and Zapier's own claim at the time, side by side.

Full availability history for Zapier: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

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 servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Zapier, and again when they can reach it again. That is our own measurement from ten regions, not Zapier's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Zapier uptime measured by RealUptimeLive, from this page's own readings.
[![Zapier uptime measured by RealUptime](https://realuptime.io/outages/zapier/badge.svg?days=30)](https://realuptime.io/outages/zapier)
<a href="https://realuptime.io/outages/zapier"><img src="https://realuptime.io/outages/zapier/badge.svg?days=30" alt="Zapier uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Zapier's SLA implies, from our measurement

At or above your target

We measured none of downtime for Zapier over the 337h 30m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Zapier's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://status.zapier.com/api/v2/status.json
secondary
https://status.zapier.com/
RealUptime is not affiliated with Zapier; the name identifies what we measured, and nothing here speaks for Zapier's own team. We send a single web request to Zapier from 4 regions on our own schedule and time the response. We do not see inside Zapier's systems, do not use an account or real transaction, and are not the same signal Zapier's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Zapier is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Zapier operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.