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.

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.

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.