Diabolocom Outage History

Diabolocom is up right now

There were 10 Diabolocom outages since February 16, 2026 totaling 19h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.diabolocom.com

Critical April 20, 2026

ODD Plateforms Down

Detected by Pingoru
Apr 20, 2026, 12:50 PM UTC
Resolved
Apr 20, 2026, 03:48 PM UTC
Duration
2h 58m
Affected: Plateform accessPlateform AccessPlateform AccessPlateform AccessPlateform accessPlateform Access
Timeline · 8 updates
  1. 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

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. monitoring Apr 20, 2026, 03:46 PM UTC

    We are continuing to monitor for any further issues.

  8. 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.

Read the full incident report →

Critical April 20, 2026

HDS2 WebRTC Down

Detected by Pingoru
Apr 20, 2026, 12:10 PM UTC
Resolved
Apr 20, 2026, 03:48 PM UTC
Duration
3h 37m
Affected: WebRTC
Timeline · 10 updates
  1. identified Apr 20, 2026, 12:10 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 20, 2026, 12:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Apr 20, 2026, 12:22 PM UTC

    The issue has been identified and a fix is being implemented.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. monitoring Apr 20, 2026, 03:46 PM UTC

    We are continuing to monitor for any further issues.

  10. 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.

Read the full incident report →

Critical April 20, 2026

Half of french platforms are down

Detected by Pingoru
Apr 20, 2026, 11:33 AM UTC
Resolved
Apr 20, 2026, 03:47 PM UTC
Duration
4h 14m
Affected: Voice - Inbound callsVoice - Inbound callsVoice - Inbound callsVoice - Inbound callsVoice - Inbound callsVoice - Inbound callsVoice - Inbound callsVoice - Manual outbound callsVoice - Manual outbound callsVoice - Manual outbound callsVoice - Manual outbound callsVoice - Manual outbound callsVoice - Inbound callsVoice - Campaign callsVoice - Campaign callsVoice - Campaign callsVoice - Campaign callsVoice - Campaign callsVoice - Manual outbound callsMail - InboundMail - InboundMail - InboundMail - InboundMail - InboundVoice - Campaign callsMail - OutboundMail - OutboundMail - OutboundMail - OutboundMail - OutboundMail - InboundWebRTCWebRTCWebRTCWebRTCWebRTCWebRTCWebRTCWebRTCMail - OutboundSupervisionSupervisionSupervisionSupervisionSupervisionWebRTCWallboardsWallboardsWallboardsWallboardsWallboardsSupervisionReportsReportsReportsReportsReportsWallboardsSFTPSFTPSFTPSFTPSFTPReportsCall scriptsCall scriptsCall scriptsCall scriptsCall scriptsSFTPREST APIsREST APIsREST APIsREST APIsREST APIsCall scriptsAgent interfaceAgent interfaceAgent interfaceAgent interfaceAgent interfaceAgent interfaceStandard CTIStandard CTIStandard CTIStandard CTIStandard CTIStandard CTISalesforce integrationSalesforce integrationSalesforce integrationSalesforce integrationSalesforce integrationSalesforce integrationMS Dynamics integrationMS Dynamics integrationMS Dynamics integrationMS Dynamics integrationMS Dynamics integrationMS Dynamics integrationOracle integrationOracle integrationOracle integrationOracle integrationOracle integrationZendesk integrationZendesk integrationZendesk integrationZendesk integrationZendesk integrationZendesk integrationRecordingsHubspot integrationHubspot integrationHubspot integrationHubspot integrationHubspot integrationScenarioSAP integrationSAP integrationSAP integrationSAP integrationSAP integrationPlateform AccessServiceNow integrationServiceNow integrationServiceNow integrationServiceNow integrationServiceNow integrationFR12RecordingsRecordingsRecordingsRecordingsRecordingsPlateform AccessPlateform AccessPlateform AccessPlateform accessPlateform AccessScenarioScenarioScenarioScenarioScenarioFR2FR4FR6FR8FR10
Timeline · 21 updates
  1. investigating Apr 20, 2026, 11:33 AM UTC

    We are currently investigating this issue.

  2. identified Apr 20, 2026, 11:34 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 20, 2026, 11:35 AM UTC

    Problem resolved, on monitoring.

  4. identified Apr 20, 2026, 11:54 AM UTC

    The issue has been identified and a fix is being implemented.

  5. identified Apr 20, 2026, 12:06 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Apr 20, 2026, 12:08 PM UTC

    Services is recovered except WebRTC

  7. identified Apr 20, 2026, 12:13 PM UTC

    We are continuing to work on a fix for this issue.

  8. 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.

  9. identified Apr 20, 2026, 12:35 PM UTC

    We are continuing to work on a fix for this issue.

  10. identified Apr 20, 2026, 12:35 PM UTC

    We are continuing to work on a fix for this issue.

  11. identified Apr 20, 2026, 12:45 PM UTC

    Downtime of our services again We apologize for any inconvenience this may cause

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. identified Apr 20, 2026, 03:04 PM UTC

    We are continuing to work on a fix for this issue.

  17. identified Apr 20, 2026, 03:06 PM UTC

    We are continuing to work on a fix for this issue.

  18. monitoring Apr 20, 2026, 03:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  19. 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.

  20. monitoring Apr 20, 2026, 03:45 PM UTC

    We are continuing to monitor for any further issues.

  21. 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.

