Skip to content

Outage tracker / Zapier

Is Zapier down?

I'm having a problem

Vendor reports an incident, no impactWhat Zapier reports

Zapier reports an incident on its status page: Security updates in progress for third-party software components.

Impact: no impact. Since 2026-10-22 15:29 UTC.

Latest update, 2026-10-22 15:29 UTC: We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We have not identified any customer impact or evidence of exploitation, and no action is needed on your part. Some updates are rolling out now, so you may see brief latency to workflows while they complete.

Zapier's status page

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 passingchecked 3 minutes ago

Our checks of Zapier pass from all 10 regions we check.

As of Oct 22, 2026, 7:03 PM UTC, RealUptime's checks of Zapier passed in all 10 regions that returned a reading.

Front-door checks

our check readinglive · checked Oct 22, 2026, 7:03 PM UTC
US-East692 msChecks passing
US-West1344 msChecks passing
Europe819 msChecks passing
Asia-Pacific1550 msChecks passing
US-Central2659 msChecks passing
Canada1162 msChecks passing
UK612 msChecks passing
Southeast Asia1819 msChecks passing
Australia2318 msChecks passing
South America4492 msChecks passing
their status pagetheir claim, not our reading

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

from Zapier's own status page, checked Oct 22, 2026, 7:03 PM UTC

