h8lio incident

nodes not ready

Major Resolved View vendor source →

h8lio experienced a major incident on July 23, 2025 affecting h8l.io and kube.h8l.io, lasting 2h 40m. The incident has been resolved; the full update timeline is below.

Started
Jul 23, 2025, 05:23 AM UTC
Resolved
Jul 23, 2025, 08:04 AM UTC
Duration
2h 40m
Detected by Pingoru
Jul 23, 2025, 05:23 AM UTC

Affected components

h8l.iokube.h8l.io

Update timeline

  1. identified Jul 23, 2025, 05:23 AM UTC

    The node23 is not ready. We identified the issue and the resolution is in progress.

  2. monitoring Jul 23, 2025, 06:09 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Jul 23, 2025, 06:35 AM UTC

    Several nodes are not ready (31,32,33) in the same region. We are investigating the issue and check if there is any problem is reported on the hosting provider side.

  4. investigating Jul 23, 2025, 06:36 AM UTC

    We are currently investigating this issue.

  5. monitoring Jul 23, 2025, 07:02 AM UTC

    The region issue is resolved, we are monitoring it

  6. resolved Jul 23, 2025, 08:04 AM UTC

    This incident has been resolved.