Read the full incident report →

Notice April 13, 2026

API Diabolocom AI

Detected by Pingoru
Apr 13, 2026, 12:45 PM UTC
Resolved
Apr 13, 2026, 03:58 PM UTC
Duration
3h 13m
Affected: Delays on call transcriptionsCall summary generationIVR - AI Recording Processor BlockIVR - Quality Monitoring BlockAgent Assist - Real-time call transcriptionAgent Assist - Dynamic form completionAgent Assist - AI Assist ChatbotQuality Monitoring - Back-officeQuality Monitoring - Grid applicationQuality Monitoring - TriggersQuality Monitoring - Import systemAI - APIsAgent Assist - Uploading documents to the interfaceQuality Monitoring - Ingestion SFTP
Timeline · 2 updates
  1. monitoring Apr 13, 2026, 12:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Apr 13, 2026, 03:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 1, 2026

Agent assist Down

Detected by Pingoru
Apr 01, 2026, 01:23 PM UTC
Resolved
Apr 01, 2026, 01:41 PM UTC
Duration
18m
Affected: Agent Assist - AI Assist Chatbot
Timeline · 3 updates
  1. investigating Apr 01, 2026, 01:23 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 01, 2026, 01:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 01, 2026, 01:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 18, 2026

HDS2 WebRTC connection

Detected by Pingoru
Mar 18, 2026, 07:59 AM UTC
Resolved
Mar 18, 2026, 08:25 AM UTC
Duration
25m
Affected: WebRTC
Timeline · 3 updates
  1. identified Mar 18, 2026, 07:59 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Mar 18, 2026, 08:12 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 18, 2026, 08:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 11, 2026

Call distribution issue: unexpected second agent insertion into active calls

Detected by Pingoru
Mar 11, 2026, 11:34 AM UTC
Resolved
Mar 11, 2026, 01:14 PM UTC
Duration
1h 39m
Affected: Voice - Inbound callsVoice - Inbound calls
Timeline · 3 updates
  1. investigating Mar 11, 2026, 11:34 AM UTC

    Français : Nous enquêtons sur une anomalie de distribution automatique provoquant l'ajout inattendu d'un second agent en conférence sur un appel déjà actif. English: We are investigating an automated routing anomaly causing a second agent to be unexpectedly conferenced into an already active call.

  2. monitoring Mar 11, 2026, 12:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 11, 2026, 01:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 26, 2026

Plateform access and connection

Detected by Pingoru
Feb 26, 2026, 10:17 AM UTC
Resolved
Feb 26, 2026, 10:45 AM UTC
Duration
28m
Affected: Plateform AccessPlateform AccessPlateform Access
Timeline · 3 updates
  1. investigating Feb 26, 2026, 10:17 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 26, 2026, 10:24 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 26, 2026, 10:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 16, 2026

WebRTC connection issue

Detected by Pingoru
Feb 16, 2026, 02:29 PM UTC
Resolved
Feb 15, 2026, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 16, 2026, 02:29 PM UTC

    Certains agents ont pu rencontré des problèmes de connection au niveau du WebRTC durant la période de l'incident Some agents may have experienced connection issues with WebRTC during the incident.

Read the full incident report →

Critical February 16, 2026

Plateform access

Detected by Pingoru
Feb 16, 2026, 10:48 AM UTC
Resolved
Feb 16, 2026, 01:14 PM UTC
Duration
2h 26m
Affected: Plateform AccessPlateform Access
Timeline · 3 updates
  1. investigating Feb 16, 2026, 10:48 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 16, 2026, 11:03 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 16, 2026, 01:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Diabolocom downtime and outages?

Pingoru polls Diabolocom's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Diabolocom reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Diabolocom alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Diabolocom for free

5 free monitors · No credit card required