Live / Incidents / Zapier
Zapier: Webhook Triggers and Zap Actions - Service Disruption
Zapier · zapier.comImpact: minorResolved2026-09-08 14:06 UTC
Public — what happened
Summary
A brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail.
The issue has been resolved, and Zap Runs are processing normally.
We're reviewing affected accounts and replaying missed webhook events where possible.
If you notice a Zap that should have run during this window and did not, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")
Timeline
- Started — 2026-09-08 14:06 UTC
- Last update — 2026-09-08 14:06 UTC
- Resolved — 2026-09-08 17:09 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zapier against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zapier: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zapier report →