Störungsverlauf von Catchpoint

1. 12. Oktober 2026 um 03:18 UTCmonitoring

   Wir haben ein Problem identifiziert, das eine Teilmenge von Catchpoint-Tests ab dem 11. Oktober 2026 um 16:30 UTC betrifft, nachdem kürzlich ein DNSSEC-Rootkey-Rollover durchgeführt wurde. Dieses Problem betraf Tests mit DNSSEC-Validierung, was zu DNS-Auflösungsfehlern führte. Tests, die keine DNSSEC-Validierung verwenden, sind nicht betroffen. Unser Engineering-Team hat einen Fix bereitgestellt und wir überwachen sie aktiv, um sicherzustellen, dass die DNS-Auflösung und die Testausführung wieder normal sind.

2. 13. Oktober 2026 um 04:42 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. September 2026 um 21:24 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das die Verfügbarkeit von Knoten in China betrifft. Die Knoten in der CN-Region können offline im Portal erscheinen. Unser Team arbeitet daran, den normalen Service wiederherzustellen und wird weitere Updates bereitstellen, sobald mehr Informationen verfügbar sind.

2. 22. September 2026 um 22:36 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 23. September 2026 um 12:18 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. September 2026 um 09:02 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das Knoten in der EMEA-Region betrifft. Die Ausgabe begann um etwa 02:45 Uhr UTC am 12. September 2026. Unser Team untersucht das Problem aktiv. Wir werden zusätzliche Updates bereitstellen, sobald weitere Informationen verfügbar sind.

2. 12. September 2026 um 09:56 UTCmonitoring

   Ein Fix wurde implementiert und die betroffenen Daten wurden erfolgreich hinterlegt. Wir werden die Dienste weiterhin genau beobachten, um eine anhaltende Stabilität zu gewährleisten.

3. 13. September 2026 um 03:44 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. August 2026 um 19:36 UTCidentified

   Wir untersuchen derzeit ein Problem, das das Portal betrifft und eine sehr kleine Teilmenge unserer Benutzer betrifft. Wir arbeiten mit unserem Engineering-Team zusammen, um das Problem zu lösen.

2. 27. August 2026 um 21:54 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 28. August 2026 um 14:20 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 13:44 UTCresolved

   We identified and resolved an issue affecting SSL tests running on the US East Backbone and Cloud nodes from August 14, 2026, at 10:28:00 UTC to 13:14:10 UTC.

1. 22. Juni 2026 um 19:57 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das Backbone-Knoten in Australien betrifft. Alle anderen Knoten funktionieren normal. Wir arbeiten mit unseren regionalen Anbietern zusammen, um das Problem so schnell wie möglich zu beheben und werden Updates bereitstellen, sobald sie verfügbar sind.

2. 26. Juni 2026 um 16:23 UTCinvestigating

   Wir haben die Aufhebung aller Überwachungsknoten in Sydney und Melbourne abgeschlossen und sie sind jetzt voll funktionsfähig. Die verbleibenden Knoten in Adelaide, Brisbane und Perth sollen nächste Woche nicht unterbrochen werden. Wir werden ein weiteres Update zur Verfügung stellen, sobald es abgeschlossen ist. Vielen Dank für Ihre Geduld, da wir den Service an den verbleibenden Standorten weiterhin wiederherstellen.

3. 30. Juni 2026 um 08:05 UTCresolved

   Dieser Vorfall ist nun behoben und alle Knoten werden angehalten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. Mai 2026 um 20:04 UTCidentified

   We have identified an issue where certain alert emails may not be delivered to recipients. Our team is looking into this on priority and is currently investigating the cause and impact. We will provide an update as soon as we have more information. Please contact us at [email protected] if you need any further assistance or information.

2. 11. Mai 2026 um 21:57 UTCmonitoring

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

3. 12. Mai 2026 um 13:17 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 11:53 UTCinvestigating

   We are currently investigating an issue affecting nodes in the APAC region (excluding China) that began around 11:20 UTC. Impacted nodes may not be running tests as expected. Our team is actively working to resolve the issue and restore normal operations.

2. 8. Mai 2026 um 12:12 UTCmonitoring

   A fix was implemented around 11:46 UTC for the issue. Data collection and test execution have resumed, and we are continuing to monitor the services.

3. 11. Mai 2026 um 07:02 UTCresolved

   This incident has been resolved.

1. 29. April 2026 um 14:39 UTCmonitoring

   We identified an issue that affected a small number of users and API requests, impacting data loading on Record, Smartboard, and the REST API between 10:07 and 10:17 ET. A fix has been deployed and the issue is now resolved. We are continuing to monitor the system to ensure stability.

