Störungsverlauf von Phoneburner

1. 21. Oktober 2026 um 13:43 UTCmonitoring

   Als Teil unseres anhaltenden Engagements für Daten- und Informationssicherheit setzen wir aus einer Fülle von Vorsicht eine Reihe von Sicherheitsgegenmaßnahmen ein, um auf die in den letzten 24 Stunden angekündigte weit verbreitete Sicherheitslücke im Internet zu reagieren. Im rahmen dieser schnellen reaktionsbemühungen können einige nutzer intermittierende verfügbarkeit unserer dienste erleben. Wir werden weitere Updates bereitstellen, wenn diese Bemühungen abgeschlossen sind.

2. 21. Oktober 2026 um 15:28 UTCmonitoring

   Die Arbeit wird als Reaktion auf die weithin berichtete bekannte Sicherheitslücke im Internet fortgesetzt, die in den letzten 24 Stunden angekündigt wurde. Da unsere Teams Sicherheitsverbesserungen einsetzen, können Benutzer eine zeitweise beeinträchtigte Erfahrung erleben, während sich diese Änderungen über unsere Dienste ausbreiten. Wir schätzen Ihre Geduld, da wir weiterhin Sicherheitsverbesserungen bereitstellen und weiterhin Updates bereitstellen werden.

3. 21. Oktober 2026 um 16:25 UTCresolved

   Wir haben erfolgreich neue Sicherheitspatches implementiert und unsere Umgebung mit neuen Konfigurationen unserer Sicherheitspartner aktualisiert. Wir glauben, dass Benutzer normale Betriebsbedingungen erleben sollten. Wir schätzen Ihre Geduld, da wir diesen Prozess durchlaufen haben, um unsere Dienste und Anwendungen zu sichern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 19:46 UTCidentified

   Wir untersuchen Website-Probleme. Ingenieure haben das Problem identifiziert und arbeiten an einer Lösung.

2. 20. Juli 2026 um 19:49 UTCmonitoring

   Das Problem ist gelöst. Wir überwachen

3. 20. Juli 2026 um 19:58 UTCresolved

   Die Website ist wieder normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juni 2026 um 13:51 UTCinvestigating

   We are investigating a fix.

2. 9. Juni 2026 um 14:00 UTCresolved

   This incident has been resolved.

1. 28. Juli 2025 um 18:20 UTCinvestigating

   We are investigating performance issues with the website.

2. 28. Juli 2025 um 18:23 UTCmonitoring

   Site performance is improving. We're monitoring.

3. 28. Juli 2025 um 18:25 UTCresolved

   Site performance is back to normal operation.

1. 23. Juli 2025 um 20:31 UTCidentified

   We have identified an intermittent issue with the dialer where the buttons don't work as expected. We have identified it as an issue with one of our vendors. We're working closely with them to resolve the issue.

2. 23. Juli 2025 um 20:51 UTCidentified

   The vendor is still researching the issues on their end.

3. 23. Juli 2025 um 21:49 UTCmonitoring

   We have started the process of moving all the usage away from the problematic vendor. We are monitoring. We recommend any users experiencing the issues log out of your account and login again to ensure you pickup the new configurations.

4. 23. Juli 2025 um 21:55 UTCresolved

   Traffic is migrated away from the problematic vendor and we'll continue monitoring.

1. 9. Juli 2025 um 14:36 UTCinvestigating

   We are investigating issues with the site

2. 9. Juli 2025 um 14:47 UTCidentified

   We've identified the source of the issue and we're remediating. We're starting to see performance improvements.

3. 9. Juli 2025 um 15:08 UTCmonitoring

   We are seeing full site performance recovery. We are monitoring.

4. 9. Juli 2025 um 15:39 UTCresolved

   Site performance has been restored. We've determined that an upstream provider was having performance issues that degraded some aspects of our site. We have mitigated those issue and the site is performing well. We'll continue monitoring.

1. 18. Juni 2025 um 18:42 UTCinvestigating

   We are investigating degraded website performance

2. 18. Juni 2025 um 18:56 UTCmonitoring

   Engineers have identified the issue and we're seeing performance recover. We're monitoring.

3. 18. Juni 2025 um 19:10 UTCresolved

   Site performance has been restored.

1. 16. Mai 2025 um 01:07 UTCinvestigating

   We have identified the issue and are working on a resolution.

2. 16. Mai 2025 um 01:34 UTCidentified

   Engineering team has identified a fix and an update and/or fix should be deployed shortly.

3. 16. Mai 2025 um 01:41 UTCmonitoring

   Calls are completing successfully. We are monitoring the make sure the system is stable.

4. 16. Mai 2025 um 01:49 UTCresolved

   The incident is resolved.

1. 3. April 2025 um 16:41 UTCinvestigating

   We are investigating site performance issues

2. 3. April 2025 um 16:53 UTCmonitoring

   We are observing improved performance. The team is continuing to monitor.

3. 3. April 2025 um 17:03 UTCresolved

   Site performance has been fully restored.

1. 27. März 2025 um 01:56 UTCinvestigating

   We are investigating the issue.

