This incident has been resolved. Our systems have returned to operational, and all tasks should be processed as expected.

While this has been resolved, we’re still looking for any lingering effects that this incident may have caused. More detailed communications will be sent regarding any updates or findings.

Thank you for your patience and understanding. If you need support, you can get in touch with us here: https://zapier.com/app/get-help

We are seeing a return to healthy operations with the AWS incident being resolved. However, we still expect delays in processing hooks over the next few hours.

We are continuing to monitor the status of this incident and will provide further updates as we have them.

If you have any further questions, please reach out to our Support team: https://zapier.com/app/get-help

Thank you!

The Zapier.com website has returned to full function. Additionally, Zaps that trigger with a "Polling Trigger" are beginning to process as expected. Zaps using an "Instant Trigger" are still seeing degraded performance as we begin to see improvements in server status from AWS.

We'll provide an update as soon as we can. You can also follow along with AWS' status here: https://health.aws.amazon.com/health/status

If you have any further questions, please reach out to our Support team:

https://zapier.com/app/get-help

We are continuing to experience issues caused by a widespread AWS outage that is affecting Zap Processing and the availability of portions of Zapier.com. We are seeing Zaps begin to process again, however at a degraded level. Similar degraded performance is occurring throughout other portions of Zapier.com.

AWS has reported beginning to see improvements in status and are working towards full recovery. You can follow along with AWS' status page here:

https://health.aws.amazon.com/health/status

If you have any questions about this incident, please reach out to our Support team:

https://zapier.com/app/get-help

We are continuing to experience a widespread outage in AWS that is affecting Zap processing as well as all parts of Zapier.com. We are currently investigating the issue, and will update this status page once new information becomes available.

Some possible manifestations of this outage are:

• Zaps not running as expected

• Webpages not loading/presenting errors

• Errors stating "INTERNAL_FUNCTION_INVOCATION_FAILED”

You can follow along with AWS' own status page here:

https://health.aws.amazon.com/health/status

If you have any questions about this incident, please reach out to our Support team:

https://zapier.com/app/get-help