Incidents and maintenance reported on status page for VoiceBot Studio https://status.voicebot.studio/ https://d1lppblt9t2x15.cloudfront.net/logos/7d1333cc4b606339f81797e0ac687e9a.png https://status.voicebot.studio/ en https://status.voicebot.studio/incident/902712 Tue, 09 Jun 2026 02:10:00 -0000 https://status.voicebot.studio/incident/902712#eda82605e73291a9c094202d60415908caa3314814d3349efa13999437866606 Incident Resolved: Call Logs & Billing Data We've resolved the issue that was preventing call logs from appearing on your dashboard. All call log data is now fully available and up to date across both your Dashboard and Billing views, including historical records. No action is required on your end — your call history and associated billing details should now display correctly. We're continuing to actively monitor to ensure everything remains stable. If you notice any missing or inaccurate data, please reach out to our support team and we'll be happy to help. Thank you for your patience. https://status.voicebot.studio/incident/902610 Tue, 09 Jun 2026 02:06:00 -0000 https://status.voicebot.studio/incident/902610#f690ba0842858309e00a970e52a380ad502aaac566eea18946423c4b7cd5bd8b Incident Resolved: Call Logs & Billing Data We've resolved the issue that was preventing call logs from appearing on your dashboard. All call log data is now fully available and up to date across both your Dashboard and Billing views, including historical records. No action is required on your end — your call history and associated billing details should now display correctly. We're continuing to actively monitor to ensure everything remains stable. If you notice any missing or inaccurate data, please reach out to our support team and we'll be happy to help. Thank you for your patience. https://status.voicebot.studio/incident/907180 Thu, 28 May 2026 11:27:00 -0000 https://status.voicebot.studio/incident/907180#7b99edcc6cc9b24d90caab49e4fddddfd629a74af56d5e4ae3fb227ce443b43c Incident Issue is fixed, it was caused by brief network issue with our database. we will be monitoring services to ensure stability. https://status.voicebot.studio/incident/907180 Thu, 28 May 2026 10:41:00 -0000 https://status.voicebot.studio/incident/907180#548ba3fa790688c90148758514e4023d3521529420169b14aaf46ae5fa72eaee Incident We are seeing increase call failure rates in calls, our team is actively working on it. https://status.voicebot.studio/incident/902610 Fri, 22 May 2026 08:40:00 -0000 https://status.voicebot.studio/incident/902610#72ea59717dec19a0d5238266671263a898737616157f58e15b002d87625902bd Incident We are currently experiencing a database performance degradation that is impacting the Call Logs feature. As a result, some users may notice slow loading times or temporary errors when trying to view their call logs on the dashboard. Our engineering team is actively investigating the root cause and working on a resolution. We apologize for the inconvenience and will provide updates as we make progress. https://status.voicebot.studio/incident/902712 Thu, 21 May 2026 13:40:00 -0000 https://status.voicebot.studio/incident/902712#3102dfcff2fc2165264db44354cd7ed5e220e8a9f976a25421d14cd2594e1389 Incident Incident Window: May 21, 2026, 3:55 PM CEST – Ongoing Status: Partially Resolved (Core Services Restored, Data Processing Catching Up) Affected Services: Real-Time Voice Processing, Live Chat, and Call Logging/Reporting Services Executive Summary On May 21, 2026, our platform experienced a technical disruption that affected our real-time communication services. While our primary management dashboard remains online and accessible, users initially experienced failures with call creation and live chat functionality. Additionally, there are ongoing delays in retrieving call logs and end-of-call reports. The root cause was traced back to a network routing configuration error with our upstream cloud infrastructure provider. While core communication services (call creation and chat) have been fully restored, backend data processing queues are currently catching up, which is causing a temporary delay in call logs appearing on the dashboard. Current Status & What Happened During a routine infrastructure update by our upstream cloud provider, an unexpected configuration error occurred in their network routing layer. This error caused severe packet loss and connection timeouts, blocking our backend services from initializing new voice calls and chat sessions. Our provider has since rolled back the problematic update, which fully restored live calling and chat capabilities. However, because data could not flow normally during the outage, a large backlog of call logs and end-of-call reports accumulated in our processing queues. Core live services are 100% operational, but our reporting servers are currently processing this backlog chronologically. As a result, you will notice a delay in new call logs appearing on your dashboard until the sync is complete. Next Steps & Preventative Actions To minimize the impact of similar upstream provider issues in the future, we are implementing the following measures: Enhanced Failover Routing: We are optimizing our network infrastructure to automatically reroute traffic through secondary backup channels if our primary provider experiences connection drops. Isolated Reporting Queues: We are restructuring our logging architecture to ensure that even during a network interruption, data reports are cached and synchronized to the dashboard faster once connectivity is restored. We sincerely apologize for the inconvenience this infrastructure event has caused and appreciate your continued patience while our data queues fully catch up.