Live  /  Zapier  /  Incident

Zapier: Agent runs (agents.zapier.com) intermittently experiencing 429 errors

Zapier · zapier.comMinor incidentResolved2026-09-21 19:27 UTC
Public — what happened

Summary

Zapier reported that some Agent runs on agents.zapier.com, along with Zap runs that use AI by Zapier, were intermittently failing with 429 errors, and it rated the problem as minor. The company said the confirmed impact ran from September 18, 2026 at 2:00am UTC until 15:00 UTC on September 21, and it marked the issue resolved later that day at 19:27. Zapier said it had already re-run all affected AI by Zapier jobs, but some Agent runs from September 18 to 20 were not replayed to avoid running them twice, so users can retry those by asking the agent in chat. The company said it is working with a service provider to add safeguards against a repeat, without naming a specific cause.

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 40, 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.