# Webhook Triggers and Zap Actions - Service Disruption

- Provider: [Zapier](https://down.guide/providers/zapier)
- Confidence: Confirmed
- Impact: Degraded
- lasted 3h 2m
- started 2026-09-08 14:06 UTC
- Zapier states the impact was 2026-09-08 12:15 to 13:50 UTC (1h 35m)
- id: DWN-fbc66fd142
- Official page: https://status.zapier.com/incidents/01M20NFAB8480D5PJP43DC2Z0F

## Updates from Zapier
### 2026-09-08 14:06 UTC: monitoring
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")

### 2026-09-08 17:08 UTC: resolved
The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved.
If you're still seeing issues with a Zap that should have run during this window, contact Support: \[zapier.com/app/get-help\](http://zapier.com/app/get-help "zapier.com/app/get-help")

From the builder: does your app depend on Zapier? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=zapier) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Zapier.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-fbc66fd142), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.