Live / Zapier / Incident
Zapier: Connection errors affecting Salesforce Pardot Zaps
Zapier · zapier.comMajor incidentResolved2026-10-26 23:02 UTC
Public — what happened
Summary
Zapier said some customers using its Salesforce Pardot integration saw connection errors that stopped their Zaps from running or delayed them, while other Pardot connections worked normally. The problem began on October 23, and about an hour later Zapier said it had confirmed the trouble was on the Pardot service's side and gave no recovery time. Over the following days Zapier said it was working with Salesforce to pin down the underlying issue, and it suggested that affected users reconnect their Pardot account, which had helped some but not all. The incident was marked resolved on October 26 at 23:02 UTC.
Timeline
- Started — 2026-10-23 10:50 UTC
- Investigating — 2026-10-23 10:50 UTC (6 updates)
- Resolved — 2026-10-26 23:02 UTC · 4 days after it started
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 →
More from Zapier
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.