Previous incidents

This incident has been resolved. All calls are now processing normally and our services are fully operational.

Root cause: The disruption was caused by a memory issue affecting one of our system components.

We will be conducting a thorough investigation into this issue and will implement measures to prevent similar disruptions in the future.

We sincerely apologize for the inconvenience this may have caused and thank you for your patience.

Between 8:57 AM and 9:01 AM today, the platform was unable to process some incoming calls.
Root cause: A batch job saturated a database connection pool, preventing the call-handling service from acquiring connections.
Current status: The issue has been mitigated and service has returned to normal. We are continuing to monitor the platform closely to confirm stability.
We apologize for the disruption and will share further updates if needed.

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.

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.

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.

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.