Live

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

The latest update from Zapier.

State

Resolved

Started

Lasted

25 h 1 min

Worst impact

Notice

Timeline

4 updates
15:2121:3603:5210:0716:22
NoticeUpdate postedTimes in UTC

Investigating

31 min 2%

Identified

24 h 31 min 98%

Updates

Times in UTC

As posted by Zapier

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

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](https://zapier.com/app/get-help "here").

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](https://zapier.com/app/get-help "support team") if you need any help in the meantime.

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

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

8.3× 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·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")

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

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.cc/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.cc/feed.xml?providers=zapier
Slack
/feed subscribe https://outages.cc/feed.xml?providers=zapier

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane