Historial de interrupciones de Catchpoint

1. August 27, 2026 at 7:36 PM UTCidentified

   Actualmente estamos investigando un problema que afecta al Portal que afecta a un subconjunto muy pequeño de nuestros usuarios. Trabajamos con nuestro equipo de Ingeniería para resolver el problema.

2. August 27, 2026 at 9:54 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. August 28, 2026 at 2:20 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 14, 2026 at 1:44 PM 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. June 22, 2026 at 7:57 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a los nodos de columna vertebral en Australia. Todos los demás nodos funcionan normalmente. Trabajamos con nuestros proveedores regionales para resolver el problema lo antes posible y proporcionaremos actualizaciones cuando estén disponibles.

2. June 26, 2026 at 4:23 PM UTCinvestigating

   Hemos completado el impago de todos los nodos de monitoreo de Sydney y Melbourne, y ahora están totalmente operativos. Los nodos restantes en Adelaide, Brisbane y Perth están programados para ser no utilizados la próxima semana. Vamos a proporcionar otra actualización una vez completa. Gracias por su paciencia mientras continuamos restaurando el servicio en los lugares restantes.

3. June 30, 2026 at 8:05 AM UTCresolved

   Este incidente se resuelve ahora y todos los nodos se detienen ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 11, 2026 at 8:04 PM 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. May 11, 2026 at 9:57 PM UTCmonitoring

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

3. May 12, 2026 at 1:17 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 11:53 AM 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. May 8, 2026 at 12:12 PM 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. May 11, 2026 at 7:02 AM UTCresolved

   This incident has been resolved.

1. April 29, 2026 at 2:39 PM 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. April 30, 2026 at 9:46 AM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 7:57 AM 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. April 24, 2026 at 8:47 AM UTCmonitoring

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

3. April 24, 2026 at 11:59 AM UTCresolved

   This incident has been resolved.

1. April 23, 2026 at 11:20 AM 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. April 23, 2026 at 11:48 AM UTCinvestigating

   We are continuing to investigate this issue.

3. April 23, 2026 at 3:14 PM UTCresolved

   This incident has been resolved.

1. April 21, 2026 at 8:51 AM 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. April 21, 2026 at 11:14 AM UTCresolved

   This incident has been resolved.

1. April 15, 2026 at 11:01 AM 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. April 15, 2026 at 12:11 PM UTCmonitoring

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

3. April 15, 2026 at 2:15 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 9:53 PM 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. March 11, 2026 at 3:10 AM UTCresolved

   This incident has been resolved.

1. February 6, 2026 at 10:28 AM 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. February 6, 2026 at 10:55 AM UTCmonitoring

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

3. February 7, 2026 at 5:52 AM UTCresolved

   This incident has been resolved.

1. January 16, 2026 at 6:52 AM UTCinvestigating

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

2. January 16, 2026 at 2:29 PM UTCresolved

   This incident has been resolved.

1. January 13, 2026 at 3:09 PM 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. January 13, 2026 at 3:34 PM UTCresolved

   This incident has been resolved.

1. December 12, 2025 at 6:03 AM 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. December 12, 2025 at 6:17 AM UTCidentified

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

3. December 12, 2025 at 6:33 AM UTCmonitoring

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

4. December 12, 2025 at 6:43 AM UTCresolved

   This incident has been resolved.

1. December 11, 2025 at 8:53 PM 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. December 11, 2025 at 9:24 PM UTCidentified

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

3. December 12, 2025 at 1:42 AM UTCresolved

   This incident has been resolved.

1. December 11, 2025 at 3:17 PM 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. December 11, 2025 at 4:36 PM UTCmonitoring

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

3. December 12, 2025 at 4:04 AM UTCresolved

   This incident has been resolved.

1. December 11, 2025 at 1:24 AM 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. December 11, 2025 at 3:16 PM UTCresolved

   This incident has been resolved.

1. December 9, 2025 at 1:28 PM 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. December 9, 2025 at 2:17 PM 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. December 9, 2025 at 2:33 PM UTCmonitoring

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

4. December 9, 2025 at 11:33 PM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 6:53 PM 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. December 5, 2025 at 11:08 PM UTCresolved

   This incident has been resolved.