All Systems Operational
Website ? Operational
Zaps Operational
Instant Triggers ? Operational
Polling Triggers ? Operational
Searches & Writes ? Operational
Apps ? Operational
Developer Platform Operational
Operational
Degraded Performance
Partial Outage
Major Outage
System Metrics Month Week Day
Polling Triggers Reliability ?
Fetching
Polling Triggers Response Time ?
Fetching
Instant Triggers Reliability ?
Fetching
Instant Triggers Response Time ?
Fetching
Support Queue ?
Fetching
Website Response Time
Fetching
Past Incidents
Jul 28, 2016

No incidents reported today.

Jul 27, 2016

No incidents reported.

Jul 26, 2016
Resolved - The issues with our provider are now resolved, and Zaps are running at full speed again. Any failed tasks may be replayed; customers with Autoreplay enabled need take no action.
Jul 26, 10:21 UTC
Monitoring - Polling Zaps are currently delayed, and some requests to zapier.com are failing due to issues with one of our providers. We're running at 50% capacity until the issue is resolved. Instant triggers are unaffected.
Jul 26, 10:10 UTC
Identified - We're seeing delays to running Zaps and website response times due to issues with one of our providers. We'll update this incident when we know more.
Jul 26, 10:03 UTC
Jul 25, 2016

No incidents reported.

Jul 24, 2016

No incidents reported.

Jul 23, 2016

No incidents reported.

Jul 22, 2016
Resolved - Feedly Zaps are back to normal, we apologize for any Feedly Zaps that triggered unexpectedly and we are prioritizing internal safety mechanisms to prevent this from happening again. Below is recap of what happened and what we're doing now.

The anomaly was caused by a broken migration that changed how Zapier "identifies" new posts in Feedly triggers. This caused Zapier to think every post it saw was "new" and therefore required triggering. Once we identified this issue, we immediately began halting Feedly Zaps and initiating a rollback. After the rollback, we confirmed Feedly Zaps were behaving properly again and began resuming Feedly Zaps with the correct behavior. All Feedly Zaps are back to normal.

Any "Pending Tasks" for Feedly you may see in your Task History will not run.

As a result, we'll be prioritizing the implementation of new safety mechanisms to validate the behavior of any migrations so that this doesn't happen again. We apologize for the hassle.

Non-Feedly Zaps were not effected in this outage.
Jul 22, 21:19 UTC
Monitoring - Feedly Zaps are resuming now. We'll monitor the situation as they come back online and recap once we're back to 100%.
Jul 22, 21:03 UTC
Identified - A failed migration caused a large number of Feedly Zaps to run unexpectedly. We've identified the root cause, paused all Zaps, will apply a fix and will resume Feedly Zaps shortly.
Jul 22, 20:50 UTC
Jul 21, 2016

No incidents reported.

Jul 20, 2016
Resolved - Networking issues look fully resolved - we're all clear now and zaps are back up to speed!
Jul 20, 03:20 UTC
Monitoring - Some networking latency issues with our upstream provider may cause some zaps to be delayed.
Jul 19, 18:57 UTC
Jul 18, 2016

No incidents reported.

Jul 17, 2016

No incidents reported.

Jul 16, 2016

No incidents reported.

Jul 15, 2016

No incidents reported.

Jul 14, 2016

No incidents reported.