Allium had 52 outages in the last 2 years totaling 730h 3m of downtime — averaging 2.1 incidents per month.
There were 52 Allium outages since May 30, 2025 totaling 730h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently having ingestion issues with Cosmos as the chain seems to have stalled. Will monitor the situation and ingestion will resume once the chain is back online.
The chain seems to have resumes, ingestion is in steady state but we will still be monitoring the situation.
This incident has been resolved.
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.
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 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 are currently investigating an issue with several chains. At this time, users may experience data delays, elevated latency, or intermittent timeouts when querying recent data for these networks. All other supported chains, historical data, and other endpoints are not affected and continue to operate normally. We'll continue to share updates as we have them.
Update: The situation is largely recovered and services are returning to normal. - All other chains are fully back to normal. - Beacon chain is currently the only chain still recovering/catching up, and our team is closely monitoring it. We'll provide a final confirmation once Beacon Chain is completely back to baseline.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently having ingestion issues with Solana Testnet as the chain seems to have stalled. Will monitor the situation and ingestion will resume once the chain is back online.
This incident has been resolved.
We are investigating increased latency from our RPC providers on RobinHood Mainnet.,
The Robinhood endpoints are recovering and we are actively monitoring the system.
We are continuing to monitor for any further issues.
This incident has been resolved.
Due to an increase in Monad load, our ingestion system has been degraded. We have scaled up the systems and are actively monitoring the situation.
We are continuing to monitor for any further issues.
All affected data has now been patched and incident is resolved.
We had an issue with our token prices data provider, causing missing token prices from 30 Aug 01:30 to 05:11 UTC. The immediate issue was resolved at 05:11 UTC and prices since then are complete. We are currently backfilling token prices during the affected time range.
We are continuing to work on a fix for this issue.
Batch data has been patched and incident has since been resolved
Our team has identified the cause of a Solana testnet ingestion issue, and is working toward a resolution. The issue is the result of upstream network and RPC instability on Solana testnet. A fix is pending upstream, and we are monitoring for recovery. At this time, customers consuming Solana testnet data may experience missing, incomplete, or delayed data. Solana mainnet is unaffected, and all other chains are unaffected. We'll continue to share updates as we have them.
This incident has been resolved.
We are investigating delayed data for Canton chain due to upstream provider issues. Canton tables have incomplete data for blocks starting 15 July 21:00 UTC.
All affected data has now been patched and the incident is resolved.
Our robinhood chain data is currently experiencing degraded performance due to issues with RPC performance. We are currently isolating the issue and working on mitigations.
We have made configuration changes to our RPCs and we are seeing some signs of recovery. We are continuing our mitigation efforts and will keep you posted.
We have mitigated the steady state data ingestion, and are working to patch any missing data caused due to the incident.
We are continuing to work on a fix for this issue.
All affected data has now been patched and incident is resolved.
This incident has been resolved.
Optimism Mainnet appears to have stalled at block 153924191. The Allium team is investigating and will update this page as more information becomes available.
Optimism Mainnet block height is advancing again. Continuing to monitor the situation.
The Optimism Mainnet network stall at block 153924191 has been resolved. The network is advancing normally. We will continue to monitor for stability.
We are currently investigating this issue.
We've identified the issue and are currently rolling out a fix in our ingestion pipeline. Affected chains: - base - beacon - bsc - lighter - polygon
This incident has been resolved.
Apechain is currently halted. We are currently monitoring and will keep you informed on the situation.
We are continuing to monitor for any further issues.
This incident has been resolved.
The Base chain is currently halted. We are currently monitoring and will keep you informed on the situation
We are continuing to monitor for any further issues. Current status can be viewed here: https://status.base.org/incidents/5c4gm1wzbjs4
We are continuing to monitor for any further issues.
This incident has been resolved.
Our team is investigating degraded performance on replicated regions for Datashares. At this time, customers consuming Allium data via Snowflake shares in replicated (non-GCP-us-central-1) regions may experience delayed data freshness and slower-than-usual replication.
Our team has implemented a fix to resolve the degraded performance on replicated regions, and is monitoring the situation. Replication throughput on Datashares is recovering and freshness is catching up to the primary region.
Replication throughput on Datashares has recovered for all chains except Solana, which remains degraded. Ethereum, Arbitrum, BSC, Base, Bitcoin, Hyperliquid, Beacon, and the EVM / UTXO / Cosmos / Move / Other ecosystem shares are back to normal freshness. The Solana replication delay is the result of an issue with an upstream vendor. We are actively engaged with the vendor to unblock replication and will continue to monitor until Solana is fully caught up.
This incident has been resolved.
No data for sui, as the network is currently stalled at block 280,912,461. We are monitoring.
A fix has been implemented on the upstream Sui network, and Sui ingestion on Allium has resumed as of 15:50 UTC. We are continuing to monitor the recovery.
Sui experienced a second network stall starting ~21:35 UTC on 2026-05-29 during an epoch transition. Allium ingestion fully recovered by 02:21 UTC on 2026-05-30 and has been stable since. We are continuing to monitor through the next epoch boundary before resolving.
This incident has been resolved.
Our team is investigating a freshness degradation on Sui data. At this time, customers consuming Sui realtime data, datastreams or datashares may experience delayed or stalled data. The cause appears to be an upstream Sui network issue, not an Allium pipeline issue. Our ingestion will resume automatically once the Sui network resumes producing checkpoints. Historical Sui data is unaffected. Other chains and ecosystems are unaffected.
A fix has been implemented on the upstream Sui network, and Sui ingestion on Allium has resumed as of 21:00 UTC. We are continuing to monitor the recovery.
This incident has been resolved. Sui data ingestion has been restored and is stable since 21:00 UTC.
Our team has identified the cause of a data quality degradation in Solana token transfers, and is actively rolling out a fix. At this time, users querying Solana token transfers data may experience incorrect or incomplete values within the affected window. Other Solana datasets (blocks, transactions, instructions, DEX trades) and other chains are unaffected. The fix is rolling out now. Once deployed, we will backfill the affected window and verify before marking the incident resolved. We'll continue to share updates as we have them.
Our team has identified the cause of the Solana token transfers data quality degradation and the fix has been rolled out. Going-forward ingestion is healthy, and recent data from the past month is clean. We are now in the process of pruning ingested data affected by the prior defect (2026-05-19). We'll continue to update you here as the cleanup progresses.
Our team has resolved the Solana token transfers data quality degradation, and Solana token transfers should now be fully operational for all users. The historical cleanup is complete and the affected data has been pruned and reconciled. If you continue to experience an issue, please open a ticket with our support team. Thanks for your patience with us!
Our team is investigating an issue with Explorer Queries where queries are not returning data. At this time, users running queries in Explorer may see empty result sets or failed queries. Underlying data is intact. Realtime APIs, Datastreams, and Datashares are unaffected.
A fix has been implemented and we are monitoring the results.
Our Explorer query result fetching and storage pipeline experienced a temporary disruption that delayed or failed some queries between 19:37-20:19 UTC. The issue has been resolved, and we are implementing enhanced monitoring and automatic remediation to detect and resolve similar issues faster in the future.
We are currently investigating issues with the polygon chain ingestion pipeline.
We have addressed the issue in our ingestion pipeline and resolved it. Data gaps in the affected window have been patched.
This incident has been resolved.
We are currently investigating the issue.
We have deployed a fix.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our data provider is facing compute execution errors and data is failing to be refreshed. We've escalated the issue and waiting for updates.
Our data provider is still investigating and we will provide an update as soon as they have definitive findings.
Our data provider has identified the issue and systems are stable now. We're currently verifying the data in Snowflake.
The incident is resolved, and gaps of data in the affected window 16/04/2026 to 17/04/2026 (UTC) have been patched.
This incident has been resolved.
Wallet balances and Prices developer APIs experiencing higher error rates
We are continuing to investigate this issue.
The issue has been identified and remediated. All APIs are healthy since 16:01 UTC.