Live / Incidents / Zapier
Zapier: Zap History not displaying Zap runs
Zapier · zapier.comImpact: majorResolved2026-09-09 18:59 UTC
Public — what happened
Summary
The Engineering team has implemented a fix for this issue, and Zap runs continue to load into the Zap History.
Executions have not been affected: Zap runs are executing normally. However, the Zap run data was not rendering in the Zap history correctly.
We appreciate your patience while we worked through this, and we will share a final update once all Zap runs are displaying successfully.
If you have questions or need help, please contact our Support team at: zapier.com/get-help.
Timeline
- Started — 2026-09-09 17:51 UTC
- Last update — 2026-09-09 18:59 UTC
- Resolved — 2026-09-09 19:42 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zapier against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zapier: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zapier report →