Allium incident

Chain Ingestion Degradation

Major Resolved View vendor source →
Started
Feb 16, 2026, 02:06 AM UTC
Resolved
Feb 16, 2026, 12:47 PM UTC
Duration
10h 40m
Detected by Pingoru
Feb 16, 2026, 02:06 AM UTC

Affected components

Explorer UIExplorer Queries

Update timeline

  1. investigating Feb 16, 2026, 02:06 AM UTC

    We are experiencing degraded ingestion across several blockchains. Affected services will have stale data - Allium Explorer - Allium Developer - Datashares and Datastreams We are in the process of investigation and will post hourly updates.

  2. identified Feb 16, 2026, 03:12 AM UTC

    We have identified the issue and have rolled out a mitigation. Data freshness is improving across the components. We will carry out backfills for missing data when the system is stable. Components affected - Allium Developers - Allium Explorer - Datashares - Datastreams

  3. monitoring Feb 16, 2026, 04:53 AM UTC

    We have isolated the issue to evm contract ingestions. Other raw entities (blocks, logs, traces, transactions) are not impacted at the moment. Our engineers are working on root-causing and rolling out a fix.

  4. monitoring Feb 16, 2026, 06:19 AM UTC

    We have identified the root-cause and have rolled out a fix. We are continuing to monitor the ingestion and will begin data patching when the system is stable

  5. resolved Feb 16, 2026, 12:47 PM UTC

    This incident has been resolved. EVM contract ingestions are now stable and data has been patched.

Looking to track Allium downtime and outages?

Pingoru polls Allium's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Allium reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Allium alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Allium for free

5 free monitors · No credit card required