Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for SEKOIA.IO and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for SEKOIA.IO.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
EUR1 - XDR | Active |
FRA2 - XDR (SecNumCloud / PCI DSS region) | Active |
MCO1 - XDR | Active |
UAE1 - XDR | Active |
FRA1 - CTI | Active |
API consumption | Active |
Enrichers | Active |
MISP consumption | Active |
Search | Active |
TAXII consumption | Active |
Web application | Active |
FRA1 - XDR | Active |
Automation | Active |
Case management | Active |
Detection | Active |
Event storage | Active |
Hunting | Active |
Ingestion | Active |
Threat Intelligence for research & triage | Active |
Web application | Active |
View the latest incidents for SEKOIA.IO and check for official updates:
Description: Today at 11:16 CEST, an issue with an unexpected surge in alerts arose, which has since been resolved. This was linked to a recent update in the Microsoft 365 Defender format, which included relocating certain process information to process.parent for AdvancedHunting-DeviceEvents and AdvancedHunting-DeviceProcessEvents. Resolution Summary: - The Microsoft Defender for Endpoint integration was reverted to its previous version to stop potentially false positive alerts. - We are addressing and dismissing non-relevant alerts that were raised. Thank you for your understanding and patience. The incident is now fully resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 9, 2024, 9:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 7, 2024, 3:55 p.m.
Description: Due to expired credentials, new playbooks run could not start between 18:45 CEST yesterday and 10:05 CEST today. A bug in our observability stack prevented the on-call team from being paged at the right time. During that time, existing triggers and connectors kept running without errors, but node runs were unable to start. The root cause has now been identified and resolved. Additionally, steps are being taken to enhance the observability stack to prevent future occurrences. We apologize for any inconvenience caused by this incident.
Status: Resolved
Impact: Major | Started At: Aug. 22, 2024, 9:25 a.m.
Description: We are now processing playbooks in real-time. This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Aug. 20, 2024, 11:36 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Aug. 5, 2024, 8:55 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.