The Service Status Page where we will keep you up to date on any current known events, both network outages and scheduled maintenance, which may affect your Catchpoint Services.
Update -
We are actively collaborating with our vendor to restore services and sincerely appreciate your patience during this process.
Oct 22, 16:08 EDT
Update -
We are continuing to investigate this issue.
Oct 20, 15:29 EDT
Investigating -
We are currently experiencing an issue affecting a subset of nodes in San Francisco, US. This may result in a subset of our tests not running as expected from those specific locations. We apologize for any inconvenience and are actively working to resolve the problem.
Oct 20, 09:50 EDT
Completed -
The scheduled maintenance has been completed.
Oct 16, 16:00 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 16, 12:00 EDT
Scheduled -
Our next release, Lynx, will roll out on Wednesday, October 16, at 12:00 PM ET.
The Catchpoint Portal (portal.catchpoint.com) will continue to be available throughout the rollout, and your tests will continue to run and collect data. During this time, you might encounter the following:
- Individual clients will have a brief time (about 3-5 minutes) where alerts and charts will be inaccessible or delayed while we upgrade our applications.
- The REST API will experience a short downtime of about 15 minutes. The Alert and Test Data Webhooks will continue to operate throughout the rollout.
During the rollout, support tickets may still be filed via the Help Center or email to support@catchpoint.com.
Oct 9, 17:08 EDT
Resolved -
This incident has been resolved.
Oct 16, 09:43 EDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 16, 08:04 EDT
Update -
We have identified the issue and are currently implementing the fix.
Oct 16, 07:02 EDT
Identified -
We are currently experiencing an issue in the portal where scheduled and instant tests for WebPageTest have not been returning results since 9:15 AM UTC. We are actively working on resolving this issue.
Oct 16, 06:36 EDT