Zapier experienced a chatbot service disruption from 11:00 PM to 5:30 AM MST on June 8, 2026, where chatbots failed to initialize or dropped connections during user interactions, with some users encountering "Forbidden" errors. The issue was caused by degradation in Zapier's LLM proxy, which led to backend request timeouts and connection failures. The problem self-resolved after approximately 6.5 hours with chatbot metrics returning to normal and no data loss reported.
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 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
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