Zapier Status

Jul 5, 2025

No incidents reported today.

Jul 4, 2025

No incidents reported.

Jul 3, 2025

Users Unable To Publish Drafts – Timeout / Network Error

Resolved - This incident has been resolved.
Jul 3, 11:42 PDT

Monitoring - We have implemented a temporary fix to mitigate these errors on accounts. We hope to have a permanent fix in place shortly.

If you are still experiencing these errors when trying to publish Zap Drafts, please reach out to Zapier Support: https://zapier.com/app/get-help
Jul 2, 15:37 PDT

Identified - We're currently investigating an issue where some users are encountering timeout or network errors when attempting to publish their Zaps.

Initial findings suggest the issue is related to a gateway timeout between internal services, which may be preventing draft Zaps from saving or publishing successfully.

This appears to impact a limited number of users and Zaps, but we're continuing to investigate the root cause and monitor for further reports.

We'll share an update as soon as we have more information or mitigation steps.
Jul 2, 08:36 PDT

Jul 2, 2025

Increased number of 503 errors with Google Ads actions

Resolved - This incident has been resolved. Google has confirmed that they had resolved the issue with Google Ads based on their their Status Page here: https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu.

Our team will be replaying the errored Zap runs related to this incident. No actions is required from customers at this time.

If you continue to encounter any issues related to this, kindly reach out to our Support Channel (https://zapier.com/app/get-help). Thank you.
Jul 2, 23:33 PDT

Identified - Google Ads has confirmed that they are currently investigating an issue with the Google Ads platform. You can find more updates here:
https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu
Jul 2, 16:49 PDT

Investigating - We are currently investing reports of an increase in 503 errors from actions within the Google Ads integration ( such as then Send Offline Conversion, Create Customer List, and Set Campaign List actions).

We will update here once we have more information
Jul 2, 15:50 PDT

Zaps using instant triggers aren't triggering

Resolved - This incident has been resolved.

We are working to better understand the root cause and will provide any necessary updates.

All missed triggers that were replayable have been replayed.

Thank you for your patience.
Jul 2, 08:51 PDT

Investigating - We have identified an issue affecting Zaps that use instant triggers.

A small number of hooks were not processed correctly, which caused some Zaps to not trigger.

We're currently investigating the cause and working on how to mitigate the impacts.
Jul 2, 04:00 PDT

Jul 1, 2025

502 Errors Impacting zapier.com Access and Zap Execution Affected

Resolved - All systems are now fully operational.

Our team has verified that:
Instant triggers and polling have returned to normal.
No data loss has been detected.
Affected Zaps using instant triggers were replayed where possible.
Some users may have Zap runs stuck in a “playing” or “waiting” status. We recommend reviewing your Zap History and replaying those entire runs if needed.

Learn more: https://zapier.com/help/manage/history/replay-failed-zap-runs

Editor drafts created during the outage may not have saved as expected.

We appreciate your patience while we worked through this issue. If you continue to see problems, please contact our support team.
Jul 1, 03:03 PDT

Update - We are continuing to monitor the results of our recent fix. However, users might see Zap runs that are not in a "success" or "filtered" status; they may be in statuses like "playing" or "waiting" instead. We recommend reviewing affected Zap runs and replaying those runs in full to resolve the issues. You can learn more about how to replay entire Zap runs here: https://zapier.com/help/manage/history/replay-failed-zap-runs

We will continue to update the status page with more information as it becomes available. Thank you for your continued patience.
Jun 30, 15:23 PDT

Monitoring - At approximately 12:32 PM ET, we began experiencing an issue that affected access to zapier.com and Zap execution. As of 1:30 PM ET, the site is accessible again.

Our engineering team is currently reviewing and processing Zaps that were triggered during the incident window. As a result, some users may notice temporary latency in Zap execution for that time period. Additionally, Zap Editor drafts that were created or edited during the incident window may not have been saved as expected. We’re closely monitoring progress.
Jun 30, 11:19 PDT

Investigating - We’re currently investigating an issue resulting in 502 errors across the Zapier platform. This is affecting homepage site access.

Our team is actively working to resolve the issue and restore full functionality. We’ll provide updates as they become available.

Thank you for your patience.
Jun 30, 10:04 PDT

Jun 30, 2025

Users attempting to access the Interfaces page are encountering a 500 Internal Server Error.

Resolved - The incident regarding the Interfaces homepage failing to load has been resolved. The issue causing the 500 Internal Server Error has been identified and fixed by our engineering team and access to the Interfaces page should now be restored.

We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve this issue.
Jun 30, 14:15 PDT

Investigating - We are currently investigating an issue where requests to the Interfaces page are resulting in 500 errors. This may prevent customers from viewing or interacting with their Interfaces. Our engineering team is actively working to identify the root cause and restore full functionality.
Jun 30, 12:47 PDT

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025

No incidents reported.

Jun 25, 2025

Delays to live runs showing in the Zap run history page.

Resolved - Our Engineering team has applied a fix and Zap History page is no longer facing delays.

During the affected period, there wasn't any data loss and everything should be working as expected now.

We apologize for any inconvenience this may have caused.

If you have questions, please contact our support team: https://zapier.com/app/get-help
Jun 25, 03:08 PDT

Investigating - We're currently investigating an issue causing delays in the Zap run history page populating live runs.

Our team is actively working to identify and resolve the error. We will provide updates as soon as possible.

Thank you for your patience.
Jun 25, 01:11 PDT

Jun 24, 2025

Issue with Webhook steps processing actions unexpecting, causing errors.

Resolved - Our engineering team has rolled users back to a stable version of Webhooks by Zapier to address the recent issues with POST requests.

During the affected period, some data loss may have occurred for workflows where file contents were expected in webhook calls. In these cases, file contents were not returned in a usable format, which prevented downstream steps from receiving the correct file data.

We apologize for any inconvenience this may have caused and will continue to monitor the situation with any future app updates.

If you have questions, please contact our support team: https://zapier.com/app/get-help
Jun 24, 13:57 PDT

Monitoring - Our Engineering team is currently in the process of rolling back all users to a previous version of the Webhooks applications.

If you're still having a problem with a Webhooks action step, please feel free to reach out to our support team at here: https://zapier.com/app/get-help
Jun 24, 11:04 PDT

Investigating - We've identified an reoccurance of an issue where POST requests sent via WebHooks with Form payload type are returning unexpected content (e.g. ), resulting in missing output and causing dependent steps in Zaps to fail. Separtely, some users have also reported Post requests are sending two responses for a single POST action.

Our engineering team is actively working on a fix. Once deployed, we will automatically replay all affected runs and errored steps.
Jun 24, 10:18 PDT

Jun 23, 2025

Webhooks Steps with Form Data Causing Step Errors

Resolved - All errored Zap runs had been replayed successfully.

The POST requests made via Webhooks by Zapier should be working properly now.
Jun 23, 20:49 PDT

Monitoring - Our engineering team had deployed a fix and migrated all users to the newest app version of Webhooks by Zapier.

Zap runs should be working properly now and will be processed accordingly. We are currently in the process of replaying all affected and errored Zap runs.

We will share another update once all errored Zap runs are replayed successfully, and when this is resolved.
Jun 23, 20:11 PDT

Identified - On Monday, June 23, 2025, 03:06 UTC, we've identified an issue where POST requests sent via Webhooks with Form payload type are returning unexpected content (e.g. ), resulting in missing output and causing dependent steps in Zaps to fail.

Our engineering team is actively working on a fix. Once deployed, we will automatically replay all affected runs and errored steps.

There are currently no signs of data loss. We'll continue monitoring closely.
Jun 23, 17:46 PDT

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

All Systems Operational

Past Incidents