Histórico de interrupções do Commpeak

1. 6 Here 2026 da 11:54 UTCidentified

   Após nossa recente manutenção programada em PBX Stas, estamos observando efeitos colaterais inesperados impactando uma pequena porcentagem de solicitações, resultando em tempos de resposta elevados. A nossa equipa de engenharia está a investigar a causa raiz e a implantar uma solução. Os serviços de voz e as características primárias permanecem operacionais, mas alguns usuários podem ter atrasos intermitentes.

2. 6 Here 2026 da 11:58 UTCresolved

   Os problemas de desempenho que afetam o PBX Stas após nossa manutenção programada foram totalmente resolvidos. Os tempos de resposta e o processamento da solicitação retornaram aos parâmetros operacionais normais. A nossa equipa continuará a monitorizar de perto a estabilidade do sistema. Agradecemos a sua paciência enquanto trabalhávamos para resolver esta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gwengolo 2026 da 12:14 UTCidentified

   Estamos experimentando um discador temporário que pode causar um desempenho comprometido em sua funcionalidade e desempenho do discador

2. 22 Gwengolo 2026 da 12:16 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 22 Gwengolo 2026 da 12:57 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 22 Gwengolo 2026 da 13:01 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 07:56 UTCinvestigating

   Atualmente, estamos passando por uma perturbação que afeta vários serviços de CommPeak, incluindo [Voice / SIP trunking, SMS, provisionamento DID, Dialer, Portal do Cliente, API]. Durante este período, você pode ver [tentativas de chamada falhadas, entrega de mensagens atrasadas, erros de login do portal, timeouts de API]. Nossa equipe de engenharia identificou a questão em [07:34 UTC] e está trabalhando ativamente para restaurar o serviço completo. Esta é a nossa prioridade, e temos todas as equipas envolvidas. Publicaremos a próxima atualização por [08:15 UTC], ou mais cedo se a situação mudar. Compreendemos o impacto que isto tem nas vossas operações, e lamentamos a interrupção. Para perguntas específicas da conta, entre em contato com seu gerente de conta ou [email protected].

2. 26 Eost 2026 da 08:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 5 Kerzu 2025 da 09:12 UTCinvestigating

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

2. 5 Kerzu 2025 da 09:17 UTCmonitoring

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

3. 5 Kerzu 2025 da 09:23 UTCresolved

   This incident has been resolved

1. 18 Du 2025 da 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 Du 2025 da 12:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 Du 2025 da 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 Du 2025 da 17:53 UTCresolved

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

1. 4 Eost 2025 da 10:10 UTCinvestigating

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

2. 4 Eost 2025 da 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 Eost 2025 da 12:17 UTCmonitoring

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

4. 5 Eost 2025 da 06:13 UTCresolved

   This incident has been resolved.

1. 17 Gouere 2025 da 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 Gouere 2025 da 16:05 UTCidentified

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

3. 17 Gouere 2025 da 17:08 UTCresolved

   This incident has been resolved.

1. 30 Mezheven 2025 da 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 Mezheven 2025 da 10:01 UTCresolved

   The incident has been resolved.

1. 29 Eost 2024 da 04:46 UTCidentified

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

2. 29 Eost 2024 da 06:24 UTCmonitoring

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

3. 29 Eost 2024 da 07:01 UTCresolved

   This incident has been resolved.

1. 5 Eost 2024 da 08:14 UTCinvestigating

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

2. 5 Eost 2024 da 08:41 UTCresolved

   This incident has been resolved.

1. 22 Cʼhwevrer 2024 da 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 Cʼhwevrer 2024 da 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 Cʼhwevrer 2024 da 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 Cʼhwevrer 2024 da 09:17 UTCinvestigating

   We are currently investigating this issue.

2. 20 Cʼhwevrer 2024 da 10:31 UTCresolved

   This incident has been resolved.

1. 30 Here 2023 da 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 Here 2023 da 20:35 UTCidentified

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

3. 30 Here 2023 da 20:39 UTCresolved

   This incident has been resolved.

1. 4 Here 2023 da 11:02 UTCinvestigating

   We are currently investigating this issue.

2. 4 Here 2023 da 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 Here 2023 da 13:00 UTCmonitoring

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

4. 8 Here 2023 da 09:37 UTCresolved

   This incident has been resolved.

1. 24 Eost 2023 da 10:20 UTCinvestigating

   We are currently investigating this issue.

2. 24 Eost 2023 da 10:51 UTCidentified

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

3. 24 Eost 2023 da 10:53 UTCmonitoring

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

4. 24 Eost 2023 da 10:54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 Eost 2023 da 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 Eost 2023 da 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 Eost 2023 da 15:15 UTCmonitoring

   We applied a developed workaround and monitoring the results.

8. 25 Eost 2023 da 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 Du 2022 da 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 Du 2022 da 18:01 UTCidentified

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

3. 8 Du 2022 da 18:09 UTCmonitoring

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

4. 8 Du 2022 da 18:10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 Du 2022 da 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 Eost 2022 da 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 Eost 2022 da 16:03 UTCresolved

   This incident has been resolved.

3. 30 Eost 2022 da 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 Gouere 2022 da 09:21 UTCinvestigating

   We are currently investigating this issue.

2. 12 Gouere 2022 da 09:26 UTCidentified

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

3. 12 Gouere 2022 da 09:32 UTCmonitoring

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

4. 12 Gouere 2022 da 10:30 UTCresolved

   This incident has been resolved.

1. 28 Mezheven 2022 da 14:32 UTCidentified

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

2. 28 Mezheven 2022 da 14:52 UTCresolved

   This incident has been resolved.

1. 21 Mezheven 2022 da 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 Mezheven 2022 da 07:07 UTCidentified

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

3. 21 Mezheven 2022 da 07:32 UTCmonitoring

   A fix was applied, we are monitoring the result.

4. 21 Mezheven 2022 da 08:15 UTCresolved

   This incident has been resolved.