Company Logo

Is there an SEKOIA.IO outage?

SEKOIA.IO status: Systems Active

Last checked: 58 seconds ago

Get notified about any outages, downtime or incidents for SEKOIA.IO and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

SEKOIA.IO outages and incidents

Outage and incident data over the last 30 days for SEKOIA.IO.

There have been 6 outages or incidents for SEKOIA.IO in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for SEKOIA.IO

Outlogger tracks the status of these components for Xero:

EUR1 - XDR Active
FRA2 - XDR (SecNumCloud / PCI DSS region) Active
MCO1 - XDR Active
UAE1 - XDR Active
API consumption Active
Enrichers Active
MISP consumption Active
Search Active
TAXII consumption Active
Web application Active
Automation Active
Case management Active
Detection Active
Event storage Active
Hunting Active
Ingestion Active
Threat Intelligence for research & triage Active
Web application Active
Component Status
EUR1 - XDR Active
FRA2 - XDR (SecNumCloud / PCI DSS region) Active
MCO1 - XDR Active
UAE1 - XDR Active
Active
API consumption Active
Enrichers Active
MISP consumption Active
Search Active
TAXII consumption Active
Web application Active
Active
Automation Active
Case management Active
Detection Active
Event storage Active
Hunting Active
Ingestion Active
Threat Intelligence for research & triage Active
Web application Active

Latest SEKOIA.IO outages and incidents.

View the latest incidents for SEKOIA.IO and check for official updates:

Updates:

  • Time: March 15, 2024, 10:50 a.m.
    Status: Resolved
    Update: The incident is resolved and everything should be accessible as usual now.
  • Time: March 15, 2024, 10:37 a.m.
    Status: Identified
    Update: We are applying some modifications on the database. It can cause further instabilities.
  • Time: March 15, 2024, 10:32 a.m.
    Status: Identified
    Update: We are currently handling an incident involving a database, which is used by multiple IC components. We are working towards a resolution.

Updates:

  • Time: March 15, 2024, 10:50 a.m.
    Status: Resolved
    Update: The incident is resolved and everything should be accessible as usual now.
  • Time: March 15, 2024, 10:37 a.m.
    Status: Identified
    Update: We are applying some modifications on the database. It can cause further instabilities.
  • Time: March 15, 2024, 10:32 a.m.
    Status: Identified
    Update: We are currently handling an incident involving a database, which is used by multiple IC components. We are working towards a resolution.

Updates:

  • Time: March 14, 2024, 6:27 p.m.
    Status: Resolved
    Update: Everything is stable since the last update, and we have established a list of corrective actions in order to avoid this kind of situation in the future. This incident is now resolved.
  • Time: March 14, 2024, 3:12 p.m.
    Status: Monitoring
    Update: We are fully back online and our API error rates went back to their baselines. The root cause has been identified, and a post-mortem is being written. We will be monitoring for a few moments before closing this incident.
  • Time: March 14, 2024, 2:19 p.m.
    Status: Identified
    Update: HTTP ingest is operational again, our error rate is going down gradually.
  • Time: March 14, 2024, 2:09 p.m.
    Status: Identified
    Update: We identified an issue with the central routers for the region. All APIs & the web applications are now available. HTTP ingestion is stopped for now.
  • Time: March 14, 2024, 1:22 p.m.
    Status: Investigating
    Update: We are currently experiencing issues with the web proxies of FRA1. Our team is investigating.

Updates:

  • Time: March 14, 2024, 6:27 p.m.
    Status: Resolved
    Update: Everything is stable since the last update, and we have established a list of corrective actions in order to avoid this kind of situation in the future. This incident is now resolved.
  • Time: March 14, 2024, 3:12 p.m.
    Status: Monitoring
    Update: We are fully back online and our API error rates went back to their baselines. The root cause has been identified, and a post-mortem is being written. We will be monitoring for a few moments before closing this incident.
  • Time: March 14, 2024, 2:19 p.m.
    Status: Identified
    Update: HTTP ingest is operational again, our error rate is going down gradually.
  • Time: March 14, 2024, 2:09 p.m.
    Status: Identified
    Update: We identified an issue with the central routers for the region. All APIs & the web applications are now available. HTTP ingestion is stopped for now.
  • Time: March 14, 2024, 1:22 p.m.
    Status: Investigating
    Update: We are currently experiencing issues with the web proxies of FRA1. Our team is investigating.

Updates:

  • Time: March 5, 2024, 5:11 p.m.
    Status: Resolved
    Update: Hard RAM limits were added on the processes that caused the initial crash. This incident is now resolved and shouldn't happen again.
  • Time: March 5, 2024, 4:42 p.m.
    Status: Identified
    Update: We identified a process consuming all the RAM available on one of the node that serves the distributed storage infrastructure of FRA2. We are investigating the process in order to avoid reproducing this issue
  • Time: March 5, 2024, 3:57 p.m.
    Status: Identified
    Update: It seems that FRA2 is down again, our team is investigating. We are contacting our cloud provider which may be at the root of this issue
  • Time: March 5, 2024, 2:03 p.m.
    Status: Monitoring
    Update: We identified a VM in a faulty, previously unseen state. The region is working again, but our team is still investigating the root cause of that crash.
  • Time: March 5, 2024, 1:53 p.m.
    Status: Investigating
    Update: We are experiencing an outage on one of our regions. We are currently investigating on the root cause and will keep you updated shortly.

Check the status of similar companies and alternatives to SEKOIA.IO

Qualys
Qualys

Systems Active

Ping Identity
Ping Identity

Systems Active

Veracode
Veracode

Systems Active

OPSWAT
OPSWAT

Systems Active

Sonatype
Sonatype

Systems Active

Aqua Security
Aqua Security

Systems Active

appviewx
appviewx

Systems Active

Signifyd
Signifyd

Systems Active

Alert Logic
Alert Logic

Systems Active

Red Canary
Red Canary

Systems Active

Frequently Asked Questions - SEKOIA.IO

Is there a SEKOIA.IO outage?
The current status of SEKOIA.IO is: Systems Active
Where can I find the official status page of SEKOIA.IO?
The official status page for SEKOIA.IO is here
How can I get notified if SEKOIA.IO is down or experiencing an outage?
To get notified of any status changes to SEKOIA.IO, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of SEKOIA.IO every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here

Start monitoring now!

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.

Get Started for Free