Allium restores 18 major chains, but only specific platforms are safe

Allium has restored its data delivery services following a security incident, but users should verify historical coverage before relying on records from the disruption period.

In an October 28 update, the blockchain data provider reported that live data feeds are operating normally for all supported chains on Snowflake, Databricks, and BigQuery. However, historical backfills—used to recover records from the affected timeframe—remain in progress across parts of the service.

The recovery notice also reiterates feature restrictions and credential changes that were put in place during the incident.

Allium disclosed the breach on October 28, noting that unauthorized access to certain systems was identified on October 25. The company immediately restricted access, notified affected customers, and engaged an independent cybersecurity firm to assess the situation.

On Snowflake and Databricks platforms, raw and enriched tables for 18 major chains—including Ethereum, Solana, Bitcoin, Base, Arbitrum, and Arc—have passed Allium’s completeness and freshness checks. These chains are now considered reliable for real‑time queries.

Validation efforts continue, with Hyperliquid data still being processed. Backfills for other chains and for all chains hosted on BigQuery are ongoing. Notably, BigQuery’s historical recovery is a separate process, even when the same chains have already cleared checks on Snowflake and Databricks.

The update also addresses why “verified_until” timestamps may appear outdated. Allium explains that this lag is due to the re‑activation of automated re‑verification processes and does not signal missing data. Users should differentiate between stale timestamps and the ongoing historical backfill operations.

For teams that rely on Allium data for research, reconciliation, or product infrastructure, the key validation step is to confirm consistency across the warehouse, chain, and historical window.

The Explorer incident record shows that core Explorer and API services were fully restored at 10:59 a.m. EDT on October 28. Recovery instructions require that existing API keys be revoked and replaced, a new password be set, and multi‑factor authentication be enabled. Allium has also temporarily disabled new uploads and access to previously uploaded data, preventing queries that depend on those tables.

Returning users performing historical analysis should monitor confirmation that the affected backfills and verification processes are complete; that milestone will mark the settlement of the recovery question.

Source link