Previous incidents
Degraded service — SIP call transfers
Resolved Jun 16, 2026 at 8:00am UTC
The incident affecting SIP call transfers has been resolved by our telephony provider. All transfers are now operating normally.
We apologize for any inconvenience caused.
1 previous update
Degraded Performance — Conversations
Resolved Jun 8, 2026 at 2:37pm UTC
The incident has been resolved. The latency issues affecting some conversations were caused by an incident on our hosting provider's side, which has now been fully resolved. Conversations are back to normal performance.
Thank you for your patience and we apologize for the disruption.
1 previous update
Degraded Performance — Increased Latency on Conversations
Resolved May 29, 2026 at 5:08pm UTC
The incident that resurfaced at 4:50 PM has been resolved. Microsoft Azure infrastructure has been restored and performance is back to normal levels. We will continue to closely monitor the situation to ensure long-term service stability. We apologize for the inconvenience caused.
3 previous updates
Ongoing — Call Transfer Degradation
Resolved May 4, 2026 at 4:30pm UTC
A patch has been applied and appears to have resolved the issue. No errors have been observed in the logs since 6:28 PM CEST. Call transfers are operating normally. We will continue to monitor and share a post-mortem once our analysis is complete.
3 previous updates
Post Call Latency & API Errors — Resolved
Resolved Apr 29, 2026 at 2:48pm UTC
We experienced a platform incident between 4:07 PM and 4:29 PM CEST.
Impact: Latency on post call action delivery, and errors across all Volubile APIs.
The incident has been resolved. All systems are fully operational.
Ongoing Incident – Platform Outage
Resolved Apr 13, 2026 at 9:47am UTC
The incident affecting our telephony network has been fully resolved as of 11:44 AM. The platform is now fully operational and all inbound and outbound calls are restored.
Root cause: Issue on our telephony network.
Impact: Inbound and outbound calls were unavailable for approximately 24 minutes.
We apologize for the disruption and thank you for your patience.
1 previous update