Intermittent unavailability of the CSIS Portal
Pending
- resolved
We've now resolved the incident. Thanks for your patience.
Loading status page
Checking service and reports...
Loading status page
Loading status page
Checking service and reports...
25 recorded Csis Security Group incidents since February 2024, with official updates, affected components, duration and resolution information.
We've now resolved the incident. Thanks for your patience.
We have successfully completed our Disaster Recovery Exercise. Thank you for your patience.
We have now resolved the incident.
On October 20, 2025, from 05:27 UTC to 07:06 UTC, all HTTP-based CSIS services experienced a loss of availability due to an unexpected compatibility issue introduced during an automated Kubernetes cluster upgrade. A more detailed "Reason for outage" document can be requested via the CSIS Portal.
The maintenance is now complete. Thanks for your patience.
We have successfully completed our Disaster Recovery Exercise. Thank you for your patience.
We have rolled back the responsible deployment and are starting work on the Post Mortem investigation and Reason for Outage document.
The rollback is complete and the Threat Intelligence Portal is back online.
Our monitoring reports all is ok.
Our monitoring reports all is ok.
Our monitoring reports all is ok.
Our monitoring reports all is ok.
Our monitoring reports all is ok.
We are still working on the root cause analysis of this incident and will release the Reason for Outage as soon as we have finished the investigation.
Our monitoring reports all is ok.
Our monitoring reports all is ok.
We identified the cause and the issue has been resolved. Thanks for your patience.
Our monitoring reports all is ok.
We successfully finished yesterday's disaster recovery exercise. The first switch to the secondary data center was completed with less than 20 minutes of downtime. The simulated failure of our primary data center occurred at 20:39:25 UTC, and all systems were back up and running in our secondary data center at 20:58:07 UTC. As this process was on the lower end of the expected unavailability duration, we decided to switch back to the primary data center within the same maintenance window. This eliminated the need for the second maintenance window, scheduled for the next day. The complete switch back to the primary data center was completed after less than 15 minutes of downtime. The simulated failure of our secondary data center occurred at 21:46:11 UTC, and all systems were back up and running in our primary data center at 22:00:16 UTC. We would like to thank you for your understanding for this exercise and the associated periods of unavailability.
Our monitoring reports all is ok.