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

1. 27 августа 2026 г. в 19:36 UTCidentified

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

2. 27 августа 2026 г. в 21:54 UTCmonitoring

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

3. 28 августа 2026 г. в 14:20 UTCresolved

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

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

1. 14 августа 2026 г. в 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 июня 2026 г. в 19:57 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую магистральные узлы в Австралии. Все остальные узлы работают нормально. Мы работаем с нашими региональными поставщиками, чтобы решить проблему как можно быстрее и предоставить обновления по мере их поступления.

2. 26 июня 2026 г. в 16:23 UTCinvestigating

   Мы завершили разблокировку всех узлов мониторинга Сиднея и Мельбурна, и теперь они полностью работоспособны. Остальные узлы в Аделаиде, Брисбене и Перте должны быть отключены на следующей неделе. Мы предоставим еще одно обновление после завершения. Спасибо за ваше терпение, поскольку мы продолжаем восстанавливать сервис в оставшихся местах.

3. 30 июня 2026 г. в 08:05 UTCresolved

   Этот инцидент теперь разрешен, и все узлы теперь остановлены.

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

1. 11 мая 2026 г. в 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 мая 2026 г. в 21:57 UTCmonitoring

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

3. 12 мая 2026 г. в 13:17 UTCresolved

   This incident has been resolved.

1. 8 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 07:02 UTCresolved

   This incident has been resolved.

1. 29 апреля 2026 г. в 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 апреля 2026 г. в 09:46 UTCresolved

   This incident has been resolved.

1. 24 апреля 2026 г. в 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 апреля 2026 г. в 08:47 UTCmonitoring

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

3. 24 апреля 2026 г. в 11:59 UTCresolved

   This incident has been resolved.

1. 23 апреля 2026 г. в 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 апреля 2026 г. в 11:48 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 апреля 2026 г. в 15:14 UTCresolved

   This incident has been resolved.

1. 21 апреля 2026 г. в 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 апреля 2026 г. в 11:14 UTCresolved

   This incident has been resolved.

1. 15 апреля 2026 г. в 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 апреля 2026 г. в 12:11 UTCmonitoring

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

3. 15 апреля 2026 г. в 14:15 UTCresolved

   This incident has been resolved.

1. 10 марта 2026 г. в 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 марта 2026 г. в 03:10 UTCresolved

   This incident has been resolved.

1. 6 февраля 2026 г. в 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 февраля 2026 г. в 10:55 UTCmonitoring

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

3. 7 февраля 2026 г. в 05:52 UTCresolved

   This incident has been resolved.

1. 16 января 2026 г. в 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 января 2026 г. в 14:29 UTCresolved

   This incident has been resolved.

1. 13 января 2026 г. в 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 января 2026 г. в 15:34 UTCresolved

   This incident has been resolved.

1. 12 декабря 2025 г. в 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 декабря 2025 г. в 06:17 UTCidentified

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

3. 12 декабря 2025 г. в 06:33 UTCmonitoring

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

4. 12 декабря 2025 г. в 06:43 UTCresolved

   This incident has been resolved.

1. 11 декабря 2025 г. в 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 декабря 2025 г. в 21:24 UTCidentified

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

3. 12 декабря 2025 г. в 01:42 UTCresolved

   This incident has been resolved.

1. 11 декабря 2025 г. в 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 декабря 2025 г. в 16:36 UTCmonitoring

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

3. 12 декабря 2025 г. в 04:04 UTCresolved

   This incident has been resolved.

1. 11 декабря 2025 г. в 01:24 UTCmonitoring

   We are currently investigating an issue affecting a subset of users, which may result in errors when plotting data starting from 00:30 UTC. Our Engineering team has identified the issue and deployed a fix. We will continue to monitor and provide updates as more information becomes available.

2. 11 декабря 2025 г. в 15:16 UTCresolved

   This incident has been resolved.

1. 9 декабря 2025 г. в 13:28 UTCinvestigating

   We are currently investigating an issue that is causing failures in REST API calls. The failure began on December 09, 2025 at 12:48 UTC, and our teams are actively working to restore full functionality. At this time, your test data and alerts continue to operate as expected. We will provide additional updates as more information becomes available.

2. 9 декабря 2025 г. в 14:17 UTCinvestigating

   No errors have been observed since Dec 09, 2025 - 13:22 UTC, our team continues to investigate the issue and we shall keep you posted with the updates.

3. 9 декабря 2025 г. в 14:33 UTCmonitoring

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

4. 9 декабря 2025 г. в 23:33 UTCresolved

   This incident has been resolved.

1. 5 декабря 2025 г. в 18:53 UTCmonitoring

   On 5th December 2025, between 08:48 and 09:11 UTC, we experienced an issue with our CDN vendor that affected our REST API. During this time, users may have encountered failures with API calls. Our vendor has resolved the issue, and we are closely monitoring the situation. We appreciate your patience and will provide updates, as necessary.

2. 5 декабря 2025 г. в 23:08 UTCresolved

   This incident has been resolved.