Is Zapier down?

Last checked 1m ago
Current status
Zapier is up

No incidents right now.

  • Official status page: status.zapier.com
  • Checked every 5 minutes
  • 18 components tracked

Zapier is operational right now. Last checked 1m ago; the most recent incident resolved 2d ago.

Real-time Zapier status, recent outages, and incident history: pulled directly from Zapier's official status page at status.zapier.com every 5 minutes. Pingoru tracks 18 Zapier services and has captured 27 incidents in the last 90 days (97.90% uptime). Get email, Slack, Discord, or webhook alerts the moment Zapier reports a new incident, free for 3 monitors, no credit card.

Users who monitor Zapier also follow these No-Code services: Airtable Webflow Typeform IFTTT Vasion Bubble Skylight Coda DoorDash AnyDesk View all 8,000+ providers
Zapier uptime 97.90% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 39m
    Started Oct 29, 2026, 04:13 PM UTC · Resolved Oct 29, 2026, 06:53 PM UTC
    Timeline · 2 updates
    • investigating · Oct 29, 2026, 04:13 PM UTC

      Status: Investigating Some customers may experience failures when making Discord requests through SDK-based flows and Custom Actions. We’re investigating and may temporarily disable these requests to mitigate the issue; the Discord integration itself is not expected to be affected.

    • resolved · Oct 29, 2026, 06:53 PM UTC

      Status: Resolved 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 https://zapier.com/app/get-help.

    Latest: Status: Resolved 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…

  2. Resolved 3d 12h
    Started Oct 23, 2026, 10:50 AM UTC · Resolved Oct 26, 2026, 11:02 PM UTC
    Polling Triggers
    Timeline · 7 updates
    • investigating · Oct 23, 2026, 10:50 AM UTC

      Status: 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 "here": https://zapier.com/app/get-help. Affected components Polling Triggers (Partial outage)

    • investigating · Oct 23, 2026, 12:06 PM UTC

      Status: 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 "contact our support team": https://zapier.com/app/get-help. Affected components Polling Triggers (Partial outage)

    • investigating · Oct 23, 2026, 04:19 PM UTC

      Status: 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 "contact our support team": https://zapier.com/app/get-help. We are continuing to work with Salesforce on the underlying issue. Affected components Polling Triggers (Partial outage)

    • investigating · Oct 23, 2026, 10:18 PM UTC

      Status: 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. "contact our support team.": https://zapier.com/app/get-help Thank you for your patience, and we'll share another update as soon as we have more information. Affected components Polling Triggers (Partial outage)

    • investigating · Oct 24, 2026, 02:00 PM UTC

      Status: 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 "contact our support team": https://zapier.com/app/get-help. We do not yet have a confirmed recovery time. Affected components Polling Triggers (Partial outage)

    • investigating · Oct 26, 2026, 07:43 PM UTC

      Status: 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 "contact our support team": https://zapier.com/app/get-help. Affected components Polling Triggers (Partial outage)

    • resolved · Oct 26, 2026, 11:02 PM UTC

      Status: 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 Affected components Polling Triggers (Operational)

    Latest: Status: Resolved This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesf…

  3. Resolved 4d 19h
    Started Oct 22, 2026, 03:29 PM UTC · Resolved Oct 27, 2026, 10:56 AM UTC
    Timeline · 4 updates
    • investigating · Oct 22, 2026, 03:29 PM UTC

      Status: Investigating We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We have not identified any customer impact or evidence of exploitation, and no action is needed on your part. Some updates are rolling out now, so you may see brief latency to API by Zapier and Webhooks by Zapier while they complete. Zap workflows are expected to keep running normally, and we don't expect any data loss.

    • investigating · Oct 22, 2026, 07:21 PM UTC

      Status: Investigating We’re continuing to roll out the security updates and are monitoring the deployment closely. We have not identified any customer impact or evidence of exploitation. You may continue to see brief workflow latency while updates complete. We'll continue to keep you up to date as we make progress

    • identified · Oct 23, 2026, 05:33 PM UTC

      Status: Identified We've made good progress rolling out the security updates and are continuing to work through the remaining components while monitoring closely. We have not identified any customer impact or evidence of exploitation. We'll continue to keep you up to date as we make progress.

    • resolved · Oct 27, 2026, 10:56 AM UTC

      Status: Resolved 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.

    Latest: Status: Resolved We have not identified any customer impact or evidence of exploitation. We have completed the priority security updates and mitigations, and are closing this incid…

  4. Resolved 44m
    Started Oct 22, 2026, 02:02 PM UTC · Resolved Oct 22, 2026, 02:46 PM UTC
    Timeline · 2 updates
    • investigating · Oct 22, 2026, 02:02 PM UTC

      Status: Investigating We have not identified customer impact related to the PHP vulnerabilities reported on October 21, 2026. Our security and engineering teams are reviewing potential exposure in NodeJS services and across Zapier. The assessment is ongoing. We will share further findings here as they are confirmed. Please reach out to our Support team "Support team": https://zapier.com/app/get-help if you need any help in the meantime.

    • resolved · Oct 22, 2026, 02:46 PM UTC

      Status: Resolved 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). 5. Could PHP applications I host be affected? Possibly. Applications you run yourself, including on third-party hosting platforms, may be vulnerable if they run an affected PHP version, regardless of Zapier. We recommend updating to a patched PHP version. "

    Latest: Status: Resolved 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 …

  5. Resolved 1d 1h
    Started Oct 21, 2026, 03:21 PM UTC · Resolved Oct 22, 2026, 04:22 PM UTC
    Timeline · 4 updates
    • investigating · Oct 21, 2026, 03:21 PM UTC

      Status: Investigating Some customers may see delayed or missing real-time updates in Zapier Tables, including changes made by collaborators and refreshed formula results. Tables remains available, and underlying formula calculations and triggers continue to run. We are investigating a disruption affecting delivery of these updates and assessing the scope of customer impact. If you need any assistance in the meantime, please reach out to our support team "support team": https://zapier.com/app/get-help.

    • identified · Oct 21, 2026, 03:52 PM UTC

      Status: Identified We have identified an issue with an upstream service provider that is affecting real-time updates in Zapier Tables. Some customers may continue to see delayed or missing collaborator changes and refreshed formula results. Tables remains available, and underlying formula calculations and triggers continue to run. We are monitoring the provider’s recovery and assessing customer impact. We do not yet have an estimated resolution time. Please reach out to our support team "support team": https://zapier.com/app/get-help if you need any help in the meantime.

    • identified · Oct 21, 2026, 04:04 PM UTC

      Status: Identified We continue to await recovery from an issue affecting our upstream service provider. Real-time updates in Zapier Tables may still be delayed or missing, including collaborator changes and refreshed formula results. Tables remains available, and underlying formula calculations and triggers continue to run. We are watching for improvements, but do not yet have an estimated resolution time. For any assistance in the meantime, please reach out to our support team here "here": https://zapier.com/app/get-help.

    • resolved · Oct 22, 2026, 04:22 PM UTC

      Status: Resolved 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 "support team": https://zapier.com/app/get-help.

    Latest: Status: Resolved The issue affecting real-time updates in Zapier Tables has been resolved. Collaborator changes and refreshed formula results should now appear normally. If you con…

See the full Zapier outage history

21 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Zapier outage history →

Or sign up free to get alerts when Zapier breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · incident.io · 18 components checked every 5 minutes
143incidents recorded
143last 12 months
26last 90 days
11 hourstypical duration, 12 months

The longest incident in the last year, Facebook Lead Ads intermittently missing leads on June 18, 2026, ran for 8 days. 11 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Agents11
  • Website9
  • Chatbots6
  • Instant Triggers6
  • MCP4

Latest incidents

  • Discord integration issues October 29, 2026 · 3 hours · degraded service

    Status: Investigating Some customers may experience failures when making Discord requests through SDK-based flows and Custom Actions. We’re investigating and…

  • Connection errors affecting Salesforce Pardot Zaps October 23, 2026 · 4 days · degraded service

    Status: Investigating Some customers using the Salesforce Pardot integration are experiencing connection errors that prevent their Zaps from running. Other…

  • Security updates in progress for third-party software components October 22, 2026 · 5 days · degraded service

    Status: Investigating We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We…

Outage history

Past 90 days · 26 incidents View full outage history →