If your Zaps connect to Salesforce Pardot, you likely saw connection errors and delayed or failed runs for 84 hours and 14 minutes starting at 10:50 UTC. Zapier says the fault sat upstream with Salesforce, not with its own platform.
Started
10:50 UTC
Duration
Lasted 3d 12h
Source
IsDown
Next time
Zapier is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Polling Triggers, Zaps
What happened?
Zapier's status page opened this incident at 10:50 UTC, reporting that some customers using the Salesforce Pardot integration were getting connection errors that stopped their Zaps running, while other Pardot connections kept working. By 12:06 UTC Zapier confirmed it was an upstream issue with the Pardot service itself and said it had no confirmed recovery time. Zapier also flagged it was checking whether any trigger activity had been missed during the disruption, and whether delayed or held runs would need extra attention once things recovered. At 16:19 UTC Zapier suggested reconnecting your Pardot account in Zapier as a possible fix, noting it had seen recovery for a small number of customers who had already done this, but had not confirmed it worked for everyone. That same advice, reconnect and wait, repeated through updates at 22:18, 14:00 and 19:43 UTC the next day, with Zapier saying each time that it was still working with Salesforce to identify the underlying cause. No update in this run names a root cause beyond "upstream issue with the Pardot service". Two components are listed as affected: Zaps and Polling Triggers. No user reports were filed in this window, so the only account of impact comes from Zapier's own six updates. The incident ran for 84 hours and 14 minutes before closing, well above the 3 hours 17 minutes median duration Zapier has posted across its last 25 incidents in 90 days. No post-mortem has been published explaining what Salesforce changed or fixed to end it.
Learning
This incident shows the shape of a dependency failure rather than a Zapier failure: the problem lived inside Salesforce Pardot, and Zapier's own infrastructure kept running, which is why the fix Zapier recommended was reconnecting your Pardot account rather than anything on Zapier's side. If you only watch your own endpoints, this kind of fault is invisible until your Zaps stop firing and you have to go looking for why. UptimeRobot's own 30 day figures for Zapier show 12 incidents with a median duration of 1 hour 51 minutes, a reminder that most Zapier incidents resolve far faster than this one did, so an 84 hour run is well outside the normal pattern and worth treating as an exception. Watching your own product tells you your half is healthy, it says nothing about whether the integration you depend on is degraded somewhere upstream. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.