← Back to Zapier's check readings
We started checking Zapier on August 20, 2026, which is 54 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Zapier reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Zapier's own status page declared. Below it, any public chatter we saw about Zapier and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Zapier's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Zapier in the last 24 hours, which is not evidence that nothing is wrong.
Zapier's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Zapier's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Zapier next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Zapier's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by GoogleOngoing, all systems operational
Oct 9, 2026, 5:07 PM UTC, open for 2d 3h so faridentified
their latest update (Oct 10, 2026, 3:50 AM UTC): We've completed the initial cleanup and are now collaborating with the Google team to determine the next steps needed to clear the "dangerous site" flag on our file storage domain.
During this period, your files that passed through Zapier remain safe, and Zaps, Tables, and Forms…
Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.Partial outage
Oct 5, 2026, 6:54 PM UTC to Oct 5, 2026, 7:46 PM UTC (51 min)resolved
their latest update (Oct 5, 2026, 7:46 PM UTC): 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 …
Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)Minor incident
Sep 28, 2026, 12:13 PM UTC to Sep 28, 2026, 1:18 PM UTC (1h 5m)resolved
their latest update (Sep 28, 2026, 1:18 PM UTC): This has been fully resolved. If you still face this issue, please reach out to our support team via the [Get help and support with Zapie](https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapier "Get help and support with Zapie")r channels
Agent runs (agents.zapier.com) intermittently experiencing 429 errorsMinor incident
Sep 21, 2026, 3:30 PM UTC to Sep 21, 2026, 7:27 PM UTC (3h 58m)resolved
their latest update (Sep 21, 2026, 7:27 PM UTC): The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC.
Our team continues to work with our service provider to prevent this iss…
Zap History not displaying Zap runsPartial outage
Sep 9, 2026, 5:51 PM UTC to Sep 9, 2026, 7:41 PM UTC (1h 50m)resolved
their latest update (Sep 9, 2026, 7:41 PM UTC): We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now.
If you have questions or need help, please contact our Support team at: [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help").
Webhook Triggers and Zap Actions - Service DisruptionMinor incident
Sep 8, 2026, 2:06 PM UTC to Sep 8, 2026, 5:08 PM UTC (3h 2m)resolved
their latest update (Sep 8, 2026, 5:08 PM UTC): 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://…
Freshservice - Webhook delivery disruptionAll systems operational
Sep 1, 2026, 12:03 PM UTC to Sep 7, 2026, 12:44 PM UTC (6d 0h)resolved
their latest update (Sep 7, 2026, 12:44 PM UTC): Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes.
If you experience ongoing issues, contact Support by clicking above or go to: […
Tables, Chatbots, and Forms not loading for some customersMinor incident
Aug 28, 2026, 2:35 PM UTC to Aug 28, 2026, 3:35 PM UTC (1h 1m)resolved
their latest update (Aug 28, 2026, 3:35 PM UTC): The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC.
Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead.
All affected surfaces — Tables, Forms, Chatbots, and folder/subfol…
Intermittent instant trigger failuresMinor incident
Aug 26, 2026, 4:55 PM UTC to Aug 26, 2026, 9:41 PM UTC (4h 46m)resolved
their latest update (Aug 26, 2026, 9:41 PM UTC): 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-…
403 errors when trying to connect or reconnect to ActiveCampaignAll systems operational
Aug 21, 2026, 11:48 PM UTC to Aug 22, 2026, 2:19 AM UTC (2h 31m)resolved
their latest update (Aug 22, 2026, 2:19 AM UTC): The issue with ActiveCampaign app connections and runs returning a 403 error has been fully resolved. Authentication and integration are functioning normally again.
Impacted runs during the incident period have been replayed successfully.
If you're experiencing any issues, plea…
Showing the 10 most recent of 36 incidents Zapier has declared in the history we hold.
These entries are Zapier's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Zapier's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.