- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on Zapier. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4h 46m it lasted.
Anything that failed between 2026-08-26 16:55 UTC and 2026-08-26 21:41 UTC may need a replay.Subscribe to Zapier's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Zapier 4
- investigating
Some customers may experience intermittent delays or failures with instant triggers, which can prevent workflows from starting. We are investigating the issue and working to restore normal processing. We will provide updates as soon as possible.
provider
- investigating
We're continuing to investigate a small number of workflows that failed to start between approximately 9:00–9:20 AM UTC on August 25. Affected triggers did not fire during this window. No data has been lost — failed triggers can be replayed once the issue is resolved. Our team is actively working to determine the root cause. We'll provide another update as soon as possible. If you need help: [ https://zapier.com/app/get-help](https://zapier.com/app/get-help " https://zapier.com/app/get-help")
provider
- monitoring
A fix has been implemented and we are monitoring the results. We have not seen any new instant trigger failures since approximately 10:26 AM PDT (17:26 UTC). The change we deployed adds automatic retries for the failure that was preventing a small number of triggers from firing, and we are continuing to roll it out fully. No data has been lost. We have confirmed that affected triggers replay successfully, and we are now replaying the triggers that failed during this incident. Our team is monitoring closely to confirm the issue is fully resolved. If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thank you for your patience.
provider
- resolved
Instant trigger processing has returned to normal. We have successfully replayed the affected triggers and continue not to see any impacted Zap runs, so the incident is now resolved. If you have any questions, please reach out to our support team: [[https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")]([https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help"))
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c09cccd353
Is Zapier still down?
No, this incident was resolved 2026-08-26 21:41 UTC. For Zapier's live state, see https://down.guide/zapier.
How long did it last?
4h 46m, from 2026-08-26 16:55 UTC to 2026-08-26 21:41 UTC, by the times Zapier posted.
What caused it?
Zapier hasn't published a root cause. If it does, it shows here.
Where does this come from?
Zapier's official status page, https://status.zapier.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.