Catchpoint had 49 outages in the last 2 years totaling 441h 40m of downtime — averaging 2 incidents per month.
There were 49 Catchpoint outages since June 3, 2025 totaling 441h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue affecting the Portal affecting a very small subset of our users. We are working with our Engineering team to resolve the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are currently investigating an issue affecting backbone nodes in Australia. All other nodes are operating normally. We are working with our regional providers to resolve the issue as quickly as possible and will provide updates as they become available.
We have completed the unpausing of all Sydney and Melbourne monitoring nodes, and they are now fully operational. The remaining nodes in Adelaide, Brisbane, and Perth are scheduled to be unpaused next week. We'll provide another update once complete. Thank you for your patience as we continue to restore service across the remaining locations.
This Incident is now resolved and all the nodes are now paused.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate this issue.
This incident has been resolved.
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.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating an issue where recent modifications to tests are not going live. We will share updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A subset of historical capture data in the US-West region is currently unavailable. All real-time capture data is working expected.
This incident has been resolved.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
Today, between 16:23 and 16:30 UTC, we experienced an issue affecting the REST API and the Catchpoint portal. During this period, users may have encountered slowness and intermittent failures when using the portal, and API calls may have failed. The issue has been resolved and we are actively monitoring the situation and taking the necessary steps to prevent this from happening again. We appreciate your patience and will provide updates as needed.
This incident has been resolved.
We are currently investigating an issue impacting users with Client Observer access, preventing them from using the portal. Our teams are actively working to restore functionality as quickly as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue where users with Division Administrator and Client observer user roles are able to log in but are unable to see any data on the portal. Rest assured, all test data, alerts, and test-related configurations continue to function as expected. This issue also impacts any API key associated with these users. Our team is actively working to identify the root cause, and we will provide further updates as soon as they are available.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We apologize for the inconvenience this is causing our users. Rest assured, we are treating this as a critical issue and our teams continue to investigate.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue that affected a subset of client tests that were using a Global Variable. The issue has since been resolved as of 09:30 UTC. Our team is continuing to review the incident, and we will share additional details once the analysis is complete. If you need any assistance with tests that use Global Variables, please contact us at [email protected]
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating slowness in the portal. Users may experience delays when performing actions on the Test Properties blade. Our team is actively investigating the issue to restore normal performance as quickly as possible.
We have resolved the issue that caused slowness within the portal, where users may have experienced delays while performing actions on the test properties blade. The incident was traced to a third-party service used by the portal. We have temporarily stopped the functionality that relies on this service while we work with the provider to determine why it caused the issue and to prevent recurrence. If you need additional details please reach out to [email protected]