The Ledger
Allium Clears Historical Data Checks Across Every Chain and Region
Allium says historical verification checks have passed for datashares across every chain and region, after delivery resumed following its October security incident. The company also reports core platform recovery, while some features remain unavailable and security measures affect customer access.

Allium says historical verification checks have now passed for datashares covering every chain across every region, marking a recovery milestone after its October security incident. In an update posted at 11:03 a.m. EDT on Friday, Oct. 30, the blockchain data provider said delivery was operating normally through Snowflake, BigQuery and Databricks. The status page still lists the datashare incident as unresolved, however, and shows partial outages for parts of Allium’s app and Explorer.
All chains pass historical checks
The Oct. 30 update expands on a narrower report from two days earlier. On Oct. 28, Allium said raw and enriched tables for 18 named chains had passed its existing completeness and freshness checks on Snowflake and Databricks, while Hyperliquid remained in progress and work continued on other chains and on BigQuery backfills. The newer notice says historical checks have passed across all chains and regions on the three data-sharing platforms.
Allium had resumed datashare delivery on Oct. 27 after tables stopped receiving new data on Oct. 26. During the interruption, customers could encounter stale records or errors when querying the tables. The company’s latest update reports that delivery is normal and historical verification is complete, but it does not say that the underlying security investigation has concluded.
Core access returns with restrictions
Allium’s Explorer and Explorer API returned on Oct. 28, according to the company’s status page. The page lists the Allium App, Explorer UI and Explorer Queries as partially unavailable. Its incident notice also said Allium Assistant and the Allium MCP were not yet available when core services came back online.
Security precautions affect customer access as well. Allium is revoking existing API keys and tells users to create replacements, unless their Allium contact is issuing a new key directly. The company asks users to set a new password and recommends multifactor authentication; uploads of new data and access to previously uploaded data remain temporarily disabled, leaving queries that rely on uploaded tables unavailable.
Allium has not described the intrusion method
Allium says it identified unauthorized access to certain systems on Oct. 25, restricted access and notified affected customers directly. It has engaged an independent cybersecurity firm to support its response and investigation, and says it plans to share a summary of findings and response measures after the investigation.
“We’re sorry for the disruption this has caused our customers. We know maintaining their trust requires clear communication and follow-through, and we’re committed to both.”
Ethan Chan, CEO and co-founder of Allium
The company’s public update does not explain how the unauthorized access occurred or say whether customer information was accessed. The Oct. 28 update referred to completeness and freshness verification; the Oct. 30 update reports historical checks across all chains and regions without specifying those measures. The status page continues to carry an unresolved datashare incident notice even as the Oct. 30 update reports that historical checks have passed.
Sources
- Original source · Status page Allium Status status.allium.so
Other pages read
- Allium allium.so