Adeptcore incident

Elk Datacenter Issues

Critical Resolved View vendor source →

Adeptcore experienced a critical incident on March 23, 2023 affecting ACP - Storage, lasting 55d 3h. The incident has been resolved; the full update timeline is below.

Started
Mar 23, 2023, 04:58 PM UTC
Resolved
May 17, 2023, 08:54 PM UTC
Duration
55d 3h
Detected by Pingoru
Mar 23, 2023, 04:58 PM UTC

Affected components

ACP - Storage

Update timeline

  1. investigating Mar 23, 2023, 04:58 PM UTC

    We are aware of reports about some VM's at our ELK data center and are looking into the issue. We will update you as we get more information.

  2. identified Mar 23, 2023, 05:25 PM UTC

    We have identified the issue to be storage related and have resolved the issue. We are working on bringing all effected VM's back online currently.

  3. identified Mar 23, 2023, 05:38 PM UTC

    It appears that the storage is continuing to experience issues. Storage engineers are currently looking at the cluster and this issue is actively being worked on.

  4. monitoring Mar 23, 2023, 06:12 PM UTC

    It appears this issue has been resolved once again. All servers at this time appear to be back online and functional. If you have any continued issues, please email us at [email protected] and we can take a look. We are still investigating the root cause and will update this status once we determine the cause of the issues.

  5. identified Apr 04, 2023, 01:57 PM UTC

    We have received additional reports regarding virtual machines showing offline at our ELK datacenter. The storage engineers have confirmed the issue is related to storage and are working on resolving it now.

  6. monitoring Apr 04, 2023, 02:49 PM UTC

    The storage issue was resolved around 30 minutes ago and all virtual machines appear to be functioning correctly. We are continuing to monitor the infrastructure and are working with the storage engineers to determine the exact cause and to prevent this issue from reoccurring in the future.

  7. resolved May 17, 2023, 08:54 PM UTC

    This incident has been resolved.