Diabolocom Outage History
Diabolocom is up right nowPingoru has recorded 51 incidents for Diabolocom: 45 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 8 of 720 (1%) |
| May 2026 | 2 | 22 of 744 (3%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 3 | 2 of 744 (0%) |
| August 2026 | 2 | 20 of 744 (3%) |
| September 2026 | 9 | 29 of 720 (4%) |
| October 2026 | 3 | 3 of 509 (1%) |
Incidents, newest first
Critical October 14, 2026 WebRTC media issue 1h 45m WebRTC
Started Oct 14, 2026, 07:12 AM UTC· resolved Oct 14, 2026, 08:58 AM UTC
- investigating Oct 14, 2026, 07:12 AM UTC
We are currently investigating this issue.
- monitoring Oct 14, 2026, 08:11 AM UTC
Fixed. Agents should log out and log in again to establish correct WebRTC session.
- monitoring Oct 14, 2026, 08:58 AM UTC
The issue is confirmed to be fully fixed.
- resolved Oct 14, 2026, 08:58 AM UTC
This incident has been resolved.
Minor October 7, 2026 Storage issue 1h 2m Recordings, Recordings, Scenario, Scenario
Started Oct 07, 2026, 01:35 PM UTC· resolved Oct 07, 2026, 02:37 PM UTC
- investigating Oct 07, 2026, 01:35 PM UTC
We are currently investigating this issue.
- investigating Oct 07, 2026, 01:37 PM UTC
We are continuing to investigate this issue.
- resolved Oct 07, 2026, 02:37 PM UTC
This incident has been resolved.
Minor October 5, 2026 Voice Instability and Disturbance 28m Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls and 53 more
Started Oct 05, 2026, 09:28 AM UTC· resolved Oct 05, 2026, 09:56 AM UTC
- investigating Oct 05, 2026, 09:28 AM UTC
We are experiencing disruptions to our voice services. We are currently investigating the issue.
- identified Oct 05, 2026, 09:31 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 05, 2026, 09:46 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 05, 2026, 09:56 AM UTC
This incident has been resolved.
Minor September 28, 2026 Instability and delays on ur Platforms 26m Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls and 8 more
Started Sep 28, 2026, 08:57 AM UTC· resolved Sep 28, 2026, 09:24 AM UTC
- monitoring Sep 28, 2026, 08:57 AM UTC
We experienced slowdowns and instability between 10:37 a.m. and 10:50 a.m. Nous avons rencontré des ralentissement, et des instabilités entre 10H37 et 10H50
- resolved Sep 28, 2026, 09:24 AM UTC
This incident has been resolved.
Critical September 28, 2026 AI products currently unavailable 23h 47m Delays on call transcriptions, Call summary generation, IVR - AI Recording Processor Block, IVR - Quality Monitoring Block and 11 more
Started Sep 28, 2026, 07:39 AM UTC· resolved Sep 29, 2026, 07:27 AM UTC
- identified Sep 28, 2026, 07:39 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 28, 2026, 08:33 AM UTC
Virtual Agent and Agent Assist are available again. Our other services are still down at this time. Virtual agent et agent assist de nouveau accessible. Nos autres services sont toujours hors service pour le moment
- monitoring Sep 28, 2026, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 29, 2026, 07:27 AM UTC
This incident has been resolved.
Major September 21, 2026 Virtual Agent down 11m Virtual Agent
Started Sep 21, 2026, 03:15 PM UTC· resolved Sep 21, 2026, 03:27 PM UTC
- identified Sep 21, 2026, 03:15 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Sep 21, 2026, 03:27 PM UTC
This incident has been resolved.
Minor September 21, 2026 File Storage issue 34m Scenario, Scenario, Scenario, Scenario and 13 more
Started Sep 21, 2026, 02:53 PM UTC· resolved Sep 21, 2026, 03:27 PM UTC
- identified Sep 21, 2026, 02:53 PM UTC
We are experiencing an issue with our file management service. This may affect audio files and routing in your scenarios. The issue has been identified, and our team is taking the necessary steps to resolve it as quickly as possible. Nous rencontrons un incident au niveau de notre service de gestion de fichiers. Cela peut avoir un impact sur les fichiers audio et le routage au niveau de vos scénarios. Le problème est identifié, notre équipe fait le nécessaire pour résoudre cela le plus rapidement possible.
- monitoring Sep 21, 2026, 03:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 21, 2026, 03:27 PM UTC
This incident has been resolved.
Critical September 21, 2026 Virtual Agent Down 24m Virtual Agent
Started Sep 21, 2026, 02:42 PM UTC· resolved Sep 21, 2026, 03:06 PM UTC
- investigating Sep 21, 2026, 02:42 PM UTC
We are currently investigating this issue.
- resolved Sep 21, 2026, 03:06 PM UTC
This incident has been resolved.
Major September 21, 2026 Mobile admin down 12m Voice, Voice Convergence to engage, SMS, DATA and 5 more
Started Sep 21, 2026, 02:34 PM UTC· resolved Sep 21, 2026, 02:47 PM UTC
- investigating Sep 21, 2026, 02:34 PM UTC
We are currently investigating this issue.
- investigating Sep 21, 2026, 02:35 PM UTC
We are continuing to investigate this issue.
- resolved Sep 21, 2026, 02:47 PM UTC
This incident has been resolved.
Major September 21, 2026 Quality monitoring slowdowns 1h 59m Delays on call transcriptions, Call summary generation, IVR - AI Recording Processor Block, IVR - Quality Monitoring Block and 10 more
Started Sep 21, 2026, 08:04 AM UTC· resolved Sep 21, 2026, 10:04 AM UTC
- identified Sep 21, 2026, 08:04 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 21, 2026, 08:42 AM UTC
We are continuing to work on a fix for this issue.
- identified Sep 21, 2026, 08:42 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Sep 21, 2026, 09:37 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 21, 2026, 10:04 AM UTC
This incident has been resolved.
Major September 4, 2026 Test Zendesk X Diabolocom 55m Test API, Test API 2
Started Sep 04, 2026, 07:36 AM UTC· resolved Sep 04, 2026, 08:31 AM UTC
- investigating Sep 04, 2026, 07:36 AM UTC
We are currently investigating this issue.
- resolved Sep 04, 2026, 08:31 AM UTC
This incident has been resolved.
Major September 1, 2026 Test Incident Diabolocom - Do not take it in account 58m Voice - Inbound calls, Call scripts
Started Sep 01, 2026, 08:14 AM UTC· resolved Sep 01, 2026, 09:12 AM UTC
- investigating Sep 01, 2026, 08:14 AM UTC
We are currently investigating this issue.
- monitoring Sep 01, 2026, 08:20 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 01, 2026, 09:12 AM UTC
This incident has been resolved.
Critical August 12, 2026 Diabolocom Knowledge base - down 19h 55m Support access
Started Aug 12, 2026, 11:53 AM UTC· resolved Aug 13, 2026, 07:48 AM UTC
- identified Aug 12, 2026, 11:53 AM UTC
The knowledge base is currently unavailable. Please use the following URL to contact our support team: https://support.diabolocom.com/hc/en-us/requests/new La base de connaissance n'est pas accessible pour le moment. Vous pouvez passer par l'URL suivante pour nous contacter au support : https://support.diabolocom.com/hc/en-us/requests/new
- resolved Aug 13, 2026, 07:48 AM UTC
This incident has been resolved.
Minor August 3, 2026 API & Contact Datas - Degraded performance 19m REST APIs, FR10
Started Aug 03, 2026, 02:53 PM UTC· resolved Aug 03, 2026, 03:12 PM UTC
- identified Aug 03, 2026, 02:53 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 03, 2026, 03:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 03, 2026, 03:12 PM UTC
This incident has been resolved.
Critical July 23, 2026 Incident OVH - Accès à la plateform impossible 1h 12m Plateform access, HADS2
Started Jul 23, 2026, 07:15 AM UTC· resolved Jul 23, 2026, 08:28 AM UTC
- identified Jul 23, 2026, 07:15 AM UTC
OVH Incident - Unable to Access the Platform
- monitoring Jul 23, 2026, 08:03 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 23, 2026, 08:28 AM UTC
This incident has been resolved.
Major July 3, 2026 TEST DIABOLOCOM SUPPORT 17m Test API
Started Jul 03, 2026, 03:22 PM UTC· resolved Jul 03, 2026, 03:39 PM UTC
- investigating Jul 03, 2026, 03:22 PM UTC
CECI EST UN TEST / THIS IS A TEST
- resolved Jul 03, 2026, 03:39 PM UTC
This incident has been resolved.
Critical July 2, 2026 Calls Not routed to Agents 36m Voice - Inbound calls, Voice - Inbound calls
Started Jul 02, 2026, 12:21 PM UTC· resolved Jul 02, 2026, 12:58 PM UTC
- identified Jul 02, 2026, 12:21 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jul 02, 2026, 12:43 PM UTC
FR1 > Fixed FR1 > Rétabli
- identified Jul 02, 2026, 12:47 PM UTC
Both platforms were fixed.
- monitoring Jul 02, 2026, 12:47 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 02, 2026, 12:51 PM UTC
We are continuing to monitor for any further issues.
- resolved Jul 02, 2026, 12:58 PM UTC
No impact observed.
Minor June 1, 2026 Diabolocom mobile Datas 45m DATA
Started Jun 01, 2026, 08:46 AM UTC· resolved Jun 01, 2026, 09:31 AM UTC
- identified Jun 01, 2026, 08:46 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 01, 2026, 09:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 01, 2026, 09:31 AM UTC
This incident has been resolved.
Minor May 19, 2026 Minor Incident - Archives recordings 19h 50m SFTP, SFTP, SFTP, SFTP and 30 more
Started May 19, 2026, 12:24 PM UTC· resolved May 20, 2026, 08:15 AM UTC
- identified May 19, 2026, 12:24 PM UTC
EN : We have identified an issue affecting playback of some recordings in the Archives. Users may encounter the following error message when previewing a call: “Your browser can’t decode the audio file.” This issue may also cause slowdowns when accessing files through SFTP. Our technical teams have identified the root cause, and a fix is currently being deployed. Resolution is expected later tonight, or by tomorrow at the latest. We apologize for the inconvenience and will continue to share updates through this status page. FR : Nous avons identifié un problème affectant la lecture de certains enregistrements dans les Archives. Les utilisateurs peuvent rencontrer le message d’erreur suivant lors de la prévisualisation d’un appel : “Your browser can’t decode the audio file.” Ce problème peut également entraîner des ralentissements lors de l’accès aux fichiers via le SFTP. Nos équipes techniques ont identifié la cause et un correctif est en cours de déploiement. La résolution est prévue dans la soirée, au plus tard demain. Nous vous prions de nous excuser pour la gêne occasionnée et vous tiendrons informés de l’avancement via cette page de statut.
- identified May 19, 2026, 12:36 PM UTC
EN: Following additional investigations, this was identified as a false alarm regarding the global platform impact. The issue is currently limited to the DE1 platform only. Other platforms are not impacted. Our technical teams are continuing investigations and deploying the fix on the affected environment. We apologize for the confusion caused and thank you for your understanding. FR: Après investigation complémentaire, il s’avère qu’il s’agissait d’une fausse alerte concernant l’impact global de la plateforme. L’incident est actuellement limité à la plateforme DE1 uniquement. Les autres plateformes ne sont pas impactées. Nos équipes techniques poursuivent les investigations et le déploiement du correctif sur l’environnement concerné. Nous vous présentons nos excuses pour la confusion occasionnée et vous remercions pour votre compréhension.
- resolved May 20, 2026, 08:15 AM UTC
EN: The fix has been successfully applied on the affected platform. Recording services have now fully recovered and are operating normally. We thank you for your patience and apologize for the inconvenience caused. FR: Le correctif a été appliqué avec succès sur la plateforme concernée. Les services d’enregistrements (Recordings) sont désormais pleinement rétablis et fonctionnent normalement. Nous vous remercions pour votre patience et vous présentons nos excuses pour la gêne occasionnée.
Minor May 12, 2026 Sim Management Issue 2h 13m Sim Management(Activation,Suspension,...)
Started May 12, 2026, 08:28 AM UTC· resolved May 12, 2026, 10:41 AM UTC
- investigating May 12, 2026, 08:28 AM UTC
We are currently experiencing an issue with our partner API interface. The issue is currently being investigated.
- investigating May 12, 2026, 10:00 AM UTC
The issue is still being investigated on the partner's side. Currently, around 11% of user requests are impacted. If you experience any issues with SIM management actions, please retry now or later.
- resolved May 12, 2026, 10:41 AM UTC
The incident has been resolved and services are operating normally. We will continue monitoring the situation closely.
Critical April 20, 2026 ODD Plateforms Down 2h 58m Plateform access, Plateform Access, Plateform Access, Plateform Access and 2 more
Started Apr 20, 2026, 12:50 PM UTC· resolved Apr 20, 2026, 03:48 PM UTC
- identified Apr 20, 2026, 12:50 PM UTC
We are currently experiencing an issue across all of our platforms We apologize for any inconvenience this may cause
- identified Apr 20, 2026, 01:46 PM UTC
WebRTC connections are currently unstable, with intermittent WebSocket disconnections causing brief spinner displays in the agent interface before automatic recovery. All other services have now been restored.
- identified Apr 20, 2026, 02:08 PM UTC
🇫🇷 Mise à jour Le service IMAP est désormais totalement stabilisé : la récupération des emails fonctionne à nouveau normalement et sans délai. Le service WebRTC est également rétabli, mais peut nécessiter encore quelques minutes pour se stabiliser complètement en raison du volume élevé de connexions simultanées. Le seul point restant concerne des déconnexions WebSocket intermittentes, pouvant entraîner des problèmes de connexion sur l’interface agent ; nos équipes techniques sont actuellement mobilisées pour résoudre ce sujet. 🇬🇧 Update IMAP is now fully stabilized: email retrieval is working normally again without delays. WebRTC has also recovered, although it may take a few more minutes to fully stabilize due to high concurrent traffic. The only remaining issue is intermittent WebSocket disconnections, which may cause connection issues on the agent interface; our technical team is actively working on resolving it.
- identified Apr 20, 2026, 02:33 PM UTC
FR : Si le problème persiste sur WebRTC, nous invitons les agents à se déconnecter puis se reconnecter jusqu'à ce qu'un numéro soit alloué ; le service sera alors rétabli. EN : If agents are still experiencing WebRTC issues, please log out and log back in until a number is successfully allocated.
- identified Apr 20, 2026, 02:54 PM UTC
FR : Le délai de résolution est estimé à 30 minutes, soit aux alentours de 17h20 (heure de Paris). Veuillez nous excuser pour la gêne occasionnée. EN : Estimated time to resolution is 30 minutes (approx. 5:20 PM Paris time). We apologize for any inconvenience caused.
- monitoring Apr 20, 2026, 03:11 PM UTC
FR : La plupart des services sont désormais rétablis. Des instabilités persistent sur le WebRTC (problèmes d'allocation de numéros). Solution de contournement : Si un agent rencontre ce problème, il doit se déconnecter, patienter 1 minute, puis se reconnecter. Cette manipulation permet de forcer une nouvelle allocation de numéro. EN : Most services are now back online. Residual issues persist regarding WebRTC (number allocation failures). Workaround: If an agent is affected, please log out, wait 1 minute, and log back in. This will trigger a new number allocation.
- monitoring Apr 20, 2026, 03:46 PM UTC
We are continuing to monitor for any further issues.
- resolved Apr 20, 2026, 03:48 PM UTC
FR : L'incident est désormais résolu. Tous les services sont pleinement opérationnels. Note : Si vous constatez encore une anomalie, une dernière déconnexion/reconnexion peut être nécessaire pour finaliser le rétablissement. Un rapport d'incident complet sera fourni dès qu'il nous aura été transmis. EN : All systems are now operational. All services are fully restored. Note: If you still experience any issues, a final logout/login may be required to refresh your connection. A detailed incident report will be shared as soon as it is available.
Critical April 20, 2026 HDS2 WebRTC Down 3h 37m WebRTC
Started Apr 20, 2026, 12:10 PM UTC· resolved Apr 20, 2026, 03:48 PM UTC
- identified Apr 20, 2026, 12:10 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 20, 2026, 12:13 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Apr 20, 2026, 12:22 PM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 20, 2026, 01:46 PM UTC
WebRTC connections are currently unstable, with intermittent WebSocket disconnections causing brief spinner displays in the agent interface before automatic recovery. All other services have now been restored.
- identified Apr 20, 2026, 02:08 PM UTC
🇫🇷 Mise à jour Le service IMAP est désormais totalement stabilisé : la récupération des emails fonctionne à nouveau normalement et sans délai. Le service WebRTC est également rétabli, mais peut nécessiter encore quelques minutes pour se stabiliser complètement en raison du volume élevé de connexions simultanées. Le seul point restant concerne des déconnexions WebSocket intermittentes, pouvant entraîner des problèmes de connexion sur l’interface agent ; nos équipes techniques sont actuellement mobilisées pour résoudre ce sujet. 🇬🇧 Update IMAP is now fully stabilized: email retrieval is working normally again without delays. WebRTC has also recovered, although it may take a few more minutes to fully stabilize due to high concurrent traffic. The only remaining issue is intermittent WebSocket disconnections, which may cause connection issues on the agent interface; our technical team is actively working on resolving it.
- identified Apr 20, 2026, 02:32 PM UTC
FR : Si le problème persiste sur WebRTC, nous invitons les agents à se déconnecter puis se reconnecter jusqu'à ce qu'un numéro soit alloué ; le service sera alors rétabli. EN : If agents are still experiencing WebRTC issues, please log out and log back in until a number is successfully allocated.
- identified Apr 20, 2026, 02:54 PM UTC
FR : Le délai de résolution est estimé à 30 minutes, soit aux alentours de 17h20 (heure de Paris). Veuillez nous excuser pour la gêne occasionnée. EN : Estimated time to resolution is 30 minutes (approx. 5:20 PM Paris time). We apologize for any inconvenience caused.
- monitoring Apr 20, 2026, 03:10 PM UTC
FR : La plupart des services sont désormais rétablis. Des instabilités persistent sur le WebRTC (problèmes d'allocation de numéros). Solution de contournement : Si un agent rencontre ce problème, il doit se déconnecter, patienter 1 minute, puis se reconnecter. Cette manipulation permet de forcer une nouvelle allocation de numéro. EN : Most services are now back online. Residual issues persist regarding WebRTC (number allocation failures). Workaround: If an agent is affected, please log out, wait 1 minute, and log back in. This will trigger a new number allocation.
- monitoring Apr 20, 2026, 03:46 PM UTC
We are continuing to monitor for any further issues.
- resolved Apr 20, 2026, 03:48 PM UTC
FR : L'incident est désormais résolu. Tous les services sont pleinement opérationnels. Note : Si vous constatez encore une anomalie, une dernière déconnexion/reconnexion peut être nécessaire pour finaliser le rétablissement. Un rapport d'incident complet sera fourni dès qu'il nous aura été transmis. EN : All systems are now operational. All services are fully restored. Note: If you still experience any issues, a final logout/login may be required to refresh your connection. A detailed incident report will be shared as soon as it is available.
Critical April 20, 2026 Half of french platforms are down 4h 14m Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls, Voice - Inbound calls and 146 more
Started Apr 20, 2026, 11:33 AM UTC· resolved Apr 20, 2026, 03:47 PM UTC
- investigating Apr 20, 2026, 11:33 AM UTC
We are currently investigating this issue.
- identified Apr 20, 2026, 11:34 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 20, 2026, 11:35 AM UTC
Problem resolved, on monitoring.
- identified Apr 20, 2026, 11:54 AM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 20, 2026, 12:06 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 20, 2026, 12:08 PM UTC
Services is recovered except WebRTC
- identified Apr 20, 2026, 12:13 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 20, 2026, 12:24 PM UTC
If the problem persists, ask the affected agents to log out and log back in. Si le problème persiste, demandez aux agents affectés de se déconnecter et ensuite de se reconnecter.
- identified Apr 20, 2026, 12:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 20, 2026, 12:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 20, 2026, 12:45 PM UTC
Downtime of our services again We apologize for any inconvenience this may cause
- identified Apr 20, 2026, 01:44 PM UTC
The platforms are now accessible again, and emails will gradually start coming through again; however, there are still some issues with WebRTC and slow performances. We apologize for the inconvenience.
- identified Apr 20, 2026, 02:09 PM UTC
🇫🇷 Mise à jour Le service IMAP est désormais totalement stabilisé : la récupération des emails fonctionne à nouveau normalement et sans délai. Le service WebRTC est également rétabli, mais peut nécessiter encore quelques minutes pour se stabiliser complètement en raison du volume élevé de connexions simultanées. Le seul point restant concerne des déconnexions WebSocket intermittentes, pouvant entraîner des problèmes de connexion sur l’interface agent ; nos équipes techniques sont actuellement mobilisées pour résoudre ce sujet. 🇬🇧 Update IMAP is now fully stabilized: email retrieval is working normally again without delays. WebRTC has also recovered, although it may take a few more minutes to fully stabilize due to high concurrent traffic. The only remaining issue is intermittent WebSocket disconnections, which may cause connection issues on the agent interface; our technical team is actively working on resolving it.
- identified Apr 20, 2026, 02:32 PM UTC
FR : Si le problème persiste sur WebRTC, nous invitons les agents à se déconnecter puis se reconnecter jusqu'à ce qu'un numéro soit alloué ; le service sera alors rétabli. EN : If agents are still experiencing WebRTC issues, please log out and log back in until a number is successfully allocated.
- identified Apr 20, 2026, 02:54 PM UTC
FR : Le délai de résolution est estimé à 30 minutes, soit aux alentours de 17h20 (heure de Paris). Veuillez nous excuser pour la gêne occasionnée. EN : Estimated time to resolution is 30 minutes (approx. 5:20 PM Paris time). We apologize for any inconvenience caused.
- identified Apr 20, 2026, 03:04 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 20, 2026, 03:06 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 20, 2026, 03:07 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 20, 2026, 03:10 PM UTC
FR : La plupart des services sont désormais rétablis. Des instabilités persistent sur le WebRTC (problèmes d'allocation de numéros). Solution de contournement : Si un agent rencontre ce problème, il doit se déconnecter, patienter 1 minute, puis se reconnecter. Cette manipulation permet de forcer une nouvelle allocation de numéro. EN : Most services are now back online. Residual issues persist regarding WebRTC (number allocation failures). Workaround: If an agent is affected, please log out, wait 1 minute, and log back in. This will trigger a new number allocation.
- monitoring Apr 20, 2026, 03:45 PM UTC
We are continuing to monitor for any further issues.
- resolved Apr 20, 2026, 03:47 PM UTC
FR : L'incident est désormais résolu. Tous les services, y compris le WebRTC, sont pleinement opérationnels. Un rapport d'incident complet (Post-Mortem) sera mis à disposition dès qu'il nous aura été transmis par nos équipes techniques. Merci de votre patience. EN : All systems are now operational. All services, including WebRTC, are fully restored. A detailed incident report (RCA) will be provided as soon as it is received from our technical teams. Thank you for your patience.
Notice April 13, 2026 API Diabolocom AI 3h 13m Delays on call transcriptions, Call summary generation, IVR - AI Recording Processor Block, IVR - Quality Monitoring Block and 10 more
Started Apr 13, 2026, 12:45 PM UTC· resolved Apr 13, 2026, 03:58 PM UTC
- monitoring Apr 13, 2026, 12:45 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 13, 2026, 03:58 PM UTC
This incident has been resolved.
Critical April 1, 2026 Agent assist Down 18m Agent Assist - AI Assist Chatbot
Started Apr 01, 2026, 01:23 PM UTC· resolved Apr 01, 2026, 01:41 PM UTC
- investigating Apr 01, 2026, 01:23 PM UTC
We are currently investigating this issue.
- monitoring Apr 01, 2026, 01:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 01, 2026, 01:41 PM UTC
This incident has been resolved.