[status] Resolved: We identified an issue where a very small fraction (<0.0001% of traffic). While the overall impact was minimal, we understand even small disruptions can affect critical workflows.
Root Cause:
Zap triggers run on b… https://t.co/Ofdd5Ft3xd
[status] Resolved: All affected services (Interfaces, Tables, Agents, Chatbots, and Custom Actions) are back online and operating as expected. We’ll continue to keep an eye on things. If you have any questions or still see issues, ple… https://t.co/qheQ3bq9iy
[status] Monitoring: Services for interfaces, tables, agents, chatbots, and custom actions are coming back online. Error rates are dropping, and performance is improving. We’re watching closely and will post another update as we learn… https://t.co/F4C1qsRlIl
[status] Identified: We're currently investigating an issue where some users are encountering timeout or network errors when attempting to publish their Zaps.
Initial findings suggest the issue is related to a gateway timeout between… https://t.co/Dx8u9kcOo6
[status] Identified: Customers have reported a range of issues related to app authorizations, with a specific emphasis on authorizations related to the Google integration.
We appreciate your patience as we investigate these issues. https://t.co/GArOl7SxI9
[status] Monitoring: We're working on processing our backlog of Tables-related Zap triggers now. Thanks for your patience while we work to resolve this incident. https://t.co/sjZ2NYQ8wJ
[status] Identified: Access to the Tables User Interface is now operational; however, the triggers associated with the tables are still impacted. https://t.co/djCEmWLUYb
[status] Resolved: The issue where Zapier accounts were being automatically switched, returning "Unable to access Zap" and "You either don't have permission to see this Zap or the Zap does not exist" errors, is now resolved. You shoul… https://t.co/Q8wO9k1IH5
[status] Resolved: Earlier today, our team identified an issue that was causing Functions to silently fail, starting on June 5, 2025 at 10:34:06 PM UTC.
Functions that were created and updated during this timeframe did not run as exp… https://t.co/GUSCqi6fyW
[status] Monitoring: We’ve temporarily disabled the “Test run” feature while we resolve the root cause and prevent this issue from happening again.
Most users should see Zap executions working as expected. However, Zap History may st… https://t.co/3zSjI9G8Qn
[status] Scheduled (May 31, 2025, 14:00 PDT): During this maintenance window, some users may experience delays with webhooks, and https://t.co/5WY7GCU6mB may return 502 (Bad Gateway) or 503 (Service Unavailable) errors. We expect a mi… https://t.co/6eKM1cJuBi
[status] Resolved: The incident re-commenced at 10:44 PM UTC and was resolved by 00:06 AM.
During this period, users would have experienced failures and errors in many of their apps using Zapier. The specific error message displayed … https://t.co/LmMneRYKmf
[status] Scheduled (May 10, 2025, 09:00 PDT): During this maintenance window, some users may experience delays with webhooks, and https://t.co/5WY7GCUEc9 may return 502 (Bad Gateway) or 503 (Service Unavailable) errors. While we antic… https://t.co/AexJC3tybD