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, 2025 - 12:47 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, 2025 - 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, 2025 - 10:04 PDT
Unresolved incidents: Users attempting to access the Interfaces page are encountering a 500 Internal Server Error., 502 Errors Impacting zapier.com Access and Zap Execution Affected.
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.
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
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