Zapier favicon

Zapier outage on 2026-10-21

zapier.com
October 2026 21 Minor incident

On 21 October, Zapier ran into two separate upstream problems. One broke Zaps that pull data from BambooHR for 6h 13m, the other delayed real-time updates in Zapier Tables for 25h 1m. Zapier traced both to providers it depends on, not to its own core platform.

Started

14:10 UTC

Duration

Lasted 6h 13m

Source

IsDown

Next time

Zapier is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

The first incident started at 14:10 UTC. Zapier said Zaps using BambooHR might encounter errors or fail to retrieve data because of a service disruption at BambooHR itself. By 14:18 Zapier moved to monitoring, but it had not confirmed BambooHR's service was fully restored. That incident lasted 6h 13m before resolution. The second incident began at 15:21 UTC, just over an hour later. Zapier reported that some customers would see delayed or missing real-time updates in Zapier Tables, including collaborator changes and refreshed formula results. It was explicit that Tables itself remained available, and that the underlying formula calculations and triggers kept running. The problem was limited to the delivery of real-time updates. At 15:52 Zapier identified the cause as an issue with an upstream service provider, not named, and said it had no estimated resolution time. A further update at 16:04 repeated that it was still awaiting recovery from that provider with no ETA. This incident ran for 25h 1m in total, making it by far the longer of the two. Zapier's status page carries just five updates across both incidents, and neither filing names the upstream provider responsible for the Tables delay. No user reports were filed during this window. There are no components listed as affected in the record, so the scope beyond what Zapier described in text is not specified.

Learning

Both incidents here trace back to a provider Zapier depends on rather than a fault in Zapier's own application code, and that is a distinction worth sitting with if you build on Zapier. A dependency outage upstream, such as the one at BambooHR, can make Zaps fail even though Zapier's platform is behaving exactly as designed. The Tables incident is sharper still: Zapier explicitly said Tables remained available and that triggers and formulas kept running, yet real-time updates still failed to deliver for over a day. If you were only watching whether Zapier's main interface loaded, you would have seen green the whole time, because the fault sat specifically in the update delivery layer, one step removed from the parts of the product you can directly observe. Zapier's own history shows 26 incidents in the last 90 days with a median duration of under three hours, so a 25-hour incident like this one is well outside the normal pattern. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.