2. 27. März 2025 um 02:17 UTCinvestigating

   The team continues to investigate the issue. A new update will come shortly.

3. 27. März 2025 um 02:36 UTCinvestigating

   We are continuing to work on a fix for the issue.

4. 27. März 2025 um 02:46 UTCmonitoring

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

5. 27. März 2025 um 03:46 UTCresolved

   This incident has been resolved.

1. 14. März 2025 um 19:44 UTCinvestigating

   We are investing issues with the site loading slowly.

2. 14. März 2025 um 19:48 UTCidentified

   We have identified the source of the issue and the team is working on resolution.

3. 14. März 2025 um 19:58 UTCmonitoring

   We're observing site performance improvements. We're monitoring.

4. 14. März 2025 um 20:05 UTCresolved

   The site performance has been restored.

1. 28. Februar 2025 um 14:26 UTCidentified

   We have identified an issue with some outbound calls through the dialer. This includes call transfers as well. Engineers are actively working through the issues.

2. 28. Februar 2025 um 14:42 UTCmonitoring

   Issue has been identified and resolved. We are monitoring.

3. 28. Februar 2025 um 14:48 UTCresolved

   Systems are fully operational.

1. 24. Oktober 2024 um 14:26 UTCinvestigating

   We are currently researching issues related to slow site performance.

2. 24. Oktober 2024 um 14:38 UTCidentified

   We have identified the source of the issue and are deploying a fix.

3. 24. Oktober 2024 um 14:41 UTCmonitoring

   A fix has been implemented and performance is recovering. We are monitoring.

4. 24. Oktober 2024 um 14:46 UTCidentified

   Issues are not resolved. We are triaging a deployment issue.

5. 24. Oktober 2024 um 14:56 UTCmonitoring

   Fixes are confirmed in good working order. We are monitoring performance.

6. 24. Oktober 2024 um 15:01 UTCresolved

   Site performance is fully restored and operating normally.

1. 22. August 2024 um 12:34 UTCinvestigating

   We are currently investigating an issue with the dialer.

2. 22. August 2024 um 12:42 UTCidentified

   We have identified the issue and are working on a fix.

3. 22. August 2024 um 12:48 UTCmonitoring

   We are actively resolving the issue and we're starting to see recovery.

4. 22. August 2024 um 12:53 UTCresolved

   Dialer has been restored and fully functional.

1. 30. Mai 2024 um 20:49 UTCinvestigating

   We are currently investigating reports of a slow and/or unresponsive site.

2. 30. Mai 2024 um 21:07 UTCinvestigating

   The team is still researching. We'll update again shortly.

3. 30. Mai 2024 um 22:47 UTCmonitoring

   The team believes there is a performance problem with some in-browser integrations. We have disabled that integration and are monitoring performance. We also believe this does not impact everyone.

4. 30. Mai 2024 um 23:16 UTCresolved

   The team has confirmed that the 3rd party library in the browser is in fact driving high CPU and making the browser window unresponsive. The integration has been disabled, and the site is in working as expected. We are closing the incident and the team will continue to monitor.

1. 20. Mai 2024 um 20:44 UTCinvestigating

   We are investigating issues with site performance

2. 20. Mai 2024 um 21:13 UTCresolved

   Site access is fully restored.

1. 13. Mai 2024 um 23:23 UTCinvestigating

   We are experiencing issues the site. The team is researching.

2. 13. Mai 2024 um 23:29 UTCidentified

   We have identified the db instances in the cluster and are fixing.

3. 13. Mai 2024 um 23:33 UTCidentified

   Site is recovering as instances are restored.

4. 13. Mai 2024 um 23:51 UTCmonitoring

   Site is recovered with some indications of degraded performance. The team is still researching and monitoring.

5. 14. Mai 2024 um 00:17 UTCresolved

   Site is fully restored. We will continue to monitor.

1. 13. Mai 2024 um 21:31 UTCinvestigating

   We have noticed degraded performance on the site. The team is researching.

2. 13. Mai 2024 um 21:38 UTCidentified

   The team has identified some problematic instances in out the database cluster. A fix is being worked on now. There is no impact on data - just on site performance.

3. 13. Mai 2024 um 21:52 UTCresolved

   Problematic instances are fixed and site is fully operational.

1. 15. November 2023 um 21:13 UTCinvestigating

   We are investigating issues with accessing the site.

2. 15. November 2023 um 21:26 UTCidentified

   The team has identified a potential source cause. We are investigating further.

3. 15. November 2023 um 21:49 UTCidentified

   The team is still researching. Nothing new to report at the moment.

4. 15. November 2023 um 21:54 UTCmonitoring

   The team has resolved the root cause and is monitoring.

5. 15. November 2023 um 22:02 UTCresolved

   This incident is resolved.

1. 9. Oktober 2023 um 16:53 UTCinvestigating

   We are currently experiencing site issues. We're investgiating

2. 9. Oktober 2023 um 17:03 UTCidentified

   We have a identified a resource issue and are working on a fix.

3. 9. Oktober 2023 um 17:12 UTCmonitoring

   Sites are showing improved performance and we are monitoring.

4. 9. Oktober 2023 um 17:27 UTCresolved

   Systems are fully operational.