Where does this status come from?

From Zapier's own status page API at https://status.zapier.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Zapier's words.

How can my agent or app check Zapier status?

Fetch https://upbutler.com/status/zapier/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"zapier"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Zapier's?

Add "zapier" to the dependencies of your UpButler workspace. When one of your monitors fails while Zapier has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Zapier down?

Right now

Partly. Zapier is degraded.

Degraded performance.

Read from status.zapier.com 3 min ago · every 120s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/zapier/status.agent.json

MCP: upstream_status {"service":"zapier"}

Zaps, webhooks and the MCP / agent actions platform.

What Zapier reports

Degraded· 1 open incident

Taken as is from Zapier's own status page API. Incident titles and component names below are theirs.

Open status.zapier.com

UpButler's independent probe

There is no keyless endpoint of Zapier that says anything useful, so UpButler does not probe it. To check your own Zapier account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Zapier

zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by Googleidentified · impact none
Since 2026-10-09 17:07 UTC
We've completed the initial cleanup and are now collaborating with the Google team to determine the next steps needed to clear the "dangerous site" flag on our file storage domain. During this period, your files that passed through Zapier remain safe, and Zaps, Tables, and Forms are functioning normally. Files passing through Zapier work normally on the system side as well. However, when opening a Zapier-hosted file link directly in your browser, you may still see the "dangerous site" warning u…

Text written by Zapier, shown unchanged.

Zapier components

18 operational

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

Zapier incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Zapier.

Started (UTC)	Incident	Impact	Lasted
2026-10-05 18:54	Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.	major	51 min
2026-09-28 12:13	Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)	minor	1 h 5 min

Tell your outage from Zapier's

Declare that your project depends on Zapier. When one of your monitors fails while Zapier has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - zapier

Ask before you retry

curl -s https://upbutler.com/status/zapier/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "zapier",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "Degraded performance",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Zapier down right now?: Partly. As of 2026-10-10 05:11 UTC, Zapier is degraded. This page reads the status again every 2 minutes.
Where does this status come from?: From Zapier's own status page API at https://status.zapier.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Zapier's words.
How can my agent or app check Zapier status?: Fetch https://upbutler.com/status/zapier/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"zapier"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Zapier's?: Add "zapier" to the dependencies of your UpButler workspace. When one of your monitors fails while Zapier has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Zapier. Status and incident text belong to Zapier and are read from their public status source; the probe result is UpButler's own measurement.