Z
Outage recap · Zapier

Zapier outage — August 28, 2026

On August 28, 2026, Zapier had a reported incident on Zapier's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Tables, Chatbots, and Forms not loading for some customers

minor
Started
Aug 28, 10:35 AM EDT
Resolved
Aug 28, 11:35 AM EDT
Duration
1h 1m

Zapier's updates (3)

  1. investigating · Aug 28, 10:35 AM EDT

    We're currently investigating an issue affecting Tables, Chatbots, and Forms for some users. Affected users may find that existing Tables, Chatbots, or Forms are not loading and are instead being redirected to a creation page. If you need help in the meantime, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

  2. monitoring · Aug 28, 11:01 AM EDT

    A fix has been implemented for the issue affecting Tables, Chatbots, and Forms. These should now be loading as expected for affected users. We are continuing to monitor to confirm full stability. We will post a final update within 24 hours. If anything still seems off, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

  3. resolved · Aug 28, 11:35 AM EDT

    The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC. Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead. All affected surfaces — Tables, Forms, Chatbots, and folder/subfolder creation — have been verified and are working normally. No data loss occurred, and Zap runs were not affected. If you're still experiencing issues, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thank you for your patience.

What our checks recorded

We checked Zapier 13 times from Zapier's start time to its resolution, once every five minutes. Every one of them reached Zapier's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 233 ms, against 210 ms over the 24 hours before. Zapier posted the incident at Aug 28, 10:35 AM EDT.

Updates are Zapier's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Zapier. This recap summarizes incidents published on Zapier's official status page.