Live / Incidents / Zapier
Zapier: Agent runs (agents.zapier.com) intermittently experiencing 429 errors
Zapier · zapier.comImpact: minorResolved2026-09-21 19:27 UTC
Public — what happened
Summary
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 issue in the future, implement better safeguards, and consolidate self-healing capabilities.
Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions.
For **Agents**, if you want to replay affected runs, go to your[ Agents dashboard](https://agents.zapier.com/bots), open the [All Activity](https://agents.zapier.com/activity) tab to view recent runs, an
Timeline
- Started — 2026-09-21 15:30 UTC
- Last update — 2026-09-21 19:27 UTC
- Resolved — 2026-09-21 19:27 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 →