We’ve restored service across the Zapier platform, and all affected components are now operational. Replays have been completed, and Zapier should now work as expected. Zaps that were previously paused due to this incident have been unpaused, and functionality has been restored for: • Zaps • Zapier Interfaces • Zapier Chatbots • Zapier Tables • Zapier Agents • Zapier Canvas • Custom Actions • Account settings pages • Billing pages (invoices and checkout) • Login and sign-up pages During the incident, trigger reliability was degraded due to reduced polling (about 89% of polls were skipped) and webhook events that failed or expired because of the cloud outage. Some data may not have been processed during this period because Zapier did not receive it from connected apps due to the outage. Zapier Agent runs that weren’t triggered by a Zap or Agent trigger may have failed during this period. Because these runs aren’t automatically replayable, we recommend reviewing and manually retrying any affected runs. While we’ve verified that all systems are operational, if you notice any lingering issues or unexpected behavior, please let us know — our Support Team is happy to help. You can reach us here: Zapier Support. Thank you for your patience and understanding as we worked through yesterday’s challenges.

We’ve restored service across the Zapier platform, and all affected components are now operational. Replays have been completed, and Zapier should now work as expected. Zaps that were previously paused due to this incident have been unpaused, and functionality has been restored for:

• Zaps

• Zapier Interfaces

• Zapier Chatbots

• Zapier Tables

• Zapier Agents

• Zapier Canvas

• Custom Actions

• Account settings pages

• Billing pages (invoices and checkout)

• Login and sign-up pages

Zap runs that were in Pending, Held, Error, or Scheduled statuses due to the incident have now been replayed, and workflow processing has resumed as expected. We’re continuing to monitor platform stability following the broader AWS service disruption that caused the earlier impact. While we’ve verified that all systems are operational, if you notice any lingering issues or unexpected behavior, please let us know — our Support Team is happy to help. You can reach us here: Zapier Support. Thank you for your patience and understanding as we worked through yesterday’s challenges.

We’ve restored service across the Zapier platform and all affected components are now operational. Zaps that were previously paused due to this incident have been unpaused, and functionality has been restored for:

• Zaps

• Zapier Interfaces

• Zapier Chatbots

• Zapier Tables

• Zapier Agents

• Zapier Canvas

• Custom Actions

• Account settings pages

• Billing pages (invoices and checkout)

• Login and sign-up pages

Zap runs that were in Pending, Held, Error, or Scheduled statuses due to the incident have now been replayed, and workflow processing has resumed as expected. We’re continuing to monitor platform stability following the broader AWS service disruption that caused the earlier impact.

We’ll share a follow-up via email soon with additional details and confirmation once all systems are fully verified, and our review on data integrity from this incident is complete. If you have any questions or need further assistance, our Support Team is happy to help — you can reach us here: Zapier Support. Thank you for your patience while we worked to restore full service.

We're continuing to monitor an issue impacting parts of the Zapier platform. You may have experienced issues accessing or running Zaps, as well as delays or errors in connected products and pages, including:

• Zaps

• Zapier Interfaces

• Zapier Chatbots

• Zapier Tables

• Zapier Agents

• Zapier Canvas

• Custom Actions

• Account settings pages

• Billing pages (invoices and checkout)

• Login and sign-up pages

We have identified the issue as part of a broader AWS service disruption and are actively restoring functionality. We will be automatically replaying Zap runs that were in Held, Errored, or Pending status soon to help restore processing. We’re still assessing for any data issues, and we’ll share updates as soon as we confirm. If you have any questions or need further assistance, our Support Team is happy to help. You can reach out here: Zapier Support. Thank you

We're continuing to monitor an issue impacting parts of the Zapier platform. We're aware of the following ongoing issues:

• Some Zaps may not load or run as expected.

• The Zap Editor and connected apps may fail to open or show errors.

• Interfaces, Agents, Chatbots, and Canvas remain intermittently available.

• Task processing and app connections are limited, which may delay or prevent Zap runs.

• Login and dashboard access may intermittently fail.

We'll continue monitoring and provide updates as the platform stabilizes.

We’re continuing to see signs of recovery from a widespread outage caused by an issue with our upstream cloud provider. Some systems are returning to normal, however parts of Zapier may remain affected. Currently:

• Some Zaps may not load or run.

• The Zap Editor and connected apps may fail to open or show errors.

• Interfaces, Agents, Chatbots, and Canvas remain unavailable.

• Task processing and app connections are limited, which may delay or prevent Zap runs.

• Login and dashboard access may intermittently fail.

Our teams are actively restoring impacted systems and monitoring overall recovery. Further updates will be shared as progress continues.

We’re continuing to recover from a widespread outage caused by an ongoing issue with our upstream cloud provider. While some systems are stabilizing, parts of Zapier remain affected. Currently:

• Some Zaps may not load or run.

• The Zap Editor and connected apps may fail to open or show errors.

• Interfaces, Agents, Chatbots, and Canvas remain unavailable.

• Task processing and app connections are limited, which may delay or prevent Zap runs.

• Login and dashboard access may intermittently fail.

Our teams are actively restoring impacted systems and monitoring overall recovery. Further updates will be shared as progress continues. If you need help, please contact Zapier Support

We're continuing to recover from a widespread outage affecting several Zapier systems following an ongoing incident with our upstream cloud provider. While we're seeing gradual improvement across parts of our platform, some Zapier features remain degraded or unavailable. At this time:

• Some Zaps may not load or run as expected.

• Access to the Zap Editor and connected apps may fail to load or return errors.

• Certain product areas, including Interfaces and Chatbots, are still unavailable.

• Task processing, polling, and app connections remain limited, which may delay or prevent Zap runs.

• Login and dashboard access may intermittently fail for some users.

Our engineering teams are actively working to restore service stability as upstream systems recover. We’re closely monitoring recovery progress and will continue to post updates as we learn more. If you need assistance, please reach out to Zapier Support.

We've identified that a mitigation has been applied upstream. We're starting to see our services recover. Nonetheless, we're still working on recovery efforts and assessing the impact. Our team is closely monitoring the situation and will continue to provide updates as we receive more information from the provider. If you need assistance, please reach out to Zapier Support - https://zapier.com/app/get-help Thank you for your patience and understanding while this external issue is being resolved.

We’ve identified that multiple services on the Zapier platform are being affected by an upstream provider outage. This issue is outside of Zapier’s control and appears to be part of a wider incident impacting multiple platforms. Our team is closely monitoring the situation and will continue to provide updates as we receive more information from the provider. If you need assistance, please reach out to Zapier Support - https://zapier.com/app/get-help Thank you for your patience and understanding while this external issue is being resolved.