All Systems Operational
Web application
Operational
Event ingestion
Operational
Event storage
Operational
Detection
Operational
Queries
Operational
Cases
Operational
Automation
Operational
AI
Operational
CTI Search
Operational
CTI Feed (API & TAXII)
Operational
CTI Feed (MISP)
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 8, 2026
No incidents reported today.
Sep 7, 2026
Resolved -
This incident is resolved.
Detection process is back in real-time.
All events and alert are stored and searchable in real-time.
Overall the event ingestion process is in real time.
We thank you for your patience during resolution.
Sep 7, 18:46 UTC
Detection process is back in real-time.
All events and alert are stored and searchable in real-time.
Overall the event ingestion process is in real time.
We thank you for your patience during resolution.
Sep 7, 18:46 UTC
Monitoring -
A fix was implemented and allowed detection and ingestion services to restart.
We expect lag to resorb gradually.
Our engineering teams are monitoring the situation.
Sep 7, 14:37 UTC
We expect lag to resorb gradually.
Our engineering teams are monitoring the situation.
Sep 7, 14:37 UTC
Update -
Restarting the affected components has not fully restored service.
Detection may be delayed while the issue persists.
Our teams are investigating a problem that appears to be related to the underlying cache management component. We are evaluating workarounds and possible solutions.
Sep 7, 13:48 UTC
Detection may be delayed while the issue persists.
Our teams are investigating a problem that appears to be related to the underlying cache management component. We are evaluating workarounds and possible solutions.
Sep 7, 13:48 UTC
Identified -
The issue affecting our cache infrastructure has recurred and may affect detection services.
Our teams are restarting the affected components as a temporary measure to restore service while we continue investigating the root cause.
The service should be partially restored soon.
We will provide another update as soon as more information is available.
Sep 7, 13:15 UTC
Our teams are restarting the affected components as a temporary measure to restore service while we continue investigating the root cause.
The service should be partially restored soon.
We will provide another update as soon as more information is available.
Sep 7, 13:15 UTC
Investigating -
Our engineering teams have detected and investigating an issue.
Some of our customers might experience delay in events ingestion.
An update will be provided as soon as possible to inform about remediation actions.
We thank you for your patience during resolution.
Sep 7, 12:56 UTC
Some of our customers might experience delay in events ingestion.
An update will be provided as soon as possible to inform about remediation actions.
We thank you for your patience during resolution.
Sep 7, 12:56 UTC
Resolved -
The incident has been resolved. Ingestion and Detection services have been recovered.
Sep 7, 10:58 UTC
Sep 7, 10:58 UTC
Monitoring -
Following the restart of the affected backend components, some services took longer than expected to reconnect. They have since reconnected automatically, and we are continuing to monitor the service.
Sep 7, 10:05 UTC
Sep 7, 10:05 UTC
Identified -
The situation has improved slightly, but ingestion and detection services continue to experience disruptions. The services remain available, although some functionality may be affected.
Our teams are continuing to work on restoring normal service.
Sep 7, 09:37 UTC
Our teams are continuing to work on restoring normal service.
Sep 7, 09:37 UTC
Monitoring -
Service appears to be returning to normal following the restart of an affected backend component.
Our initial findings point to an issue affecting our cloud provider’s infrastructure. We are continuing to monitor the service to confirm full stability.
Sep 7, 09:25 UTC
Our initial findings point to an issue affecting our cloud provider’s infrastructure. We are continuing to monitor the service to confirm full stability.
Sep 7, 09:25 UTC
Update -
Further analysis indicates that this incident may affect our detection services. Our teams are continuing restoration efforts and will provide another update as soon as more information is available.
Sep 7, 09:15 UTC
Sep 7, 09:15 UTC
Identified -
Some services may be unavailable or experience degraded performance because they are unable to establish new connections to a required cache component.
Our teams are restarting the affected services to restore normal operation.
We will provide an update as soon as more information is available.
Sep 7, 09:08 UTC
Our teams are restarting the affected services to restore normal operation.
We will provide an update as soon as more information is available.
Sep 7, 09:08 UTC
Investigating -
Our Engineering team has identified an issue impacting event processing.
Users may experience some delays for events to appear in the console.
An update will be provided as soon as possible to inform about resolution actions.
We thank you for your patience during resolution.
Sep 7, 08:38 UTC
Users may experience some delays for events to appear in the console.
An update will be provided as soon as possible to inform about resolution actions.
We thank you for your patience during resolution.
Sep 7, 08:38 UTC
Sep 6, 2026
No incidents reported.
Sep 5, 2026
No incidents reported.
Sep 4, 2026
No incidents reported.
Sep 3, 2026
No incidents reported.
Sep 2, 2026
Resolved -
The incident is now resolved. Authentication services are operating normally and the platform is stable.
We will continue to monitor the service, but no further impact is expected.
Sep 2, 21:23 UTC
We will continue to monitor the service, but no further impact is expected.
Sep 2, 21:23 UTC
Monitoring -
We scaled the database infrastructure bottleneck identified during the investigation and are now able to fully absorb the increased authentication load.
The situation is resolved and services are stable. We will continue monitoring closely.
Sep 2, 21:09 UTC
The situation is resolved and services are stable. We will continue monitoring closely.
Sep 2, 21:09 UTC
Identified -
We have identified the source of the unexpected load and are currently evaluating a proper long-term solution.
The additional load is being successfully absorbed, and our teams continue to investigate the situation.
Sep 2, 20:11 UTC
The additional load is being successfully absorbed, and our teams continue to investigate the situation.
Sep 2, 20:11 UTC
Investigating -
We are investigating an unexpected increase in load on our authentication endpoints. Our teams are actively investigating the situation.
Sep 2, 19:33 UTC
Sep 2, 19:33 UTC
Sep 1, 2026
Resolved -
The incident is resolved, intelligence objects are now loading as expected.
Sep 1, 12:18 UTC
Sep 1, 12:18 UTC
Monitoring -
Objects are displayed as expected and showing positive signs or recovery, we're monitoring the situation.
Sep 1, 12:07 UTC
Sep 1, 12:07 UTC
Identified -
We've identified the root cause and are working on deploying a fix to restore intelligence objects access promptly.
Sep 1, 12:06 UTC
Sep 1, 12:06 UTC
Investigating -
We are currently investigating an issue where intelligence objects are not accessible (returning 404 errors).
Sep 1, 12:03 UTC
Sep 1, 12:03 UTC
Aug 31, 2026
No incidents reported.
Aug 30, 2026
No incidents reported.
Aug 29, 2026
No incidents reported.
Aug 28, 2026
Resolved -
The processing lag has been fully resolved, and all services are now operating normally.
We apologize for the disruption and thank you for your patience.
Aug 28, 16:56 UTC
We apologize for the disruption and thank you for your patience.
Aug 28, 16:56 UTC
Update -
Processing lag is still present, but it is gradually resolving.
We will provide a final update once full performance is completely restored.
Aug 28, 16:20 UTC
We will provide a final update once full performance is completely restored.
Aug 28, 16:20 UTC
Monitoring -
Mitigation actions have been applied to our components, and event ingestion is currently recovering. Our team is actively monitoring the pipeline to ensure full stability as the processing backlog clears.
We will provide a final update once the system has completely recovered.
Aug 28, 15:42 UTC
We will provide a final update once the system has completely recovered.
Aug 28, 15:42 UTC
Identified -
We are currently experiencing an issue with our event ingestion pipeline, causing delays or failures in processing incoming events.
Our engineering team is actively investigating the root cause and working to restore full service as quickly as possible.
We will share further updates as soon as we have more information.
Aug 28, 15:30 UTC
Our engineering team is actively investigating the root cause and working to restore full service as quickly as possible.
We will share further updates as soon as we have more information.
Aug 28, 15:30 UTC
Aug 27, 2026
Resolved -
Service has resumed successfully. Some residual lag may remain, but it is gradually clearing.
The incident is now resolved.
Aug 27, 11:02 UTC
The incident is now resolved.
Aug 27, 11:02 UTC
Monitoring -
The issue has been resolved, and event ingestion has returned to normal. The delay affecting event ingestion is gradually clearing.
We continue to monitor the service to confirm that it remains stable.
Aug 27, 10:49 UTC
We continue to monitor the service to confirm that it remains stable.
Aug 27, 10:49 UTC
Update -
Event ingestion has resumed for some communities. Our teams are continuing to work on the remaining impact and restore normal processing for all affected communities.
Aug 27, 10:32 UTC
Aug 27, 10:32 UTC
Identified -
Event ingestion is currently unavailable due to an issue affecting our Kafka infrastructure. Our teams are working to restore the service and will provide an update as soon as more information is available.
Aug 27, 10:19 UTC
Aug 27, 10:19 UTC
Aug 26, 2026
No incidents reported.
Aug 25, 2026
Resolved -
The platform is now performing under normal conditions.
We thank you again for your patience during resolution, and apologize for inconvenience caused.
Aug 25, 12:33 UTC
We thank you again for your patience during resolution, and apologize for inconvenience caused.
Aug 25, 12:33 UTC
Update -
Our Engineering team have completed all recovery operations. The platform is now performing under normal conditions.
We thank you again for your patience during resolution, and apologize for inconvenience caused.
Aug 25, 11:32 UTC
We thank you again for your patience during resolution, and apologize for inconvenience caused.
Aug 25, 11:32 UTC
Update -
Our Engineering team continues to monitor the recovery while the delay in events availability in the platform is decreasing.
We thank you for your patience during resolution.
Aug 25, 10:01 UTC
We thank you for your patience during resolution.
Aug 25, 10:01 UTC
Monitoring -
Our Engineering team has stabilized the platform and Ingestion is fully operational.
Event storage and detection are being affected by delays as a consequence of the prior Ingestion instability.
The situation is currently recovering.
Aug 25, 08:28 UTC
Event storage and detection are being affected by delays as a consequence of the prior Ingestion instability.
The situation is currently recovering.
Aug 25, 08:28 UTC
Identified -
Our Engineering team has identified an issue impacting our Event Ingestion and preventing the platform to manage some incoming queries.
The team has resolved the event ingestion and is now monitoring the situation.
We thank you for your patience during the resolution and apologize for inconvenience caused.
Aug 25, 08:09 UTC
The team has resolved the event ingestion and is now monitoring the situation.
We thank you for your patience during the resolution and apologize for inconvenience caused.
Aug 25, 08:09 UTC