Adeptcore incident

ELK Datacenter Outage

Major Resolved View vendor source →

Adeptcore experienced a major incident on January 31, 2026 affecting ACP - Network, lasting 2d 1h. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2026, 04:46 PM UTC
Resolved
Feb 02, 2026, 06:27 PM UTC
Duration
2d 1h
Detected by Pingoru
Jan 31, 2026, 04:46 PM UTC

Affected components

ACP - Network

Update timeline

  1. investigating Jan 31, 2026, 04:46 PM UTC

    We have received reports about an outage at our ELK Datacenter. We are currently investigating this issue and working with Datacenter Engineers to resolve this problem as quickly as possible. We will update this status as information becomes available.

  2. investigating Jan 31, 2026, 05:11 PM UTC

    we are continuing to investigate the issue. The primary causes at this time are believed to be a hardware or routing issue. We are interfacing with Datacenter engineers to get this resolved as quickly as possible.

  3. investigating Jan 31, 2026, 05:47 PM UTC

    Datacenter engineers are still investigating this issue. We will provide more updates as information becomes available.

  4. investigating Jan 31, 2026, 06:40 PM UTC

    We are continuing to investigate this issue and believe we have identified the issue in cooperation with the Datacenter engineers and are working on applying a fix.

  5. investigating Jan 31, 2026, 07:29 PM UTC

    We have identified the issue as a data center core routing issue affecting our cabinets and are tracing the issue to identify the exact cause and to restore our network configuration

  6. investigating Jan 31, 2026, 08:11 PM UTC

    We have begun doing a test restore of a backup of the networking configuration to new hardware

  7. monitoring Jan 31, 2026, 08:30 PM UTC

    We are now seeing systems come back online after the restore and are awaiting Datacenter engineers to provide a full write up of the cause and why this took so long to be resolved. We are continuing to monitor the situation.

  8. resolved Mar 09, 2026, 05:27 PM UTC

    This incident has been resolved.