Zapier experienced a 27.7-hour incident where Zap run history displayed with delays of up to several minutes, though Zap executions continued running normally and completing as expected. The issue was caused by elevated load on the Zap history indexing system. The problem was resolved when the indexing system recovered and new Zap runs began appearing in history with normal latency.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We are seeing the recovery of our Zap history indexing system following a period of elevated load. The immediate impact has been resolved, and new Zap runs are now appearing in your history with normal latency.
We will continue to update as new information is available.
We are currently investigating delays affecting the display of Zap run history. You may be seeing a delay in your runs showing up in your Zap history at this time.
Zap executions are running normally and completing as expected, but there may be a delay of up to several minutes before runs appear in your Zap history view.
We appreciate your patience as we work through this issue. We'll provide updates as the situation progresses.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with