Resolved -
This incident has been resolved.
Oct 29, 20:00 EDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 28, 20:50 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Oct 24, 09:03 EDT
Update -
We have paused the node for further analysis. Apologies for any inconvenience this may have caused.
Oct 23, 13:09 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Oct 23, 11:39 EDT
Update -
We have paused the node for further analysis. Apologies for any inconvenience this may have caused.
Jul 22, 19:12 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Jul 22, 18:25 EDT
Update -
We have paused the node for further testing and analysis. Apologies for any inconvenience this may have caused.
Jul 16, 14:50 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Jul 15, 14:21 EDT
Update -
We have paused the node for further testing and analysis. Apologies for any inconvenience this may have caused.
Jul 2, 09:46 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Jul 2, 08:59 EDT
Update -
We have paused the node for further investigation. Apologies for any inconvenience this may have caused.
Jun 19, 00:21 EDT
Update -
We have resumed the node to conduct further testing and analysis. We apologize for any inconvenience this may have caused.
Jun 18, 19:05 EDT
Update -
We have paused the node for further investigation. Apologies for any inconvenience this may have caused.
Jun 9, 21:57 EDT
Update -
We have resumed the node for further investigation. Apologies for any inconvenience this may have caused.
Jun 9, 20:55 EDT
Update -
We have paused the node for further investigation. Apologies for any inconvenience this may have caused.
May 21, 01:52 EDT
Update -
We have resumed the node for further investigation. Apologies for any inconvenience this may have caused.
May 21, 00:37 EDT
Update -
We have paused the node for further investigation. Apologies for any inconvenience this may have caused.
May 16, 11:20 EDT
Update -
We have resumed the node for further investigation. Apologies for any inconvenience this may have caused.
May 16, 09:34 EDT
Investigating -
Catchpoint Backbone node Kuala Lumpur, MY - Time have been paused due to an unplanned maintenance at provider end and will not run tests. We will update the status as soon as there is additional information available.
May 16, 04:47 EDT