Störungsverlauf von Commpeak

1. 6. Oktober 2026 um 11:54 UTCidentified

   Nach unserer kürzlich geplanten Wartung von PBX-Staps beobachten wir unerwartete Nebenwirkungen, die einen kleinen Prozentsatz der Anfragen betreffen, was zu erhöhten Reaktionszeiten führt. Unser Engineering-Team untersucht aktiv die Ursache und stellt einen Fix bereit. Sprachdienste und primäre Funktionen bleiben funktionsfähig, aber einige Benutzer können intermittierende Verzögerungen auftreten.

2. 6. Oktober 2026 um 11:58 UTCresolved

   Die Leistungsprobleme, die PBX Stas nach unserer geplanten Wartung betreffen, wurden vollständig behoben. Antwortzeiten und Anforderungsverarbeitung sind zu normalen Betriebsparametern zurückgekehrt. Unser Team wird die Systemstabilität weiterhin genau beobachten. Wir schätzen Ihre Geduld, während wir daran gearbeitet haben, dieses Problem zu lösen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. September 2026 um 12:14 UTCidentified

   Wir erleben einen temporären Dialer, der eine kompromittierte Leistung in Ihrer Dialer-Funktionalität und -Leistung verursachen kann

2. 22. September 2026 um 12:16 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 22. September 2026 um 12:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 22. September 2026 um 13:01 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. August 2026 um 07:56 UTCinvestigating

   Wir erleben derzeit eine Störung, die mehrere CommPeak-Dienste betrifft, einschließlich [Voice / SIP-Trunking, SMS, DID-Bereitstellung, Dialer, Kundenportal, API]. Während dieses Zeitraums können Sie [fehlgeschlagene Anrufversuche, verzögerte Nachrichtenzustellung, Portal-Anmeldefehler, API-Timeouts] sehen. Unser Ingenieurteam hat das Problem bei [07:34 UTC] identifiziert und arbeitet aktiv daran, den Full-Service wiederherzustellen. Dies ist unsere oberste Priorität, und wir haben alle relevanten Teams engagiert. Wir werden das nächste Update bis [08:15 UTC] oder früher veröffentlichen, wenn sich die Situation ändert. Wir verstehen die Auswirkungen, die dies auf Ihre Operationen hat, und es tut uns leid für die Störung. Bei kontospezifischen Fragen wenden Sie sich bitte an Ihren Account Manager oder [email protected].

2. 26. August 2026 um 08:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. Dezember 2025 um 09:12 UTCinvestigating

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

2. 5. Dezember 2025 um 09:17 UTCmonitoring

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

3. 5. Dezember 2025 um 09:23 UTCresolved

   This incident has been resolved

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

   We are continuing to investigate this issue.

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

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

1. 4. August 2025 um 10:10 UTCinvestigating

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

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

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

4. 5. August 2025 um 06:13 UTCresolved

   This incident has been resolved.

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

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

3. 17. Juli 2025 um 17:08 UTCresolved

   This incident has been resolved.

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

   The incident has been resolved.

1. 29. August 2024 um 04:46 UTCidentified

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

2. 29. August 2024 um 06:24 UTCmonitoring

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

3. 29. August 2024 um 07:01 UTCresolved

   This incident has been resolved.

1. 5. August 2024 um 08:14 UTCinvestigating

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

2. 5. August 2024 um 08:41 UTCresolved

   This incident has been resolved.

1. 22. Februar 2024 um 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. Februar 2024 um 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. Februar 2024 um 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. Februar 2024 um 09:17 UTCinvestigating

   We are currently investigating this issue.

2. 20. Februar 2024 um 10:31 UTCresolved

   This incident has been resolved.

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

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

3. 30. Oktober 2023 um 20:39 UTCresolved

   This incident has been resolved.

1. 4. Oktober 2023 um 11:02 UTCinvestigating

   We are currently investigating this issue.

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

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

4. 8. Oktober 2023 um 09:37 UTCresolved

   This incident has been resolved.

1. 24. August 2023 um 10:20 UTCinvestigating

   We are currently investigating this issue.

2. 24. August 2023 um 10:51 UTCidentified

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

3. 24. August 2023 um 10:53 UTCmonitoring

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

4. 24. August 2023 um 10:54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24. August 2023 um 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. August 2023 um 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. August 2023 um 15:15 UTCmonitoring

   We applied a developed workaround and monitoring the results.

8. 25. August 2023 um 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. November 2022 um 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. November 2022 um 18:01 UTCidentified

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

3. 8. November 2022 um 18:09 UTCmonitoring

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

4. 8. November 2022 um 18:10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8. November 2022 um 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. August 2022 um 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. August 2022 um 16:03 UTCresolved

   This incident has been resolved.

3. 30. August 2022 um 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. Juli 2022 um 09:21 UTCinvestigating

   We are currently investigating this issue.

2. 12. Juli 2022 um 09:26 UTCidentified

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

3. 12. Juli 2022 um 09:32 UTCmonitoring

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

4. 12. Juli 2022 um 10:30 UTCresolved

   This incident has been resolved.

1. 28. Juni 2022 um 14:32 UTCidentified

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

2. 28. Juni 2022 um 14:52 UTCresolved

   This incident has been resolved.

1. 21. Juni 2022 um 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. Juni 2022 um 07:07 UTCidentified

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

3. 21. Juni 2022 um 07:32 UTCmonitoring

   A fix was applied, we are monitoring the result.

4. 21. Juni 2022 um 08:15 UTCresolved

   This incident has been resolved.