Allium had 47 outages in the last 2 years totaling 3728h 59m of downtime — averaging 1.9 incidents per month.
There were 47 Allium outages since May 30, 2025 totaling 3728h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
Polygon chain has partially halted. See https://status.polygon.technology/incidents/9ysh9zczb8ml for more details.
RPC issue resolved and data is backfilled.
We are currently investigating the issue
This incident has been resolved.
Cloudflare is currently having issues. Not impacted: - APIs Degraded: - app.allium.so Down: Chain ingestion - due to upstream rpc providers
Cloudflare has implemented a fix, and our upstream rpc providers are recovering.
Everything is now stable and working.
We are experiencing heavy load on the Allium App and are working towards resolution. We will update shortly.
We are continuing to work on a fix for 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.
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.
We are monitoring the situation. Allium services impacted includes: Allium App, Allium API and Batch Data Latency for services blockchains. We will provide updates on all the blockchains affected.
Batched data from the following blockchains are experiencing latency delays: alienx apechain b3 babylon cardano core dymension manta_pacific monad sanko ton x_layer
Allium App & API services have since recovered.
All services have since resumed. We are actively monitoring the situation and updates from Cloudflare.
Allium API and Allium App services are still affected. We are monitoring the situation
Allium API and Allium App services have been resumed.
This incident has been resolved.
AWS Outage in region us-east1 impacting our realtime pipelines and causing data to be stale. AWS is aware and actively investigating.
These products are still experiencing freshness degradation: - Realtime API: EVM latest balances - Realtime API: EVM holdings - Realtime API: EVM PnL - Data shares: Snowflake AWS us-east-1 region (also inaccessible due to Snowflake AWS us-east-1 outage) - Data streams: EVM latest balances and historical balances We are still actively working on the above. These products have recovered: - Realtime API: endpoints other than those listed above - Data streams: streams other than EVM balances These products are not affected: - Allium Explorer - Allium data shares other than Snowflake AWS us-east-1
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved. Root cause: A configuration change was rolled out that modified data types in the cache. This was reverted initially, but the cache still stored incorrect data. All changes were reverted and the cache was cleared.
We are working with our RPC providers to investigate the issue.
This incident has been resolved.
We have escalated to the RPC providers and are working on mitigating the ingestion degradation.
Ingestion has resumed and we are monitoring the stability of the pipeline.
This incident has been resolved.
We have identified an issue with our RPC provider's node and is pending fixes on their end.
Ingestion is now stable and we are monitoring the ingestion pipelines. Backfills/patching will commence after the system is deemed stable.
This incident has been resolved.
The Solana Devnet is currently stalled at block 411,523,732. We are currently monitoring the situation and waiting for updates from our node provider.
This incident has been resolved.
Currently working with RPC provider on resolving Worldchain node-level issue. Realtime serving of Worldchain data via Allium API will have missing data.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate the issues. Preliminary investigations suggests that the getBlock RPC call is facing intermittent errors. We will mitigate the issue by refetching the blocks, but freshness may be degraded.
Data fixes has been rolled out to Solana tables in Snowflake GCP us-central1 and realtime APIs. We are actively working on propagating all data fixes to all other Snowflake, Databricks, and GCP BigQuery destinations.
The data fix is propagated to all downstream destinations. We are continuing to monitor effects. Note: There are reports of Kafka freshness issues - this might be due to backfilling older events into the topic. You may see occasional spikes.
This incident has been resolved.
Today at 17:00 UTC, validators voted to update network settings, and the network is now running Whisk (Protocol 23) on Mainnet. This caused our publishers to error out due to breaking changes. We are working to upgrade our ingestion systems to support Stellar protocol 23.
This incident has been resolved.
We have identified the issue and have pushed out a fix. Expected time to recovery around 30 mins.
We are continuing to work on a fix for this issue.
The incident has been resolved. Data freshness across all data regions has recovered.
The block height for Near is stalled at 160113114, due to RPC node issues. We are waiting for a resolution.
The block height for Near is stalled at 160113114, due to RPC node issues. We are waiting for a resolution.
Data is available from block height 160212657. We are in the process of resolving the data gaps.
This issue has been resolved. All Near data is now available.
We are currently investigating this issue.
The issue is being mitigated. We will continue to observe and ensure that the Sei data pipelines are healthy.
The RPC health has degraded. We working with the providers to get the system back online.
Sei ingestion is stable.
Base mainnet chain is currently stalled
This incident has been resolved.
We are awaiting a fix from the Foundation.
A fix has been implemented and the network has resumed normal operation.
RPC Provider is working with Abstract Foundation to resolve Abstract Testnet RPC issues
Belated update. This incident was resolved as of Jun 13, 2025