Allium incident

Hyperliquid API degradation

Major Resolved View vendor source →

Allium experienced a major incident on September 21, 2026 affecting Hyperliquid Endpoints, lasting 1h 40m. The incident has been resolved; the full update timeline is below.

Started
Sep 21, 2026, 07:56 AM UTC
Resolved
Sep 21, 2026, 09:37 AM UTC
Duration
1h 40m
Detected by Pingoru
Sep 21, 2026, 07:56 AM UTC

Affected components

Hyperliquid Endpoints

Update timeline

  1. investigating Sep 21, 2026, 07:56 AM UTC

    We are currently experiencing degraded ingestion in one of our Hyperliquid orders ingestion flows, which may result in incomplete data for affected users of the hyperliquid API. Our team is actively investigating the issue and working to restore normal ingestion as quickly as possible. We will provide an update here as soon as we have more information.

  2. monitoring Sep 21, 2026, 08:40 AM UTC

    We have identified the cause of the issue and implemented a fix. Hyperliquid order ingestion has returned to normal, and new data flowing into the Postgres tables is complete and accurate.

  3. resolved Sep 21, 2026, 09:37 AM UTC

    We have investigated the root cause and found that a new upstream feature, Trailing Stops, introduced a longer trigger_condition value than our Postgres schema accounted for, causing writes to fail. We widened the column to accommodate it, and the pipeline was fully recovered by 08:30 UTC.