Operational Zapier status
zapier.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Zapier problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 61 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Agent runs (agents.zapier.com) intermittently experiencing 429 errors”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Zapier's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Zapier. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Zapier, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Zapier may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Zapier. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Agent runs (agents.zapier.com) intermittently experiencing 429 errors
minor resolved · started · resolved
3 updates
- investigating
Our team is currently investigating an issue with Agent runs (from agents.zapier.com) intermittently experiencing 429 errors for some customers. We're working to confirm the root cause and implement a fix as soon as possible. AI by Zapier runs are not affected by this incident. If you have any questions or need help, please reach out to our Support team at zapier.com/get-help.
- identified
The team has identified the issue to be an intermittent overload of a service powering: • Agent runs (agents.zapier.com) • AI by Zapier executions As a result, some agent runs and AI by Zapier executions hit 429 errors. We will be working on replaying affected agent runs or Zap runs where possible, and we'll keep this status page updated on our progress. Many thanks for your patience. Our Support team is available if you have any questions, and you can reach them at: zapier.com/get-help.
- resolved
The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC. Our team continues to work with our service provider to prevent this issue in the future, implement better safeguards, and consolidate self-healing capabilities. Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions. For **Agents**, if you want to replay affected runs, go to your[ Agents dashboard](https://agents.zapier.com/bots), open the [All Activity](https://agents.zapier.com/activity) tab to view recent runs, and review the agent runs during the incident window. You can replay any runs that need to be reprocessed by prompting the agent in the chat to retry. For Zap runs using **AI by Zapier**, **no action needed
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.