Hyperliquid API degradation

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.

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.

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.