Live  /  Zapier  /  Incident

Zapier: Zap History not displaying Zap runs

Zapier · zapier.comMajor incidentResolved2026-09-09 18:59 UTC
Public — what happened

Summary

Zapier reported a major issue starting on 2026-09-09 at 17:51 UTC in which records of Zap runs were not showing up properly in users' Zap History. The company said the Zaps themselves kept running as normal, and only the display of their run data was affected. Zapier said its engineers put a fix in place and run records were loading into the history again, with the incident marked resolved at 19:42. The company said it was still monitoring and planned a final update once every run appears correctly.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 →

More from Zapier

Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.

The full archive is on the Zapier status & history page.

Related: Zapier status & history. SquidGrid is not affiliated with Zapier.