Zapier did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-12 20:00 UTC. This page shows the end time when Zapier marks it resolved.

How do I get alerts for Zapier?

Subscribe to the Zapier live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Zapier. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

ZapierIncident ·

Password reset and Verified Device Sign-In Emails are delayed

Q: What happened?

Zapier reported "Password reset and Verified Device Sign-In Emails are delayed" on its status page at 2026-11-12 20:00 UTC. Zapier reports delayed or missing password reset emails and Verified Device sign-in emails. Zapier identified the problem and the mail provider has applied a fix. Zapier continues to monitor the issue.

NoticeOfficial update

Zapier reports delayed or missing password reset emails and Verified Device sign-in emails. Zapier identified the problem and the mail provider has applied a fix. Zapier continues to monitor the issue.

State

Identified

Started

Ongoing for

54 min

Worst impact

Notice

Timeline

1 update

20:0020:1420:2720:4120:54

NoticeUpdate postedTimes in UTC

Identified

54 min 100%

Updates

Times in UTC

As posted by Zapier

Identified

We’ve received customer reports that password reset emails and Verified Device sign-in emails are delayed or not being received. Our mail provider is currently working through an issue and has implemented a fix. We continue to monitor for any additional issues and will update you as progress is made.

Zapier in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

3 h 2 min

This incident

70% shorter than 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 temporarily unavailable

Zapier reports that visitors to zapier.com could not start a chat with the Sales team. Zapier says the issue is resolved, and it lasted about 3 hours and 29 minutes. During the outage, Zapier said users could contact the Support team.

Resolved

Zapier·Delayed or failed template recommendations and template setup

Zapier reported that template recommendations on the Zapier homepage and template setup did not work for some users. Zapier later stated that the issue is resolved. The incident lasted about 37 minutes.

Resolved

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

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