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

Quick Take

1. 01 Allium reports normal delivery across three cloud platforms, while historical backfills continue for parts of its crypto data service.
2. 02 Specified Snowflake and Databricks tables passed checks, while BigQuery backfills continue.
3. 03 Published recovery instructions call for replacement API keys and new passwords, while uploaded data and some features remain restricted.

Make CryptoSlate preferred on Share Share

Blockchain data provider Allium has restored data delivery after a security incident, but users should still check historical coverage before relying on records spanning the disruption.

Its Oct. 28 datashare update says delivery is operating normally for all chains on Snowflake, Databricks and BigQuery. Historical backfills, which fill records from the affected period, remain in progress across parts of the service.

Allium’s published recovery instructions also retain feature restrictions and credential changes.

Allium disclosed the incident on Oct. 28, saying it identified unauthorized access to certain systems on Oct. 25. It said it restricted access, notified affected customers directly, and engaged an independent cybersecurity firm.

On Snowflake and Databricks, Allium says raw and enriched tables for 18 named chains, including Ethereum, Solana, Bitcoin, Base, Arbitrum and Arc, passed its existing completeness and freshness checks.

Allium says additional validation continues, Hyperliquid remains in progress, and backfills of the affected window continue for other chains and for all chains on BigQuery. BigQuery’s historical recovery remains a separate task even where the same chains have passed checks on Snowflake and Databricks.

The update also explains why tables’ verified_until timestamps may appear stale. Allium attributes that lag to automated re-verification being restored and says it does not indicate missing data. Users should distinguish that timestamp lag from the historical backfills the company says are continuing.

For teams using Allium data in research, reconciliation, or product infrastructure, the practical check is the combination of warehouse, chain, and historical window.

Related Reading

The Explorer incident record marked core Explorer and API services restored at 10:59 a.m. EDT on Oct. 28. Its published recovery instructions say existing API keys are being revoked and users should create replacements unless their Allium contact is issuing one. They also call for a new password and recommend multi-factor authentication.

The same recovery instructions say Allium has temporarily disabled new uploads and access to previously uploaded data, preventing queries that depend on uploaded tables.

For users returning to historical analysis, confirmation that the affected backfills and verification are complete will determine when the recovery question is settled.

Article context

Mentioned in this article

Related Asset Bitcoin BTC · $78,440.21 24-hour change: down 1.89% Related Asset Ethereum ETH · $2,245.28 24-hour change: down 2.86% Related Asset Solana SOL · $98.04 24-hour change: down 1.98% Featured Technology Hacks Outage

Editorial credits

Gino Matos Reporter • CryptoSlate

Gino Matos is a law school graduate and a seasoned journalist with six years of experience in the crypto industry. His expertise primarily focuses on the Brazilian blockchain…

X LinkedIn More from Gino

Exchanges

CoinDCX’s $16 million loss revives uncomfortable memories of FTX and Celsius

3 min read 3 days ago

More coverage

Oct 22, 2026 Bearish

Oct 14, 2026

Oct 7, 2026