CHYP.ai · ORBIT // Cloudy_Day Security Suite

Productivity & files

Operational Zapier status

zapier.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Zapier problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started29 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Connection errors affecting Salesforce Pardot Zaps”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside Zapier's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

We don't map other services that depend on Zapier. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Zapier, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Zapier may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Zapier. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Connection errors affecting Salesforce Pardot Zaps

major resolved · started · resolved

7 updates

  1. 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").

  2. 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").

  3. 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.

  4. 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.

  5. 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.

  6. 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").

  7. 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")

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next