Historique des pannes de Commpeak

1. 6 octobre 2026 à 11:54 UTCidentified

   Suite à notre récent entretien programmé sur PBX Stas, nous observons des effets secondaires inattendus qui touchent un petit pourcentage de demandes, entraînant des temps de réponse élevés. Notre équipe d'ingénierie enquête activement sur la cause fondamentale et déploie une solution. Les services téléphoniques et les fonctions primaires demeurent opérationnels, mais certains utilisateurs peuvent subir des retards intermittents.

2. 6 octobre 2026 à 11:58 UTCresolved

   Les problèmes de performance affectant PBX Stas après notre maintenance programmée ont été entièrement résolus. Les temps de réponse et le traitement des demandes sont revenus aux paramètres d'exploitation normaux. Notre équipe continuera de surveiller de près la stabilité du système. Nous apprécions votre patience tout en travaillant à résoudre ce problème.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 septembre 2026 à 12:14 UTCidentified

   Nous sommes en train de vivre une composition temporaire qui peut causer une performance compromise dans votre fonctionnalité de composition et de performance

2. 22 septembre 2026 à 12:16 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

3. 22 septembre 2026 à 12:57 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 22 septembre 2026 à 13:01 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 26 août 2026 à 07:56 UTCinvestigating

   Nous sommes actuellement confrontés à une perturbation affectant plusieurs services CommPeak, y compris [Voice / SIP réseau, SMS, fourniture DID, Dialer, Portail Client, API]. Pendant cette période, vous pouvez voir [ tentatives d'appel échouées, livraison de messages retardée, erreurs de connexion du portail, délais d'API]. Notre équipe d'ingénieurs a identifié le problème à [07:34 UTC] et travaille activement à rétablir le service complet. C'est notre priorité absolue, et nous avons toutes les équipes concernées engagées. Nous publierons la prochaine mise à jour par [08:15 UTC], ou plus tôt si la situation change. Nous comprenons l'impact que cela a sur vos opérations, et nous sommes désolés pour la perturbation. Pour toute question spécifique, veuillez contacter votre responsable de compte ou [email protected].

2. 26 août 2026 à 08:00 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 décembre 2025 à 09:12 UTCinvestigating

   Our team is actively investigating the ongoing outage and working toward a resolution

2. 5 décembre 2025 à 09:17 UTCmonitoring

   The issue originates with our vendor, Cloudflare. They have deployed a fix and are monitoring its effectiveness.

3. 5 décembre 2025 à 09:23 UTCresolved

   This incident has been resolved

1. 18 novembre 2025 à 11:59 UTCinvestigating

   We have confirmed that the issue lies with our third-party provider, Cloudflare. While they proceed with remediation, our team is researching alternative means to bypass the dependency.

2. 18 novembre 2025 à 12:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 novembre 2025 à 15:08 UTCmonitoring

   We can see that our third-party provider, Cloudflare, is in the process of recovering, although some issues may still persist. We will continue to monitor the situation closely and are working on a long-term workaround to prevent similar problems in the future. Some of these workarounds have already been implemented, while others are currently in progress.

4. 18 novembre 2025 à 17:53 UTCresolved

   The incident has been resolved and all services are operating normally.

1. 4 août 2025 à 10:10 UTCinvestigating

   We are currently investigating degraded network performance for our infrastructure in European Region.

2. 4 août 2025 à 10:42 UTCidentified

   There is an issue with one of our vendors Cloudflare. The scope of the impact is affecting european network. The fix is being implemented.

3. 4 août 2025 à 12:17 UTCmonitoring

   Cloudflare has mitigated the current impact. We will continue to monitor the network status.

4. 5 août 2025 à 06:13 UTCresolved

   This incident has been resolved.

1. 17 juillet 2025 à 15:32 UTCinvestigating

   We are currently experiencing a major outage affecting our TexPeak. Our engineering team is actively working to resolve the issue as quickly as possible. Thank you for your patience

2. 17 juillet 2025 à 16:05 UTCidentified

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

3. 17 juillet 2025 à 17:08 UTCresolved

   This incident has been resolved.

1. 30 juin 2025 à 07:39 UTCidentified

   We’re currently experiencing a major outage affecting our SMS gateway. Our engineering team is actively working to resolve the issue as quickly as possible. Thank you for your patience

2. 30 juin 2025 à 10:01 UTCresolved

   The incident has been resolved.

1. 29 août 2024 à 04:46 UTCidentified

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

2. 29 août 2024 à 06:24 UTCmonitoring

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

3. 29 août 2024 à 07:01 UTCresolved

   This incident has been resolved.

1. 5 août 2024 à 08:14 UTCinvestigating

   CommPeak is investigating a fault with my.commpeak.com and related services. More updates to follow shortly.

2. 5 août 2024 à 08:41 UTCresolved

   This incident has been resolved.

1. 22 février 2024 à 10:01 UTCidentified

   Our support system provider is currently partially available which affects our support teams operation, we are working in order to provide a backup solution for it. This issue does not affect our services.

2. 22 février 2024 à 11:10 UTCmonitoring

   Our support system provider has informed that the major outage is resolved. Webchat and email support is back to operational. We are continuing to monitor the situation.

