Blockchain data provider Allium has restored data delivery following a security incident identified on October 25, but users are advised to verify historical coverage before relying on records spanning the disruption period.
Allium disclosed the incident on October 28, stating it identified unauthorized access to certain systems, restricted access, notified affected customers directly, and engaged an independent cybersecurity firm.
Restoration Status Across Platforms
According to Allium's October 28 datashare update, delivery is operating normally for all chains on Snowflake, Databricks, and BigQuery. On Snowflake and Databricks, raw and enriched tables for 18 named chains—including Ethereum, Solana, Bitcoin, Base, Arbitrum, and Arc—have passed the company's completeness and freshness checks.
However, historical backfills remain in progress across parts of the service. Hyperliquid recovery is still ongoing, and BigQuery's historical recovery continues as a separate task even where the same chains have passed checks on other platforms.
Ongoing Recovery Work
Allium notes that additional validation continues and users may notice that tables' verified_until timestamps appear stale. The company attributes this lag to automated re-verification being restored and states it does not indicate missing data.
For teams using Allium data in research, reconciliation, or product infrastructure, the practical check involves confirming the combination of warehouse, chain, and historical window.
Account and Access Changes
Allium's published recovery instructions require credential changes for affected users. Existing API keys are being revoked, and users must create replacements unless their Allium contact is issuing one. Users are also required to set a new password, with multi-factor authentication recommended.
The company has temporarily disabled new uploads and access to previously uploaded data, preventing queries that depend on uploaded tables.
