- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 51m it lasted.
Anything that failed between 2026-10-05 18:54 UTC and 2026-10-05 19:46 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.
Root cause
We are investigating the issue and will give another update as soon as we find the cause.Read the postmortem
Updates from Zapier 3
- investigating
Our Engineering team is aware of an issue affecting users who sign into [Zapier.com](http://Zapier.com "Zapier.com") using Facebook or Microsoft Single Sign-On (SSO). Users logging into Zapier with these services will see a blank screen after authenticating. The login authentication is successful; however, the page can be accessed after a hard refresh or by opening a new tab. We are investigating the issue and will give another update as soon as we find the cause.
provider
- monitoring
Our Engineering team has identified the issue and has released a fix. We're now monitoring our systems to see if there are any other problems that could result from the fix.
provider
- resolved
The issue is now considered resolved, with both Facebook and Microsoft single sign-on working as expected. If you find yourself still unable to log in, please reach out to our Support team at [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help") Thank you for your patience as we worked to resolve the issue.
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-1481f11ef8
Is Zapier still down?
No, this incident was resolved 2026-10-05 19:46 UTC. For Zapier's live state, see https://down.guide/zapier.
How long did it last?
51m, from 2026-10-05 18:54 UTC to 2026-10-05 19:46 UTC, by the times Zapier posted.
What caused it?
Zapier wrote: "We are investigating the issue and will give another update as soon as we find the cause." The postmortem: https://status.zapier.com/incidents/01M46PNZQTBTNRCQVW1WZ8846V
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.