Is Allium down?

We are currently experiencing with our Explorer endpoint infrastructure. Will provide updates when we have it.

Allium's Explorer remains unavailable. We'll provide another update in the next 2 hours.

We are prioritizing bringing services back online and will update you as soon as service is restored.

Allium has taken the Allium App offline as a precautionary step to fully restoring services.

We are continuing to work on restoring the Allium App. There is no change in status since our last update. We will post our next update by 14:00 UTC.

We are continuing to work on restoring the Allium App. There is no change in status since our last update. We will post our next update by 17:00 UTC.

Allium Explorer and Explorer API are back online. Allium Assistant and the Allium MCP are not yet available, and we’ll post an update when they’re back. As a security precaution, the following changes are in effect: - API keys: existing API keys are being revoked. Please create a new key in the app to restore API access. If your Allium contact is issuing you a new key directly, no action is needed until you receive it. - Password and multi-factor authentication: please set a new password when you sign in, and we recommend turning on multi-factor authentication. - Uploaded data: uploading new data and accessing previously uploaded data are temporarily disabled. Queries that use uploaded tables won’t run until this is re-enabled. We are monitoring performance closely and will post an update once we confirm stability.

Core Allium Explorer and API Restored.

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 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.

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.