Histórico de interrupções do Catchpoint

1. 12 Here 2026 da 03:18 UTCmonitoring

   Identificamos um problema que afeta um subconjunto de testes de Catchpoint a partir de 11 de outubro de 2026, às 16:30 UTC, após um recente root key rollover do DNSSEC. Essa questão teve impacto nos testes utilizando a validação do DNSSEC, resultando em falhas na resolução do DNS. Os testes que não utilizam a validação do DNSSEC não são afetados. Nossa equipe de engenharia implantou uma correção, e estamos monitorando-os ativamente para garantir que a resolução e execução de testes do DNS retornaram ao normal.

2. 13 Here 2026 da 04:42 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gwengolo 2026 da 21:24 UTCinvestigating

   Estamos atualmente investigando uma questão que afeta a disponibilidade de nó na China. Os nós da região CN podem aparecer offline no portal. Nossa equipe está trabalhando para restaurar o serviço normal e fornecerá atualizações adicionais à medida que mais informações ficam disponíveis.

2. 22 Gwengolo 2026 da 22:36 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 23 Gwengolo 2026 da 12:18 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Gwengolo 2026 da 09:02 UTCinvestigating

   Estamos actualmente a investigar uma questão que afecta os nós na região da EMEA. O número começou aproximadamente às 02:45 UTC em 12 de setembro de 2026. A nossa equipa está a investigar a questão. Forneceremos atualizações adicionais à medida que mais informações estiverem disponíveis.

2. 12 Gwengolo 2026 da 09:56 UTCmonitoring

   Uma correção foi implementada, e os dados afetados foram preenchidos com sucesso. Continuaremos a acompanhar de perto os serviços para garantir a estabilidade permanente.

3. 13 Gwengolo 2026 da 03:44 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Eost 2026 da 19:36 UTCidentified

   Atualmente estamos investigando uma questão que afeta o Portal afetando um subconjunto muito pequeno de nossos usuários. Estamos trabalhando com nossa equipe de engenharia para resolver o problema.

2. 27 Eost 2026 da 21:54 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 28 Eost 2026 da 14:20 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Eost 2026 da 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 Mezheven 2026 da 19:57 UTCinvestigating

   Estamos a investigar um problema que afecta os nós da espinha dorsal na Austrália. Todos os outros nós estão funcionando normalmente. Estamos a trabalhar com os nossos fornecedores regionais para resolver o problema o mais rapidamente possível e vamos fornecer actualizações à medida que estiverem disponíveis.

2. 26 Mezheven 2026 da 16:23 UTCinvestigating

   Completamos a pausa de todos os nós de monitoramento de Sydney e Melbourne, e eles agora estão totalmente operacionais. Os nós restantes em Adelaide, Brisbane e Perth estão programados para não serem pausados na próxima semana. Providenciaremos outra atualização uma vez concluída. Obrigado por sua paciência como continuamos a restaurar o serviço em todos os locais restantes.

3. 30 Mezheven 2026 da 08:05 UTCresolved

   Este incidente está agora resolvido e todos os nós estão agora pausados.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Mae 2026 da 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 Mae 2026 da 21:57 UTCmonitoring

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

3. 12 Mae 2026 da 13:17 UTCresolved

   This incident has been resolved.

1. 8 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 07:02 UTCresolved

   This incident has been resolved.

1. 29 Ebrel 2026 da 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 Ebrel 2026 da 09:46 UTCresolved

   This incident has been resolved.

1. 24 Ebrel 2026 da 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 Ebrel 2026 da 08:47 UTCmonitoring

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

3. 24 Ebrel 2026 da 11:59 UTCresolved

   This incident has been resolved.

1. 23 Ebrel 2026 da 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 Ebrel 2026 da 11:48 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 Ebrel 2026 da 15:14 UTCresolved

   This incident has been resolved.

1. 21 Ebrel 2026 da 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 Ebrel 2026 da 11:14 UTCresolved

   This incident has been resolved.

1. 15 Ebrel 2026 da 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 Ebrel 2026 da 12:11 UTCmonitoring

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

3. 15 Ebrel 2026 da 14:15 UTCresolved

   This incident has been resolved.

1. 10 Meurzh 2026 da 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 Meurzh 2026 da 03:10 UTCresolved

   This incident has been resolved.

1. 6 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 10:55 UTCmonitoring

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

3. 7 Cʼhwevrer 2026 da 05:52 UTCresolved

   This incident has been resolved.

1. 16 Genver 2026 da 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 Genver 2026 da 14:29 UTCresolved

   This incident has been resolved.

1. 13 Genver 2026 da 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 Genver 2026 da 15:34 UTCresolved

   This incident has been resolved.

1. 12 Kerzu 2025 da 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 Kerzu 2025 da 06:17 UTCidentified

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

3. 12 Kerzu 2025 da 06:33 UTCmonitoring

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

4. 12 Kerzu 2025 da 06:43 UTCresolved

   This incident has been resolved.

1. 11 Kerzu 2025 da 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 Kerzu 2025 da 21:24 UTCidentified

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

3. 12 Kerzu 2025 da 01:42 UTCresolved

   This incident has been resolved.

1. 11 Kerzu 2025 da 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 Kerzu 2025 da 16:36 UTCmonitoring

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

3. 12 Kerzu 2025 da 04:04 UTCresolved

   This incident has been resolved.