Dune Outage History

We've identified an issue where some of our multichain decoded tables (the cross-chain _multichain. views that union per-chain decoded data) are not including rows from a subset of chains. Affected views are returning fewer rows than the underlying per-chain tables contain. What's affected: A subset of _multichain. decoded tables, including some events under the morphov2multichain namespace. Affected rows are real and present in the per-chain tables — they are just missing from the merged multichain view. What's not affected: Per-chain decoded tables (e.g. morphov2ethereum., morphov2monad.) are returning correct, complete data. All other Dune services — dashboards, queries, the API, DuneSQL, ingestion — are unaffected.

A large amount of curated data models are not receiving any updates since 17:00 UTC This includes: - dex.trades - tokens.transfers - lending.supply - nft.transfers

data is blocked from upstream pipeline failure. a fix is being built now.

Ingestion pipleint is broken, we are working to fix asap

We’re investigating stale data on two NEAR tables (near.balances and near.circulating_supply) which have not received new data since 2026-04-17. Other NEAR tables are updating normally, so the impact is limited to these two datasets. Queries depending on them will return outdated results until ingestion is restored.

We are investigating the issue and will aim to mitigate ASAP

prices.minute is currently empty, the data was accidentally removed. We are working through a backfill of the historical data and will update the table once complete, we expect this to take several hours. Please use prices.day or prices.hour as a temporary alternative.

We are 592k blocks behind and are investigating the root cause

Aptos data is lagging behind by 3 hours. We are investigating the problem

Data is up to date

Celo blockchain data is lagging behind by 20 hours

Data is up to date

Some users are experiencing timeouts and failures when fetching query results

180,000 blocks failed to be processed affecting decoded logs.

Data is up to date

New contract submissions wouldn't be processed We are mitigating this issue and will update asap

Fixed now for all chains, please wait a few hours until contracts submitted will be rpocessed

Lag is around 7 hours.

Data is up to date as much as possible

Data last updated around 2026-02-26 21:35 UTC. We are investigating the delay.

Data caught up

Duplicate records are present on Snowflake tables from February 20th. We are investigating which tables are affected and looking for a mitigation.