Zapier reports an active incident: Security updates in progress for third-party software components (all systems operational, since Oct 22, 2026, 3:29 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.

Zapier's own status page shows no incident, and our checks of Zapier pass right now.

Zapier's own component breakdown, as they publish it

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

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
1.1sp95 · 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-09-23 UTC: p95 632ms2026-09-24 UTC: p95 596ms2026-09-25 UTC: p95 662ms2026-09-26 UTC: p95 718ms2026-09-27 UTC: p95 623ms2026-09-28 UTC: p95 680ms2026-09-29 UTC: p95 707ms2026-09-30 UTC: p95 629ms2026-10-01 UTC: p95 829ms2026-10-02 UTC: p95 513ms2026-10-03 UTC: p95 601ms2026-10-04 UTC: p95 554ms2026-10-05 UTC: p95 641ms2026-10-06 UTC: p95 867ms2026-10-07 UTC: p95 656ms2026-10-08 UTC: p95 934ms2026-10-09 UTC: p95 870ms2026-10-10 UTC: p95 864ms2026-10-11 UTC: p95 924ms2026-10-12 UTC: p95 981ms2026-10-13 UTC: p95 857ms2026-10-14 UTC: p95 585ms2026-10-15 UTC: p95 530ms2026-10-16 UTC: p95 670ms2026-10-17 UTC: p95 955ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 828ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
US-West
3.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 589ms2026-09-24 UTC: p95 706ms2026-09-25 UTC: p95 819ms2026-09-26 UTC: p95 798ms2026-09-27 UTC: p95 716ms2026-09-28 UTC: p95 714ms2026-09-29 UTC: p95 686ms2026-09-30 UTC: p95 723ms2026-10-01 UTC: p95 703ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 703ms2026-10-04 UTC: p95 783ms2026-10-05 UTC: p95 929ms2026-10-06 UTC: p95 487ms2026-10-07 UTC: p95 650ms2026-10-08 UTC: p95 537ms2026-10-09 UTC: p95 639ms2026-10-10 UTC: p95 738ms2026-10-11 UTC: p95 929ms2026-10-12 UTC: p95 850ms2026-10-13 UTC: p95 699ms2026-10-14 UTC: p95 641ms2026-10-15 UTC: p95 723ms2026-10-16 UTC: p95 780ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 3.2s
Sep 23Oct 7Oct 22
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 506ms2026-09-24 UTC: p95 448ms2026-09-25 UTC: p95 482ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 456ms2026-09-28 UTC: p95 486ms2026-09-29 UTC: p95 480ms2026-09-30 UTC: p95 427ms2026-10-01 UTC: p95 762ms2026-10-02 UTC: p95 575ms2026-10-03 UTC: p95 607ms2026-10-04 UTC: p95 681ms2026-10-05 UTC: p95 621ms2026-10-06 UTC: p95 563ms2026-10-07 UTC: p95 638ms2026-10-08 UTC: p95 509ms2026-10-09 UTC: p95 543ms2026-10-10 UTC: p95 597ms2026-10-11 UTC: p95 551ms2026-10-12 UTC: p95 572ms2026-10-13 UTC: p95 527ms2026-10-14 UTC: p95 455ms2026-10-15 UTC: p95 489ms2026-10-16 UTC: p95 450ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 572ms2026-10-20 UTC: p95 691ms2026-10-21 UTC: p95 657ms2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Asia-Pacific
2.5sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 830ms2026-09-24 UTC: p95 985ms2026-09-25 UTC: p95 966ms2026-09-26 UTC: p95 820ms2026-09-27 UTC: p95 914ms2026-09-28 UTC: p95 922ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 950ms2026-10-07 UTC: p95 829ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 878ms2026-10-11 UTC: p95 973ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 3.1s2026-10-18 UTC: p95 3.8s2026-10-19 UTC: p95 3.9s2026-10-20 UTC: p95 3.7s2026-10-21 UTC: p95 3.8s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22
US-Central
2.7sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 756ms2026-09-24 UTC: p95 720ms2026-09-25 UTC: p95 479ms2026-09-26 UTC: p95 583ms2026-09-27 UTC: p95 556ms2026-09-28 UTC: p95 793ms2026-09-29 UTC: p95 827ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 661ms2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 855ms2026-10-06 UTC: p95 811ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 982ms2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 419ms2026-10-12 UTC: p95 932ms2026-10-13 UTC: p95 638ms2026-10-14 UTC: p95 786ms2026-10-15 UTC: p95 622ms2026-10-16 UTC: p95 995ms2026-10-17 UTC: p95 2.7s2026-10-18 UTC: p95 3.5s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.7s
Sep 23Oct 7Oct 22
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 989ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 641ms2026-09-27 UTC: p95 502ms2026-09-28 UTC: p95 621ms2026-09-29 UTC: p95 655ms2026-09-30 UTC: p95 563ms2026-10-01 UTC: p95 960ms2026-10-02 UTC: p95 974ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 967ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 780ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 955ms2026-10-11 UTC: p95 758ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 996ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
UK
1.5sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 483ms2026-09-24 UTC: p95 430ms2026-09-25 UTC: p95 467ms2026-09-26 UTC: p95 517ms2026-09-27 UTC: p95 537ms2026-09-28 UTC: p95 461ms2026-09-29 UTC: p95 372ms2026-09-30 UTC: p95 530ms2026-10-01 UTC: p95 914ms2026-10-02 UTC: p95 654ms2026-10-03 UTC: p95 596ms2026-10-04 UTC: p95 630ms2026-10-05 UTC: p95 651ms2026-10-06 UTC: p95 714ms2026-10-07 UTC: p95 600ms2026-10-08 UTC: p95 648ms2026-10-09 UTC: p95 621ms2026-10-10 UTC: p95 859ms2026-10-11 UTC: p95 757ms2026-10-12 UTC: p95 706ms2026-10-13 UTC: p95 528ms2026-10-14 UTC: p95 453ms2026-10-15 UTC: p95 525ms2026-10-16 UTC: p95 442ms2026-10-17 UTC: p95 788ms2026-10-18 UTC: p95 859ms2026-10-19 UTC: p95 816ms2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 953ms2026-09-30 UTC: p95 817ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 950ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 902ms2026-10-18 UTC: p95 795ms2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
Australia
3.8sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 990ms2026-09-27 UTC: p95 938ms2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 2.3s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 3.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 4.7s2026-10-18 UTC: p95 4.5s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 5.1s2026-10-21 UTC: p95 4.8s2026-10-22 UTC: p95 3.8s
Sep 23Oct 7Oct 22
South America
5.2sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 2.2s2026-10-02 UTC: p95 2.6s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 864ms2026-10-08 UTC: p95 976ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 990ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 917ms2026-10-16 UTC: p95 957ms2026-10-17 UTC: p95 3.4s2026-10-18 UTC: p95 4.0s2026-10-19 UTC: p95 3.4s2026-10-20 UTC: p95 3.9s2026-10-21 UTC: p95 3.8s2026-10-22 UTC: p95 5.2s
Sep 23Oct 7Oct 22

Check your own site while you wait on Zapier

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.

Email me when Zapier reports an incident on its status page, and again when it reports it resolved.

Get an email when Zapier reports an incident

Email me when Zapier reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Zapier's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 692msstatus code: 200checked: Oct 22, 2026, 6:54 PM 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
      Checks passinglatency: 1344msstatus code: 200checked: Oct 22, 2026, 7:03 PM 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.
    • US-Central
      Checks passinglatency: 2659msstatus code: 200checked: Oct 22, 2026, 6:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Zapier normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1162msstatus code: 200checked: Oct 22, 2026, 6:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Zapier normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 4492msstatus code: 200checked: Oct 22, 2026, 6:53 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Zapier normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 819msstatus code: 200checked: Oct 22, 2026, 6:57 PM 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.
    • UK
      Checks passinglatency: 612msstatus code: 200checked: Oct 22, 2026, 6:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Zapier normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1550msstatus code: 200checked: Oct 22, 2026, 6:37 PM 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.
    • Southeast Asia
      Checks passinglatency: 1819msstatus code: 200checked: Oct 22, 2026, 6:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Zapier normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2318msstatus code: 200checked: Oct 22, 2026, 6:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Zapier normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Security updates in progress for third-party software componentsdeclared on their status page2026-10-22
Assessment of recently reported PHP vulnerabilities, 44mdeclared on their status page2026-10-22
Delayed real-time updates in Zapier Tables, 25h 1mdeclared on their status page2026-10-21
Upstream errors with the BambooHR integration, 6h 12mdeclared on their status page2026-10-21
Errors publishing Zaps from Guided Templates with app approvals enabled, 1h 13mdeclared on their status page2026-10-16
Permission errors affecting shared Forms, Canvas, and Tables, 49mdeclared on their status page2026-10-14
Zoom Team Chat App connection failure, 14h 7mdeclared on their status page2026-10-14
Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters, 1h 48mdeclared on their status page2026-10-12

check 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 check readings and Zapier's own claim at the time, side by side.

Full check history for Zapier: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Zapier uptime by RealUptime's checksLive, from this page's own readings.
[![Zapier uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Zapier down?", https://realuptime.io/outages/zapier. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primary
https://zapier.com/app/login
secondary
https://status.zapier.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: zapier.com

RealUptime is not affiliated with Zapier; the name identifies what we checked, and nothing here speaks for Zapier's own team. We send a single web request to Zapier from 10 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. What we check for Zapier is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.