- Detected by Pingoru
- Jun 01, 2026, 08:46 AM UTC
- Resolved
- Jun 01, 2026, 09:31 AM UTC
- Duration
- 45m
Affected: DATA
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 12:24 PM UTC
- Resolved
- May 20, 2026, 08:15 AM UTC
- Duration
- 19h 50m
Affected: SFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPSFTPRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordingsRecordings
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 08:28 AM UTC
- Resolved
- May 12, 2026, 10:41 AM UTC
- Duration
- 2h 13m
Affected: Sim Management(Activation,Suspension,...)
Timeline · 3 updates
-
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.
Read the full incident report →
- 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
Read the full incident report →
- 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
Read the full incident report →
- 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
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
identified Mar 18, 2026, 07:59 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 18, 2026, 08:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 18, 2026, 08:25 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
monitoring Mar 11, 2026, 12:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 11, 2026, 01:14 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 26, 2026 - 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
-
investigating Feb 26, 2026, 10:17 AM UTC
We are currently investigating this issue.
-
monitoring Feb 26, 2026, 10:24 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 26, 2026, 10:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 02:29 PM UTC
- Resolved
- Feb 15, 2026, 11:00 PM UTC
- Duration
- —
Timeline · 1 update
-
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 - 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
-
investigating Feb 16, 2026, 10:48 AM UTC
We are currently investigating this issue.
-
monitoring Feb 16, 2026, 11:03 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 16, 2026, 01:14 PM UTC
This incident has been resolved.
Read the full incident report →
Critical January 22, 2026 - Detected by Pingoru
- Jan 22, 2026, 11:06 AM UTC
- Resolved
- Jan 22, 2026, 11:24 AM UTC
- Duration
- 18m
Affected: SEPIA API
Timeline · 3 updates
-
investigating Jan 22, 2026, 11:06 AM UTC
We are currently investigating this issue.
-
monitoring Jan 22, 2026, 11:19 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 22, 2026, 11:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 10:59 AM UTC
- Resolved
- Jan 22, 2026, 11:24 AM UTC
- Duration
- 25m
Affected: Voice Convergence to engageWeb InterfacePublic APIs
Timeline · 4 updates
-
identified Jan 22, 2026, 10:59 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jan 22, 2026, 11:00 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jan 22, 2026, 11:20 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 22, 2026, 11:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 10:52 AM UTC
- Resolved
- Jan 22, 2026, 11:18 AM UTC
- Duration
- 26m
Affected: Call scriptsREST APIsREST APIsREST APIsREST APIs
Timeline · 3 updates
-
identified Jan 22, 2026, 10:52 AM UTC
Issue identified, rollback in progress Estimated time : 30 min Problème identifié , rollback en cours Temps estimé : 30 min
-
monitoring Jan 22, 2026, 11:14 AM UTC
Rollback done for FR1/3/5/7/11/12
-
resolved Jan 22, 2026, 11:18 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 03:24 PM UTC
- Resolved
- Jan 22, 2026, 08:46 AM UTC
- Duration
- 17h 22m
Affected: Voice Convergence to engage
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jan 17, 2026, 04:30 AM UTC
- Resolved
- Jan 17, 2026, 04:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 26, 2026, 10:26 AM UTC
5 h 30, la base de données sur la plateforme HDS2 a subi une panne complète. Elle a été restaurée à 6 h 30.Cependant, nous avons découvert par la suite que la panne avait provoqué une incohérence interne dans le système de base de données. Même si la base de données principale a été restaurée correctement, la base de données secondaire ne s'est pas connectée correctement et a continué à se comporter comme si elle était également la base principale. En conséquence, les données entre les deux bases n'étaient pas synchronisées. De ce fait, certains de nos services ont pu enregistrer de nouvelles données, mais n'ont pas toujours été en mesure de lire les informations les plus récentes. Cela a conduit à la restitution de données incorrectes ou manquantes par ces services.Le problème a été entièrement identifié et résolu, et le fonctionnement normal a été complètement rétabli à 16h39.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:46 PM UTC
- Resolved
- Jan 16, 2026, 03:47 PM UTC
- Duration
- 1m
Affected: Test API
Timeline · 4 updates
-
investigating Jan 16, 2026, 03:46 PM UTC
We are currently investigating this issue.
-
identified Jan 16, 2026, 03:46 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jan 16, 2026, 03:47 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 16, 2026, 03:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:43 PM UTC
- Resolved
- Jan 16, 2026, 03:44 PM UTC
- Duration
- 1m
Affected: Test API
Timeline · 2 updates
-
investigating Jan 16, 2026, 03:43 PM UTC
We are currently investigating this issue.
-
resolved Jan 16, 2026, 03:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:32 PM UTC
- Resolved
- Jan 16, 2026, 03:37 PM UTC
- Duration
- 5m
Affected: Test API
Timeline · 2 updates
-
investigating Jan 16, 2026, 03:32 PM UTC
We are currently investigating this issue.
-
resolved Jan 16, 2026, 03:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 03:20 PM UTC
- Resolved
- Jan 16, 2026, 03:26 PM UTC
- Duration
- 5m
Affected: Test API
Timeline · 2 updates
-
monitoring Jan 16, 2026, 03:20 PM UTC
We are currently testing new ways to inform you about incidents
-
resolved Jan 16, 2026, 03:26 PM UTC
This is the message you will receive once the incident is solved
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 04:22 PM UTC
- Resolved
- Jan 06, 2026, 04:43 PM UTC
- Duration
- 21m
Affected: Test API
Timeline · 2 updates
-
investigating Jan 06, 2026, 04:22 PM UTC
We are currently investigating this issue.
-
resolved Jan 06, 2026, 04:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 22, 2025, 08:51 AM UTC
- Resolved
- Dec 22, 2025, 12:29 PM UTC
- Duration
- 3h 37m
Affected: Voice - Inbound callsVoice - Manual outbound callsVoice - Campaign calls
Timeline · 3 updates
-
investigating Dec 22, 2025, 08:51 AM UTC
We are currently investigating this issue.
-
monitoring Dec 22, 2025, 10:57 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 22, 2025, 12:29 PM UTC
This incident has been resolved.
Read the full incident report →
Critical December 3, 2025 - Detected by Pingoru
- Dec 03, 2025, 09:11 AM UTC
- Resolved
- Dec 03, 2025, 09:47 AM UTC
- Duration
- 36m
Affected: Support access
Timeline · 7 updates
-
investigating Dec 03, 2025, 09:22 AM UTC
We are currently investigating this issue.
-
investigating Dec 03, 2025, 09:27 AM UTC
We are continuing to investigate this issue.
-
identified Dec 03, 2025, 09:28 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Dec 03, 2025, 09:35 AM UTC
A fix has been implemented and we are monitoring the results. Please note that you may need to log out and log back in to access WebRTC.
-
monitoring Dec 03, 2025, 09:40 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Dec 03, 2025, 09:45 AM UTC
We are continuing to monitor for any further issues.
-
resolved Dec 03, 2025, 09:47 AM UTC
This incident has been resolved.
Read the full incident report →
