Previous incidents

This morning’s interruption (from 10:19 CET, with a brief recovery at 10:38 CET, until full restoration at 11:25 CET) was caused by a hardware failure at our cloud provider. A network component on the physical server hosting one of our databases failed unexpectedly, which cut the database off from the network. Because the platform relies on this database, calls and the Backoffice were unavailable during this period.

Our provider has confirmed the failure and is tracking it on their side to p...

The issue has been resolved and outbound calls are being initiated normally again.

Between September 29 at 14:00 CEST and September 30 12:50 CEST, database timeouts prevented part of the outbound calls from being placed. A fix has been deployed and the service has remained stable since. Outbound calls that failed during this window are being relaunched.

We apologize for the inconvenience and thank you for your patience.

The issue has been resolved and inbound calls are being handled normally again.

Between 14:04pm and 14:09pm CEST, an internal routing component became temporarily unavailable following an infrastructure change, preventing part of the inbound calls from being established. Service was fully restored at 14:09pm CEST and has remained stable since.

We apologize for the inconvenience and thank you for your patience.

We can confirm that the outage has been fully resolved and our services are now operating normally and stable.

Thank you for your patience and understanding throughout this incident.