2. 30. April 2026 um 09:46 UTCresolved

   This incident has been resolved.

1. 24. April 2026 um 07:57 UTCinvestigating

   We are currently investigating an intermittent issue affecting capture server data collection for a subset of test runs, including Film Strip, screenshots, headers, and response content. Our team is actively working to identify the root cause and resolve the issue as quickly as possible. We will continue to share updates as more information becomes available.

2. 24. April 2026 um 08:47 UTCmonitoring

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

3. 24. April 2026 um 11:59 UTCresolved

   This incident has been resolved.

1. 23. April 2026 um 11:20 UTCinvestigating

   We are currently investigating an issue affecting capture server data collection, including Film Strip, screenshots, headers, and response content. Our team is actively working to identify the root cause and resolve the issue as quickly as possible. We will provide updates as more information becomes available.

2. 23. April 2026 um 11:48 UTCinvestigating

   We are continuing to investigate this issue.

3. 23. April 2026 um 15:14 UTCresolved

   This incident has been resolved.

1. 21. April 2026 um 08:51 UTCmonitoring

   We have identified and resolved an issue that affected a subset of enterprise node customers between 07:09 and 08:42 UTC. Our investigation confirms that there was no impact to customer data. All services are now operating normally. We will continue to monitor the system to ensure stability.

2. 21. April 2026 um 11:14 UTCresolved

   This incident has been resolved.

1. 15. April 2026 um 11:01 UTCinvestigating

   We are currently experiencing an issue with our email support channel, which may impact our ability to receive or respond to emails in a timely manner. In the meantime, we request you to reach out to us using Live Chat or by opening a ticket through the Resource Center in the portal for faster assistance. Our team is actively working to resolve this issue and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 15. April 2026 um 12:11 UTCmonitoring

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

3. 15. April 2026 um 14:15 UTCresolved

   This incident has been resolved.

1. 10. März 2026 um 21:53 UTCmonitoring

   Some Chrome-based tests were temporarily switched to Chrome Stable Version 89 between March 10, 2026 – 19:52 UTC and 20:15 UTC. As a result, tests configured to run on a higher Chrome browser version may have experienced failures during this time due to the version downgrade impacting monitoring behaviour. The issue has been resolved and all affected tests have been restored to their intended configurations.

2. 11. März 2026 um 03:10 UTCresolved

   This incident has been resolved.

1. 6. Februar 2026 um 10:28 UTCinvestigating

   We are currently investigating an issue where recent modifications to tests are not going live. We will share updates as more information becomes available.

2. 6. Februar 2026 um 10:55 UTCmonitoring

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

3. 7. Februar 2026 um 05:52 UTCresolved

   This incident has been resolved.

1. 16. Januar 2026 um 06:52 UTCinvestigating

   A subset of historical capture data in the US-West region is currently unavailable. All real-time capture data is working expected.

2. 16. Januar 2026 um 14:29 UTCresolved

   This incident has been resolved.

1. 13. Januar 2026 um 15:09 UTCmonitoring

   We have identified an issue that resulted in a data gap between 14:37:22 and 14:49:01 UTC. The affected data has backfilled and We are closely monitoring the situation and will share updates as needed.

2. 13. Januar 2026 um 15:34 UTCresolved

   This incident has been resolved.

1. 12. Dezember 2025 um 06:03 UTCinvestigating

   We are currently investigating an issue impacting the catchpoint portal. Some users may experience a blank page after logging in or when attempting to view records. Please note that tests and alerts continue to function as expected. Our team is actively working to resolve this as quickly as possible.

2. 12. Dezember 2025 um 06:17 UTCidentified

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

3. 12. Dezember 2025 um 06:33 UTCmonitoring

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

4. 12. Dezember 2025 um 06:43 UTCresolved

   This incident has been resolved.

1. 11. Dezember 2025 um 20:53 UTCinvestigating

   We are currently investigating an increase in reported ISP-related incidents in Internet Sonar. Further updates will be shared as soon as more information is available.

2. 11. Dezember 2025 um 21:24 UTCidentified

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

3. 12. Dezember 2025 um 01:42 UTCresolved

   This incident has been resolved.

1. 11. Dezember 2025 um 15:17 UTCinvestigating

   We are investigating an issue that affected the REST API calls during 14:53 - 15:03 UTC. The tests and alerts were running as expected but the REST API calls might have failed intermittently.

2. 11. Dezember 2025 um 16:36 UTCmonitoring

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

3. 12. Dezember 2025 um 04:04 UTCresolved

   This incident has been resolved.