Dune Outage History

Bitcoin data and downstream are stale, stopped progressing. We are investigating the issue.

No new data since June 10th 9pm UTC. We are investigating the root cause and will provide a status update as soon as possible.

Tables related to Aptos are stale and not being updated. We are investigating the issue

Ethereum data on Dune is currently delayed — new blocks, logs, and traces after 13:57 UTC are not yet available, and queries against Ethereum tables may return incomplete recent data. Other blockchains are not affected.

The BNB chain ingestion has stopped progressing as of ~06:30 UTC. Raw blocks are not being written, downstream tables are behind.

We're encountering infrastructure issues and datashare syncs on Snowflake are stale as a result.

5 blocks cannot be indexed at the moment. We are investigating.

Some decoded tables on Arbitrum do not have full coverage of events and traces since contract was created.

We have identified the root cause and are rolling out a fix

An internal migration broke contract views for BNB and Polygon blockchains. We are investigating the issue

Queries, dashboards, and API responses that reference Ink block 34899772 specifically (transactions, logs, traces, receipts) will reflect data from the orphaned block. All other Ink blocks, and all other chains, are unaffected. If you have questions or believe you are affected, please reach out via support.

Service outage caused by a vendor issue.

We are observing an issue with our Tezos EVM pipeline affecting the progress of all tables.

Partial outage affecting Dune Agent - chat functionality is operational, but responses may be slower than usual.

Data ingestion for the Abstract blockchain is currently lagging behind chain tip. Queries against Abstract tables on Dune may return stale results until ingestion catches up. We're investigating and working on a fix.

We are currently experiencing a delay in our worldchain ingestion pipeline. Queries, dashboards, and Datashare feeds that depend on this table will return data that is stale beyond our usual freshness SLO. Team is actively working on a fix

Fuel Data Pipeline SLO Breach We are investigating a latency issue affecting the Fuel blockchain data pipeline in production. Affected tables: fuel.blocks, fuel.receipts, fuel.transactions Queries and dashboards relying on Fuel data may return stale results.

ethereum latest transaction is from 2026-05-09 on Dune we are investigating and working on it

blocks 66304721 and 66411108 are currently missed from Celo chain on Dune

We’ve identified a data quality issue affecting Stellar tables in the stellar.* schema for 2026-04-17, with three tables (stellar.accountbalances, stellar.tokenbalances, stellar.accounttokenactivity) also affected through 2026-04-21. Queries against these tables for the affected dates may return duplicate or missing rows.

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.