If you signed into Zapier with Facebook or Microsoft SSO on 5 October, you likely hit a blank screen right after authenticating. The fault sat on Zapier's side and lasted 54 minutes before a fix went out.
Started
18:54 UTC
Duration
Lasted 54m
Source
IsDown
Next time
Zapier is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Website, Login
What happened?
Zapier logged one incident on 5 October, starting at 18:54 UTC and running for 54 minutes. It hit the Website and Login components. The problem was specific: users signing into Zapier.com using Facebook or Microsoft Single Sign-On got a blank page after authentication completed. Zapier's own first update is precise about the mechanics, noting that login authentication itself succeeded, and that the page could be reached by a hard refresh or by opening a new tab. That detail matters because it tells you the failure was in how the page rendered post-login, not in the SSO handshake itself. At 19:42 UTC, Zapier's engineering team said it had identified the issue and released a fix, and moved to monitoring for any knock-on problems. No further update was filed after that, and the incident is marked closed at 54 minutes. There are no user reports logged in the window, so what's known comes entirely from Zapier's own two updates. Zapier has not published a post-mortem explaining what caused the blank page in the first place, so the underlying cause is not on the record. Over the past 90 days Zapier has logged 23 incidents with a median duration of 3 hours 9 minutes, which makes this one comparatively short.
Learning
This incident is a good example of a failure that would not show up in a basic uptime check on Zapier.com, because the site itself was reachable and even a hard refresh or new tab would load the page fine. The break was narrower than that: a specific login path, Facebook or Microsoft SSO, that left the page blank immediately after a successful authentication. A generic ping or homepage check would have stayed green the whole time, correctly, because the homepage was not broken. Only someone actually walking through that SSO login flow would have seen the blank screen Zapier described. This is the general shape of a lot of login-layer failures: the front door is open, but one specific hallway inside is blocked. Your own monitoring tells you your product is up and reachable, but it can't tell you whether a third party's login flow is quietly failing behind the scenes. UptimeRobot watching Zapier's status and incident history fills that gap, so you know which side of the connection broke instead of guessing.