3. 22 février 2024 à 13:12 UTCresolved

   Our support system provider has informed that the majority of functionality has been restored to normal. We are fully available at all support channels.

1. 20 février 2024 à 09:17 UTCinvestigating

   We are currently investigating this issue.

2. 20 février 2024 à 10:31 UTCresolved

   This incident has been resolved.

1. 30 octobre 2023 à 20:10 UTCinvestigating

   CommPeak is investigating availability issues with commpeak.com public website. Visitors may encounter errors when attempting to access it. No other services are affected. We are working to mitigate this problem. More updates to follow shortly.

2. 30 octobre 2023 à 20:35 UTCidentified

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

3. 30 octobre 2023 à 20:39 UTCresolved

   This incident has been resolved.

1. 4 octobre 2023 à 11:02 UTCinvestigating

   We are currently investigating this issue.

2. 4 octobre 2023 à 11:13 UTCidentified

   We are having a network issue in the Asia region which affected connectivity between our servers. We are working on the workaround.

3. 4 octobre 2023 à 13:00 UTCmonitoring

   Adjustment has been implemented, and we are monitoring the results.

4. 8 octobre 2023 à 09:37 UTCresolved

   This incident has been resolved.

1. 24 août 2023 à 10:20 UTCinvestigating

   We are currently investigating this issue.

2. 24 août 2023 à 10:51 UTCidentified

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

3. 24 août 2023 à 10:53 UTCmonitoring

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

4. 24 août 2023 à 10:54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 août 2023 à 11:51 UTCmonitoring

   There was a network issue in the Asia region which affected connectivity between our servers. We've detected an increased latency between our servers which caused delays in internal communications between system components. We've applied several workaround solutions and continue to monitor the situation along with working on additional changes in order to prevent this from happening in the future

6. 24 août 2023 à 12:36 UTCmonitoring

   There was a network issue in the Asia region which affected connectivity between our servers. We've detected an increased latency between our servers which caused delays in internal communications between system components. We've applied several workaround solutions and continue to monitor the situation along with working on additional changes in order to prevent this from happening in the futur

7. 24 août 2023 à 15:15 UTCmonitoring

   We applied a developed workaround and monitoring the results.

8. 25 août 2023 à 11:00 UTCresolved

   We've implemented a change on our infrastructure that reduce the load on network and overcomes the issue. We still continue to monitor the situation.

1. 8 novembre 2022 à 17:16 UTCinvestigating

   We are currently investigating the issue. Can be a problem to connect to the CommPeak Softphone and log in to the PBX Stats

2. 8 novembre 2022 à 18:01 UTCidentified

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

3. 8 novembre 2022 à 18:09 UTCmonitoring

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

4. 8 novembre 2022 à 18:10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 novembre 2022 à 18:17 UTCresolved

   This incident has been resolved. Due to a failure in DE-CIX, a Frankfurt-based internet backbone, a severe network interruption has occurred between our two Disaster Recovery data centers, which has triggered an intense load on our databases, making them irresponsive. We are now studying the case in order to prevent this from happening again. DE-CIX has issued emergency maintenance which will happen tonight at 00:00 UTC+1. We are continuing to follow the events and ensure the stability of our services.

1. 29 août 2022 à 15:51 UTCinvestigating

   We are currently investigating the issue. Can be problem to connect to the Commpeak Softphone and log in to the PBX Stats

2. 29 août 2022 à 16:03 UTCresolved

   This incident has been resolved.

3. 30 août 2022 à 08:40 UTCpostmortem

   Between the hours 13:00 UTC and 16:00 UTC on the 29th of August, CommPeak clients that are using CommPeak PBX Stats encountered login problems and performance issues in the system, and issues with the CommPeak Softphone connection. The event was triggered by a new feature that was deployed on the last release and created a performance regression. Our engineering team has identified a performance bottleneck with redis-server and has upgraded the component, that action has achieved partial relief, but the issue was still ongoing. The root source of the bottleneck was identified and fixed at 15:40 UTC. After the hotfix had been released, it released the bottleneck, and services were restored at 16:00 UTC. This incident had a widespread impact, and we take availability very seriously. We have identified several areas of improvement and will continue to work on uncovering any other gaps that could cause a recurrence.

1. 12 juillet 2022 à 09:21 UTCinvestigating

   We are currently investigating this issue.

2. 12 juillet 2022 à 09:26 UTCidentified

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

3. 12 juillet 2022 à 09:32 UTCmonitoring

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

4. 12 juillet 2022 à 10:30 UTCresolved

   This incident has been resolved.

1. 28 juin 2022 à 14:32 UTCidentified

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

2. 28 juin 2022 à 14:52 UTCresolved

   This incident has been resolved.

1. 21 juin 2022 à 06:54 UTCinvestigating

   We are experiencing issues with network connectivity for our systems. We believe this is related to a more widespread outage across the internet and are investigating.

2. 21 juin 2022 à 07:07 UTCidentified

   The issue is related to our CDN provider Cloudflare, we are working on a fix.

3. 21 juin 2022 à 07:32 UTCmonitoring

   A fix was applied, we are monitoring the result.

4. 21 juin 2022 à 08:15 UTCresolved

   This incident has been resolved.