Historial de interrupciones de Commpeak

1. 26 de agosto de 2026 a las 7:56 UTCinvestigating

   Actualmente estamos experimentando una perturbación que afecta a varios servicios de CommPeak, incluyendo [Bolje de voz / SIP, SMS, provisión de DID, Dialer, Portal de cliente, API]. Durante este período, puede ver [intentos de llamadas fallidos, entrega de mensajes retardados, errores de inicio de sesión de portal, timeouts de API]. Nuestro equipo de ingeniería identificó el tema en [07:34 UTC] y está trabajando activamente en restaurar el servicio completo. Esta es nuestra máxima prioridad, y tenemos a todos los equipos pertinentes comprometidos. Publicaremos la siguiente actualización por [08:15 UTC], o antes si la situación cambia. Comprendemos el impacto que esto tiene en sus operaciones, y sentimos la interrupción. Para preguntas específicas de la cuenta, comuníquese con su administrador de cuenta o [email protected].

2. 26 de agosto de 2026 a las 8:00 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 5 de diciembre de 2025 a las 9:12 UTCinvestigating

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

2. 5 de diciembre de 2025 a las 9:17 UTCmonitoring

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

3. 5 de diciembre de 2025 a las 9:23 UTCresolved

   This incident has been resolved

1. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 12:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 17:53 UTCresolved

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

1. 4 de agosto de 2025 a las 10:10 UTCinvestigating

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

2. 4 de agosto de 2025 a las 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 de agosto de 2025 a las 12:17 UTCmonitoring

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

4. 5 de agosto de 2025 a las 6:13 UTCresolved

   This incident has been resolved.

1. 17 de julio de 2025 a las 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 de julio de 2025 a las 16:05 UTCidentified

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

3. 17 de julio de 2025 a las 17:08 UTCresolved

   This incident has been resolved.

1. 30 de junio de 2025 a las 7: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 de junio de 2025 a las 10:01 UTCresolved

   The incident has been resolved.

1. 29 de agosto de 2024 a las 4:46 UTCidentified

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

2. 29 de agosto de 2024 a las 6:24 UTCmonitoring

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

3. 29 de agosto de 2024 a las 7:01 UTCresolved

   This incident has been resolved.

1. 5 de agosto de 2024 a las 8:14 UTCinvestigating

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

2. 5 de agosto de 2024 a las 8:41 UTCresolved

   This incident has been resolved.

1. 22 de febrero de 2024 a las 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 de febrero de 2024 a las 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 de febrero de 2024 a las 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 de febrero de 2024 a las 9:17 UTCinvestigating

   We are currently investigating this issue.

2. 20 de febrero de 2024 a las 10:31 UTCresolved

   This incident has been resolved.

1. 30 de octubre de 2023 a las 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 de octubre de 2023 a las 20:35 UTCidentified

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

3. 30 de octubre de 2023 a las 20:39 UTCresolved

   This incident has been resolved.

1. 4 de octubre de 2023 a las 11:02 UTCinvestigating

   We are currently investigating this issue.

2. 4 de octubre de 2023 a las 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 de octubre de 2023 a las 13:00 UTCmonitoring

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

4. 8 de octubre de 2023 a las 9:37 UTCresolved

   This incident has been resolved.

1. 24 de agosto de 2023 a las 10:20 UTCinvestigating

   We are currently investigating this issue.

2. 24 de agosto de 2023 a las 10:51 UTCidentified

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

3. 24 de agosto de 2023 a las 10:53 UTCmonitoring

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

4. 24 de agosto de 2023 a las 10:54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 de agosto de 2023 a las 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 de agosto de 2023 a las 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 de agosto de 2023 a las 15:15 UTCmonitoring

   We applied a developed workaround and monitoring the results.

8. 25 de agosto de 2023 a las 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 de noviembre de 2022 a las 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 de noviembre de 2022 a las 18:01 UTCidentified

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

3. 8 de noviembre de 2022 a las 18:09 UTCmonitoring

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

4. 8 de noviembre de 2022 a las 18:10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 de noviembre de 2022 a las 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 de agosto de 2022 a las 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 de agosto de 2022 a las 16:03 UTCresolved

   This incident has been resolved.

3. 30 de agosto de 2022 a las 8: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 de julio de 2022 a las 9:21 UTCinvestigating

   We are currently investigating this issue.

2. 12 de julio de 2022 a las 9:26 UTCidentified

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

3. 12 de julio de 2022 a las 9:32 UTCmonitoring

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

4. 12 de julio de 2022 a las 10:30 UTCresolved

   This incident has been resolved.

1. 28 de junio de 2022 a las 14:32 UTCidentified

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

2. 28 de junio de 2022 a las 14:52 UTCresolved

   This incident has been resolved.

1. 21 de junio de 2022 a las 6: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 de junio de 2022 a las 7:07 UTCidentified

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

3. 21 de junio de 2022 a las 7:32 UTCmonitoring

   A fix was applied, we are monitoring the result.

4. 21 de junio de 2022 a las 8:15 UTCresolved

   This incident has been resolved.

1. 30 de abril de 2022 a las 16:14 UTCinvestigating

   Our Skype and Telegram to Live Chat bridges are experiencing an outage. Please use our Live Chat or our support e-mail for technical support.

2. 30 de abril de 2022 a las 16:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 de mayo de 2022 a las 16:19 UTCinvestigating

   Our support is unreachable via Skype and Telegram. Please reach out via our Live Chat and/or by support e-mail. We are still working to solve this matter.

4. 4 de mayo de 2022 a las 15:22 UTCresolved

   This incident has been resolved.

1. 29 de marzo de 2022 a las 12:09 UTCmonitoring

   Datacenter technical issue occurred with one of our datacenters in Europe, affecting our Dialer services. We have recovered from the incident and we are currently monitoring the failed component.

2. 29 de marzo de 2022 a las 12:21 UTCidentified

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

3. 29 de marzo de 2022 a las 12:39 UTCresolved

   This incident has been resolved.