Catchpoint driftsforstyrrelser

1. 12. oktober 2026 kl. 03.18 UTCmonitoring

   Vi identificerede et problem, der påvirker en delmængde af Catchpoint tests fra 11 oktober 2026, 16: 30 UTC, efter en nylig DNSSEC root key rollover. Dette spørgsmål påvirkede tests ved hjælp af DNSSEC validering, hvilket resulterer i DNS opløsning fejl. Test, der ikke anvender DNSSEC-validering, påvirkes ikke. Vores ingeniørhold har indsat et fix, og vi overvåger dem aktivt for at sikre DNS opløsning og test udførelse er vendt tilbage til normal.

2. 13. oktober 2026 kl. 04.42 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. september 2026 kl. 21.24 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et spørgsmål, der påvirker node tilgængelighed i Kina. Knuderne i KN-regionen kan forekomme offline i portalen. Vores team arbejder på at genoprette normal service og vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 22. september 2026 kl. 22.36 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 23. september 2026 kl. 12.18 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. september 2026 kl. 09.02 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker knudepunkter i EMEA-regionen. Spørgsmålet begyndte omkring 02: 45 UTC den 12. september 2026. Vores team undersøger sagen aktivt. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 12. september 2026 kl. 09.56 UTCmonitoring

   En rettelse er blevet implementeret, og de berørte data er blevet fyldt med fejl. Vi vil fortsat nøje overvåge tjenesterne for at sikre fortsat stabilitet.

3. 13. september 2026 kl. 03.44 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 19.36 UTCidentified

   Vi undersøger i øjeblikket et problem, der påvirker portalen, og som påvirker en meget lille del af vores brugere. Vi arbejder med vores ingeniørhold for at løse problemet.

2. 27. august 2026 kl. 21.54 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 28. august 2026 kl. 14.20 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 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 kl. 19.57 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker rygraden i Australien. Alle andre knudepunkter fungerer normalt. Vi arbejder sammen med vores regionale udbydere for at løse problemet så hurtigt som muligt og vil levere opdateringer, efterhånden som de bliver tilgængelige.

2. 26. juni 2026 kl. 16.23 UTCinvestigating

   Vi er færdige med at fjerne alle Sydney og Melbourne overvågningsknudepunkter, og de er nu fuldt operationelle. De resterende knudepunkter i Adelaide, Brisbane og Perth er planlagt til at blive ubrugt i næste uge. Vi giver en ny opdatering, når den er færdig. Tak for din tålmodighed, da vi fortsætter med at genoprette service på tværs af de resterende steder.

3. 30. juni 2026 kl. 08.05 UTCresolved

   Denne hændelse er nu løst og alle knudepunkterne er nu sat på pause.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. maj 2026 kl. 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. maj 2026 kl. 21.57 UTCmonitoring

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

3. 12. maj 2026 kl. 13.17 UTCresolved

   This incident has been resolved.

1. 8. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 07.02 UTCresolved

   This incident has been resolved.

1. 29. april 2026 kl. 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 kl. 09.46 UTCresolved

   This incident has been resolved.

1. 24. april 2026 kl. 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 kl. 08.47 UTCmonitoring

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

3. 24. april 2026 kl. 11.59 UTCresolved

   This incident has been resolved.

1. 23. april 2026 kl. 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 kl. 11.48 UTCinvestigating

   We are continuing to investigate this issue.

3. 23. april 2026 kl. 15.14 UTCresolved

   This incident has been resolved.

1. 21. april 2026 kl. 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 kl. 11.14 UTCresolved

   This incident has been resolved.

1. 15. april 2026 kl. 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 kl. 12.11 UTCmonitoring

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

3. 15. april 2026 kl. 14.15 UTCresolved

   This incident has been resolved.

1. 10. marts 2026 kl. 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. marts 2026 kl. 03.10 UTCresolved

   This incident has been resolved.

1. 6. februar 2026 kl. 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 kl. 10.55 UTCmonitoring

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

3. 7. februar 2026 kl. 05.52 UTCresolved

   This incident has been resolved.

1. 16. januar 2026 kl. 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 kl. 14.29 UTCresolved

   This incident has been resolved.

1. 13. januar 2026 kl. 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 kl. 15.34 UTCresolved

   This incident has been resolved.

1. 12. december 2025 kl. 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. december 2025 kl. 06.17 UTCidentified

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

3. 12. december 2025 kl. 06.33 UTCmonitoring

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

4. 12. december 2025 kl. 06.43 UTCresolved

   This incident has been resolved.

1. 11. december 2025 kl. 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. december 2025 kl. 21.24 UTCidentified

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

3. 12. december 2025 kl. 01.42 UTCresolved

   This incident has been resolved.

1. 11. december 2025 kl. 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. december 2025 kl. 16.36 UTCmonitoring

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

3. 12. december 2025 kl. 04.04 UTCresolved

   This incident has been resolved.