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 | 40 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 “Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters”. 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
Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters
minor resolved · started · resolved
3 updates
- identified
We've identified an issue where some requests made through Custom Actions in Zaps or Zapier MCP include duplicated query parameters. Because of this, some customers may see errors even when their inputs are valid. Not every app or request is affected, since many apps handle duplicate query parameters without issue. Standard app actions for connected apps that run in Zaps are not affected. We'll update this page as soon as we have more information. If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
- monitoring
A fix has been deployed that stops Custom Actions and Zapier MCP requests from sending duplicated query parameters. Error rates on affected requests dropped to normal immediately after deployment (~09:40 UTC). Not every request failed during the issue, and we have not identified evidence of data loss. If a connected app behaved unexpectedly during this window, please reach out so we can take a closer look. We’re continuing to monitor and will post a final update within 24 hours. If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
- resolved
The issue causing duplicated query parameters on some Custom Actions and Zapier MCP requests has been resolved. Starting October 7, a deploy caused some outbound requests to include duplicate query parameters, which a subset of connected apps rejected even when inputs were valid. Not every request was affected, and standard app actions in Zaps were not impacted. A fix was deployed on October 12 at 09:40 UTC to remove the duplicated parameters, and error rates returned to normal immediately. We’ve been monitoring since and have not identified any further impact or evidence of data loss. We’re reviewing the change that introduced this to prevent similar issues going forward. If you experienced errors during this window and still need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
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.