Incidents 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/ Thu, 04 Jun 2026 07:21:16 +0000 https://status.voicebot.studio/#6165c7da1bf7356384b24a5f51c704eb316de931f985faee6add6aab6dd3663a Webhook Processing recovered https://status.voicebot.studio/ Thu, 04 Jun 2026 06:28:09 +0000 https://status.voicebot.studio/#6165c7da1bf7356384b24a5f51c704eb316de931f985faee6add6aab6dd3663a Webhook Processing went down https://status.voicebot.studio/ Fri, 29 May 2026 06:41:06 +0000 https://status.voicebot.studio/#b363046acd406ba747fe744fe5545bb086b11b2f21db17c5153429744a68c1a1 Webhook Processing recovered https://status.voicebot.studio/ Fri, 29 May 2026 06:28:08 +0000 https://status.voicebot.studio/#b363046acd406ba747fe744fe5545bb086b11b2f21db17c5153429744a68c1a1 Webhook Processing went down https://status.voicebot.studio/incident/907180 Thu, 28 May 2026 11:27:00 -0000 https://status.voicebot.studio/incident/907180#7b99edcc6cc9b24d90caab49e4fddddfd629a74af56d5e4ae3fb227ce443b43c 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 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 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 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. https://status.voicebot.studio/ Wed, 06 May 2026 07:56:19 +0000 https://status.voicebot.studio/#1b1cfaf8b2237def65a83ea6c74114bf4aab0d49d735126412042a19b21a786d Webhook Processing recovered https://status.voicebot.studio/ Wed, 06 May 2026 07:43:21 +0000 https://status.voicebot.studio/#1b1cfaf8b2237def65a83ea6c74114bf4aab0d49d735126412042a19b21a786d Webhook Processing went down https://status.voicebot.studio/ Sat, 02 May 2026 06:46:18 +0000 https://status.voicebot.studio/#e8c33b7aeacc0dd96c1d0ffc81634e072b15a1c49cf47a56fc55d9703d420d73 Webhook Processing recovered https://status.voicebot.studio/ Sat, 02 May 2026 06:33:17 +0000 https://status.voicebot.studio/#e8c33b7aeacc0dd96c1d0ffc81634e072b15a1c49cf47a56fc55d9703d420d73 Webhook Processing went down https://status.voicebot.studio/ Tue, 28 Apr 2026 07:50:15 +0000 https://status.voicebot.studio/#9b50c941ebb77d20b97baa9533bc7d75bda2335d34f76a907c014a31ac259da6 Web Widget & Embeds recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 18:06:58 +0000 https://status.voicebot.studio/#e98d6488f1fb0c0527e34c64a95037052bc1a36c866af6553ed8f8e6f48a448d Analytics Engine recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 18:06:54 +0000 https://status.voicebot.studio/#8647024e06cb9fb40058d44730ed176a4cb8956db5898e8ebbf0d1b89976f0b1 WhatsApp Gateway recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 18:05:27 +0000 https://status.voicebot.studio/#45b791ce1d1a73ee7be815ceac5fc257086f071e169847224233993161c13e4c Web Widget & Embeds recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 18:04:30 +0000 https://status.voicebot.studio/#037b63066a32e414a8b420bdfaf2f76b40594f250dec581db1e91af20fb1db14 Billing Services recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 18:04:05 +0000 https://status.voicebot.studio/#037d0903e4f68e5d38df18da4f769d2f826796e4dc2f447d01bbe4446dd54ddf Studio Backend recovered https://status.voicebot.studio/ Mon, 27 Apr 2026 17:49:34 +0000 https://status.voicebot.studio/#037b63066a32e414a8b420bdfaf2f76b40594f250dec581db1e91af20fb1db14 Billing Services went down https://status.voicebot.studio/ Mon, 27 Apr 2026 17:46:57 +0000 https://status.voicebot.studio/#e98d6488f1fb0c0527e34c64a95037052bc1a36c866af6553ed8f8e6f48a448d Analytics Engine went down https://status.voicebot.studio/ Mon, 27 Apr 2026 17:46:43 +0000 https://status.voicebot.studio/#8647024e06cb9fb40058d44730ed176a4cb8956db5898e8ebbf0d1b89976f0b1 WhatsApp Gateway went down https://status.voicebot.studio/ Mon, 27 Apr 2026 17:46:03 +0000 https://status.voicebot.studio/#037d0903e4f68e5d38df18da4f769d2f826796e4dc2f447d01bbe4446dd54ddf Studio Backend went down https://status.voicebot.studio/ Mon, 27 Apr 2026 17:45:40 +0000 https://status.voicebot.studio/#9b50c941ebb77d20b97baa9533bc7d75bda2335d34f76a907c014a31ac259da6 Web Widget & Embeds went down https://status.voicebot.studio/ Mon, 27 Apr 2026 17:45:14 +0000 https://status.voicebot.studio/#45b791ce1d1a73ee7be815ceac5fc257086f071e169847224233993161c13e4c Web Widget & Embeds went down https://status.voicebot.studio/ Thu, 23 Apr 2026 07:36:16 +0000 https://status.voicebot.studio/#d6006afc92d6ed6ea07a91d91b02397225b7cf0a35441163ed02e57e9bfb8615 Webhook Processing recovered https://status.voicebot.studio/ Thu, 23 Apr 2026 06:53:15 +0000 https://status.voicebot.studio/#d6006afc92d6ed6ea07a91d91b02397225b7cf0a35441163ed02e57e9bfb8615 Webhook Processing went down https://status.voicebot.studio/ Thu, 09 Apr 2026 07:51:07 +0000 https://status.voicebot.studio/#feb28e5d72268e4b85bca1093580688e7e89c26f7a47fdb1e15c1f04f78114be Webhook Processing recovered https://status.voicebot.studio/ Thu, 09 Apr 2026 06:48:15 +0000 https://status.voicebot.studio/#feb28e5d72268e4b85bca1093580688e7e89c26f7a47fdb1e15c1f04f78114be Webhook Processing went down https://status.voicebot.studio/ Wed, 25 Mar 2026 06:49:24 +0000 https://status.voicebot.studio/#5dc021341df48f2453384625ba7d2e095dac437a7cbe035f72717655068a1a74 Webhook Processing recovered https://status.voicebot.studio/ Wed, 25 Mar 2026 06:23:25 +0000 https://status.voicebot.studio/#5dc021341df48f2453384625ba7d2e095dac437a7cbe035f72717655068a1a74 Webhook Processing went down https://status.voicebot.studio/ Tue, 17 Mar 2026 02:46:58 +0000 https://status.voicebot.studio/#cdde71adceb6f03c3fc27eeff3a3dc05d9147272868811918cf59b4a15e2cedb Webhook Processing recovered https://status.voicebot.studio/ Tue, 17 Mar 2026 02:33:05 +0000 https://status.voicebot.studio/#cdde71adceb6f03c3fc27eeff3a3dc05d9147272868811918cf59b4a15e2cedb Webhook Processing went down https://status.voicebot.studio/ Fri, 13 Mar 2026 07:55:33 +0000 https://status.voicebot.studio/#0d94063b8b44af1595bddd55855543163268690e3d4a2be65815800d10a9b88a Webhook Processing recovered https://status.voicebot.studio/ Fri, 13 Mar 2026 06:58:16 +0000 https://status.voicebot.studio/#0d94063b8b44af1595bddd55855543163268690e3d4a2be65815800d10a9b88a Webhook Processing went down