Skip to content

Outage tracker / Zapier

Is Zapier down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Zapier from all 10 regions we check.

As of Oct 5, 2026, 9:02 PM UTC, Zapier answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

No outage recorded in the 46 days we have measured Zapier (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 9:02 PM UTC
US-East281 msOperational
US-West379 msOperational
Europe268 msOperational
Asia-Pacific490 msOperational
US-Central310 msOperational
Canada312 msOperational
UK232 msOperational
Southeast Asia867 msOperational
Australia1306 msOperational
South America484 msOperational
their status pagetheir claim, not our reading

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

from Zapier's own status page, checked Oct 5, 2026, 8:52 PM UTC
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

  • 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
658msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 615ms2026-09-07 UTC: p95 536ms2026-09-08 UTC: p95 621ms2026-09-09 UTC: p95 698ms2026-09-10 UTC: p95 518ms2026-09-11 UTC: p95 491ms2026-09-12 UTC: p95 534ms2026-09-13 UTC: p95 599ms2026-09-14 UTC: p95 587ms2026-09-15 UTC: p95 565ms2026-09-16 UTC: p95 732ms2026-09-17 UTC: p95 828ms2026-09-18 UTC: p95 670ms2026-09-19 UTC: p95 801ms2026-09-20 UTC: p95 686ms2026-09-21 UTC: p95 613ms2026-09-22 UTC: p95 639ms2026-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 658ms
Sep 6Sep 20Oct 5
US-West
936msp95 · 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-09-06 UTC: p95 552ms2026-09-07 UTC: p95 494ms2026-09-08 UTC: p95 581ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 428ms2026-09-11 UTC: p95 555ms2026-09-12 UTC: p95 605ms2026-09-13 UTC: p95 674ms2026-09-14 UTC: p95 729ms2026-09-15 UTC: p95 683ms2026-09-16 UTC: p95 866ms2026-09-17 UTC: p95 948ms2026-09-18 UTC: p95 903ms2026-09-19 UTC: p95 869ms2026-09-20 UTC: p95 809ms2026-09-21 UTC: p95 854ms2026-09-22 UTC: p95 674ms2026-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 936ms
Sep 6Sep 20Oct 5
Europe
635msp95 · 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-09-06 UTC: p95 358ms2026-09-07 UTC: p95 326ms2026-09-08 UTC: p95 497ms2026-09-09 UTC: p95 380ms2026-09-10 UTC: p95 280ms2026-09-11 UTC: p95 311ms2026-09-12 UTC: p95 303ms2026-09-13 UTC: p95 286ms2026-09-14 UTC: p95 327ms2026-09-15 UTC: p95 365ms2026-09-16 UTC: p95 351ms2026-09-17 UTC: p95 404ms2026-09-18 UTC: p95 466ms2026-09-19 UTC: p95 470ms2026-09-20 UTC: p95 377ms2026-09-21 UTC: p95 490ms2026-09-22 UTC: p95 662ms2026-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 635ms
Sep 6Sep 20Oct 5
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-09-06 UTC: p95 930ms2026-09-07 UTC: p95 980ms2026-09-08 UTC: p95 970ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 744ms2026-09-11 UTC: p95 703ms2026-09-12 UTC: p95 791ms2026-09-13 UTC: p95 932ms2026-09-14 UTC: p95 993ms2026-09-15 UTC: p95 987ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 932ms2026-09-18 UTC: p95 916ms2026-09-19 UTC: p95 924ms2026-09-20 UTC: p95 979ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 823ms2026-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.0s
Sep 6Sep 20Oct 5
US-Central
872msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 692ms2026-09-07 UTC: p95 727ms2026-09-08 UTC: p95 648ms2026-09-09 UTC: p95 730ms2026-09-10 UTC: p95 772ms2026-09-11 UTC: p95 797ms2026-09-12 UTC: p95 596ms2026-09-13 UTC: p95 710ms2026-09-14 UTC: p95 718ms2026-09-15 UTC: p95 846ms2026-09-16 UTC: p95 688ms2026-09-17 UTC: p95 590ms2026-09-18 UTC: p95 555ms2026-09-19 UTC: p95 840ms2026-09-20 UTC: p95 747ms2026-09-21 UTC: p95 649ms2026-09-22 UTC: p95 663ms2026-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 872ms
Sep 6Sep 20Oct 5
Canada
981msp95 · 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-06 UTC: p95 746ms2026-09-07 UTC: p95 781ms2026-09-08 UTC: p95 804ms2026-09-09 UTC: p95 593ms2026-09-10 UTC: p95 702ms2026-09-11 UTC: p95 509ms2026-09-12 UTC: p95 541ms2026-09-13 UTC: p95 697ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 610ms2026-09-16 UTC: p95 570ms2026-09-17 UTC: p95 575ms2026-09-18 UTC: p95 593ms2026-09-19 UTC: p95 562ms2026-09-20 UTC: p95 515ms2026-09-21 UTC: p95 982ms2026-09-22 UTC: p95 865ms2026-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 981ms
Sep 6Sep 20Oct 5
UK
656msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 304ms2026-09-07 UTC: p95 362ms2026-09-08 UTC: p95 228ms2026-09-09 UTC: p95 289ms2026-09-10 UTC: p95 366ms2026-09-11 UTC: p95 201ms2026-09-12 UTC: p95 193ms2026-09-13 UTC: p95 197ms2026-09-14 UTC: p95 268ms2026-09-15 UTC: p95 352ms2026-09-16 UTC: p95 268ms2026-09-17 UTC: p95 222ms2026-09-18 UTC: p95 283ms2026-09-19 UTC: p95 246ms2026-09-20 UTC: p95 262ms2026-09-21 UTC: p95 400ms2026-09-22 UTC: p95 484ms2026-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 656ms
Sep 6Sep 20Oct 5
Southeast Asia
1.7sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 800ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 904ms2026-09-19 UTC: p95 789ms2026-09-20 UTC: p95 784ms2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.0s2026-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.7s
Sep 6Sep 20Oct 5
Australia
1.5sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 956ms2026-09-11 UTC: p95 976ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.5s2026-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.5s
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 996ms2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 861ms2026-09-14 UTC: p95 974ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-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.2s
Sep 6Sep 20Oct 5

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.

Get an email when we see Zapier go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 281msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 379msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 310msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 312msstatus code: 200checked: Oct 5, 2026, 9:02 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
    Operationallatency: 484msstatus code: 200checked: Oct 5, 2026, 9:02 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 268msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 232msstatus code: 200checked: Oct 5, 2026, 9:02 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 490msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 867msstatus code: 200checked: Oct 5, 2026, 9:02 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
      Operationallatency: 1306msstatus code: 200checked: Oct 5, 2026, 9:02 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 outages

Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication., 51mdeclared on their status page2026-10-05
Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222), 1h 5mdeclared on their status page2026-09-28
Agent runs (agents.zapier.com) intermittently experiencing 429 errors, 3h 58mdeclared on their status page2026-09-21
Zap History not displaying Zap runs, 1h 50mdeclared on their status page2026-09-09
Webhook Triggers and Zap Actions - Service Disruption, 3h 2mdeclared on their status page2026-09-08
Freshservice - Webhook delivery disruption, 144h 41mdeclared 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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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

primary
https://zapier.com/app/login
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 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 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.