The issue affecting Chatbots has been resolved.
Between approximately 11:00 PM and 5:30 AM MST on June 8, 2026, some customers may have experienced failures or timeouts when initializing chats or interacting with embedded chatbots. The issue self-resolved and Chatbots has been operating normally since.
Zap Runs and tasks were not affected. No data loss occurred.
We are continuing to monitor the service and will take steps to reduce the likelihood of recurrence.
If you experienced issues during this window or notice anything still not working, contact Support: https://zapier.com/app/get-help
Resolved
The issue affecting Chatbots has been resolved.
Between approximately 11:00 PM and 5:30 AM MST on June 8, 2026, some customers may have experienced failures or timeouts when initializing chats or interacting with embedded chatbots. The issue self-resolved and Chatbots has been operating normally since.
Zap Runs and tasks were not affected. No data loss occurred.
We are continuing to monitor the service and will take steps to reduce the likelihood of recurrence.
If you experienced issues during this window or notice anything still not working, contact Support: https://zapier.com/app/get-help
Identified
We identified an issue that caused some Chatbots to fail or time out when customers initialized chats or interacted with embedded chatbots. Some users may have seen a "Forbidden" error.
The affected period was approximately 11:00 PM – 5:30 AM MST on June 8, 2026.
Zap Runs and tasks were not affected.
No data loss is expected.
The issue has since self-resolved. Chatbots metrics are healthy and error rates have returned to normal.
We traced the cause to a degradation in our LLM proxy, which led to backend request timeouts and dropped chatbot connections.
We are continuing to investigate the scope of customer impact and will post another update soon.
If you experienced issues with Chatbots during this window or notice anything still not working, please contact Support: https://zapier.com/app/get-help
