Live

Connection errors affecting Salesforce Pardot Zaps

This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesforce has remediated their side, but affected connections need to be reconnected. We've deployed a fix on our side so that affected connections now show as expired. To restore your connection, reconnect your Salesforce Pardot account in Zapier. Some Zaps may have been delayed or held, and we're checking that they resume after reconnecting. If your Zaps are still failing after reconnecting, or you need help, please contact our support team: [ https://zapier.com/app/get-help](https://zapier.com/app/get-help " https://zapier.com/app/get-help")

The latest update from Zapier.

State

Resolved

Started

Lasted

4 days

Worst impact

Partial outage

Timeline

7 updates
Oct 23Oct 24Oct 25Oct 26Oct 26
Partial outageUpdate postedDates in UTC

Investigating

4 days 100%

Updates

Times in UTC

As posted by Zapier

Resolved

This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesforce has remediated their side, but affected connections need to be reconnected. We've deployed a fix on our side so that affected connections now show as expired. To restore your connection, reconnect your Salesforce Pardot account in Zapier. Some Zaps may have been delayed or held, and we're checking that they resume after reconnecting. If your Zaps are still failing after reconnecting, or you need help, please contact our support team: [ https://zapier.com/app/get-help](https://zapier.com/app/get-help " https://zapier.com/app/get-help")

Investigating

We're continuing to investigate the Salesforce Pardot connection errors and are working with Salesforce to identify the underlying cause. If you have a Zap that uses the Pardot integration and Zap runs are failing due to a Pardot action or integration, try reconnecting your Salesforce Pardot account in Zapier. Reconnecting has helped some customers restore their connections and may resolve the errors, but we have not confirmed that it works for everyone affected. If errors persist after reconnecting, or you need help, please [contact our support team](https://zapier.com/app/get-help "contact our support team").

Investigating

Some Salesforce Pardot Zaps continue to experience connection errors, preventing them from running or delaying workflows. We are continuing to work with our partner, Salesforce, to obtain full confirmation of the underlying issue and the steps needed for recovery. If you are affected, try reconnecting your Salesforce Pardot account in Zapier. Reconnecting has helped some customers restore their connections and may resolve the errors, but we have not confirmed that it works for everyone affected. If errors persist after reconnecting, or you need help, please [contact our support team](https://zapier.com/app/get-help "contact our support team"). We do not yet have a confirmed recovery time.

Investigating

We're continuing to investigate the Salesforce Pardot connection errors and are working with Salesforce to identify the underlying cause. Reconnecting your Pardot account in Zapier may resolve the errors. We've seen recovery for a small number of customers who reconnected, but we haven't confirmed that this works for everyone affected. If you're still seeing errors after reconnecting, or you need help, please [contact our support team.](https://zapier.com/app/get-help "contact our support team.") Thank you for your patience, and we'll share another update as soon as we have more information.

Investigating

Reconnecting your Salesforce Pardot account in Zapier may resolve the connection errors. We have observed recovery for a small number of customers who appear to have reconnected their accounts, but have not yet confirmed that this works for everyone affected. If you are still experiencing errors, try reconnecting your Pardot account. If errors persist or you need help, please [contact our support team](https://zapier.com/app/get-help "contact our support team"). We are continuing to work with Salesforce on the underlying issue.

Investigating

We have confirmed that this is an upstream issue with the Pardot service and are monitoring its status. There is no confirmed recovery time yet. We are assessing whether any trigger activity was missed during the disruption and whether additional recovery steps will be needed. Once connections recover, we will verify that affected Zaps resume and check whether delayed or held runs need additional attention. We will let you know if any action is required from your team. If you need assistance in the meantime, please [contact our support team](https://zapier.com/app/get-help "contact our support team").

Investigating

Some customers using the Salesforce Pardot integration are experiencing connection errors that prevent their Zaps from running. Other Pardot connections continue to run normally. We are investigating the ongoing errors and checking recovery of affected connections and delayed Zap runs. If you need any assistance in the meantime, please contact our support team [here](https://zapier.com/app/get-help "here").

Zapier in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

25

Days with an incident

36

Median duration

3 h 2 min

This incident

28× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 3 h 2 min
90 days agoToday

Other Zapier incidents

All incidents

Zapier·"Chat with Sales" page not loading

We have tested the page post-fix and the issue is resolved. Users visiting the "Chat with Sales" page ( ) should now be able to see the chat session. This incident is now considered resolved. If you don't see the chat, we recommend clearing your browser cache and cookies, then trying the page again. If you continue to have issues with the page, reach out to our support team at [zapier.com/app/get-help](http://zapier.com/app/get-help).

Resolved

Zapier·Discord integration issues

Discord requests made through [Zapier's Proxy API](https://docs.zapier.com/proxy-api/overview) — where Zapier adds the credentials for a connected Discord account on behalf of your code or an agent (for example via the Zapier SDK, Code by Zapier, Custom Actions, MCP code actions, or Sidekick) — have been disabled and will no longer be available. Affected requests return a `401 Unauthorized` error. This does not affect Zapier's native Discord integration — standard Discord triggers and actions continue to work as normal. Code steps that call Discord with a token you supply yourself (rather than a connected Discord account) are also unaffected. If you were making direct Discord requests this way, you can switch to Zapier's [native Discord integration](https://zapier.com/apps/discord/integrations). If you need help, reach out at .

Resolved

Zapier·Security updates in progress for third-party software components

We have not identified any customer impact or evidence of exploitation. We have completed the priority security updates and mitigations, and are closing this incident. Remaining lower-risk updates, including updates managed by our providers, will continue as follow-up work. No action is needed on your part.

Resolved

Zapier·Assessment of recently reported PHP vulnerabilities

Our investigation into the reported PHP vulnerabilities is complete. We found no impact on Zapier services or customer data. This advisory is now closed. **Security FAQ: PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619)** > **1. What is this issue?** > Two vulnerabilities were disclosed in PHP, an open-source programming language. Both can lead to remote code execution under certain conditions. They affect PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, and 8.5 before 8.5.12. > > **2. Is Zapier affected?** > Our investigation is complete, and we found no impact on Zapier services or customer data. > > **3. Has customer data been affected?** > No. Our investigation found no impact to customer data. > > **4. Does this affect the Zapier WordPress integration for example?** > The Zapier WordPress plugin itself is not vulnerable. WordPress sites run on PHP, though, so site owners should make sure their PHP version is patched (see question 1 for the affected versions). >

Resolved

Zapier·Delayed real-time updates in Zapier Tables

The issue affecting real-time updates in Zapier Tables has been resolved. Collaborator changes and refreshed formula results should now appear normally. If you continue to experience issues, please contact our [support team](https://zapier.com/app/get-help "support team").

Resolved

Follow Zapier

Your coding agent knows when Zapier is down, and tells you when a failure is theirs, not yours. You can also get Zapier incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zapier" and tell me if Zapier has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=zapier
Slack
/feed subscribe https://outages.live/feed.xml?providers=zapier

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane