Elium incident

Issue on private (Outscale) hosting

Notice Resolved View vendor source →

Elium experienced a notice incident on May 13, 2024 affecting Private Hosting, lasting 1h 45m. The incident has been resolved; the full update timeline is below.

Started
May 13, 2024, 11:37 AM UTC
Resolved
May 13, 2024, 01:23 PM UTC
Duration
1h 45m
Detected by Pingoru
May 13, 2024, 11:37 AM UTC

Affected components

Private Hosting

Update timeline

  1. investigating May 13, 2024, 11:37 AM UTC

    We are detecting problems with connections to platforms hosted by our private cloud (Outscale). We investigate the problem.

  2. investigating May 13, 2024, 11:43 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 13, 2024, 11:48 AM UTC

    Some virtual machines hosted in our private cloud (Outscale) are not responding. We have contacted our cloud provider and are awaiting further information.

  4. investigating May 13, 2024, 12:02 PM UTC

    Our Cloud provider (Outscale) reported a problem with their internal network and data hosting. We are awaiting further information.

  5. investigating May 13, 2024, 12:26 PM UTC

    Our Cloud provider (Outscale) added the problem to their persistant storage, public network and API. We are awaiting further information.

  6. investigating May 13, 2024, 12:39 PM UTC

    The connection to services and virtual machines seem to be accessible again. Storage is still not working, files are not accessible.

  7. identified May 13, 2024, 12:46 PM UTC

    Our cloud provider (Outscale) notify that a fix has been implemented and that they still monitoring the results. But we still have issues with files.

  8. identified May 13, 2024, 12:56 PM UTC

    Services hosted on private Cloud (Outscale) are now restored and platforms are available but storage system seems to stil broken and files still unavailable. We are awaiting further information.

  9. monitoring May 13, 2024, 01:19 PM UTC

    Every platforms hosted on our private cloud (Outscale) have been restored.

  10. resolved May 13, 2024, 01:23 PM UTC

    This incident has been resolved.