История сбоев Commpeak

1. 6 октября 2026 г. в 11:54 UTCidentified

   После недавнего планового технического обслуживания PBX Stas мы наблюдаем неожиданные побочные эффекты, влияющие на небольшой процент запросов. Наша инженерная команда активно исследует первопричину и развертывает исправление. Голосовые службы и основные функции остаются в рабочем состоянии, но некоторые пользователи могут испытывать периодические задержки.

2. 6 октября 2026 г. в 11:58 UTCresolved

   Проблемы с производительностью, затрагивающие PBX Stas после запланированного технического обслуживания, были полностью решены. Время отклика и обработка запросов вернулись к нормальным рабочим параметрам. Наша команда будет внимательно следить за стабильностью системы. Мы ценим ваше терпение, пока мы работали над решением этой проблемы.

Автоматический перевод официального обновления инцидента.

1. 22 сентября 2026 г. в 12:14 UTCidentified

   Мы испытываем временный коммутатор, который может вызвать скомпрометированную производительность в функциональности и производительности вашего коммутатора

2. 22 сентября 2026 г. в 12:16 UTCidentified

   Мы продолжаем работать над решением этой проблемы.

3. 22 сентября 2026 г. в 12:57 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

4. 22 сентября 2026 г. в 13:01 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 26 августа 2026 г. в 07:56 UTCinvestigating

   В настоящее время мы испытываем сбои, затрагивающие несколько сервисов CommPeak, включая [Voice / SIP trunking, SMS, DID provisioning, Dialer, Customer Portal, API]. В течение этого периода вы можете увидеть [неудачные попытки вызова, задержку доставки сообщений, ошибки входа в портал, тайм-ауты API]. Наша инженерная команда определила проблему на [07:34 UTC] и активно работает над восстановлением полного сервиса. Это наш главный приоритет, и мы привлекаем все соответствующие команды. Мы опубликуем следующее обновление к [08:15 UTC], или раньше, если ситуация изменится. Мы понимаем, какое влияние это оказывает на ваши операции, и мы сожалеем о сбое. По вопросам, связанным с учетной записью, пожалуйста, свяжитесь с менеджером вашей учетной записи или [email protected].

2. 26 августа 2026 г. в 08:00 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 5 декабря 2025 г. в 09:12 UTCinvestigating

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

2. 5 декабря 2025 г. в 09:17 UTCmonitoring

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

3. 5 декабря 2025 г. в 09:23 UTCresolved

   This incident has been resolved

1. 18 ноября 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 ноября 2025 г. в 12:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 ноября 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 ноября 2025 г. в 17:53 UTCresolved

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

1. 4 августа 2025 г. в 10:10 UTCinvestigating

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

2. 4 августа 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 августа 2025 г. в 12:17 UTCmonitoring

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

4. 5 августа 2025 г. в 06:13 UTCresolved

   This incident has been resolved.

1. 17 июля 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 июля 2025 г. в 16:05 UTCidentified

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

3. 17 июля 2025 г. в 17:08 UTCresolved

   This incident has been resolved.

1. 30 июня 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 июня 2025 г. в 10:01 UTCresolved

   The incident has been resolved.

1. 29 августа 2024 г. в 04:46 UTCidentified

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

2. 29 августа 2024 г. в 06:24 UTCmonitoring

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

3. 29 августа 2024 г. в 07:01 UTCresolved

   This incident has been resolved.

1. 5 августа 2024 г. в 08:14 UTCinvestigating

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

2. 5 августа 2024 г. в 08:41 UTCresolved

   This incident has been resolved.

1. 22 февраля 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 февраля 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 февраля 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 февраля 2024 г. в 09:17 UTCinvestigating

   We are currently investigating this issue.

2. 20 февраля 2024 г. в 10:31 UTCresolved

   This incident has been resolved.

1. 30 октября 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 октября 2023 г. в 20:35 UTCidentified

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

3. 30 октября 2023 г. в 20:39 UTCresolved

   This incident has been resolved.

1. 4 октября 2023 г. в 11:02 UTCinvestigating

   We are currently investigating this issue.

2. 4 октября 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 октября 2023 г. в 13:00 UTCmonitoring

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

4. 8 октября 2023 г. в 09:37 UTCresolved

   This incident has been resolved.

1. 24 августа 2023 г. в 10:20 UTCinvestigating

   We are currently investigating this issue.

2. 24 августа 2023 г. в 10:51 UTCidentified

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

3. 24 августа 2023 г. в 10:53 UTCmonitoring

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

4. 24 августа 2023 г. в 10:54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 августа 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 августа 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 августа 2023 г. в 15:15 UTCmonitoring

   We applied a developed workaround and monitoring the results.

8. 25 августа 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 ноября 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 ноября 2022 г. в 18:01 UTCidentified

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

3. 8 ноября 2022 г. в 18:09 UTCmonitoring

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

4. 8 ноября 2022 г. в 18:10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 ноября 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 августа 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 августа 2022 г. в 16:03 UTCresolved

   This incident has been resolved.

3. 30 августа 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 июля 2022 г. в 09:21 UTCinvestigating

   We are currently investigating this issue.

2. 12 июля 2022 г. в 09:26 UTCidentified

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

3. 12 июля 2022 г. в 09:32 UTCmonitoring

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

4. 12 июля 2022 г. в 10:30 UTCresolved

   This incident has been resolved.

1. 28 июня 2022 г. в 14:32 UTCidentified

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

2. 28 июня 2022 г. в 14:52 UTCresolved

   This incident has been resolved.

1. 21 июня 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 июня 2022 г. в 07:07 UTCidentified

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

3. 21 июня 2022 г. в 07:32 UTCmonitoring

   A fix was applied, we are monitoring the result.

4. 21 июня 2022 г. в 08:15 UTCresolved

   This incident has been resolved.