Dune: 91 Chains. No Room for Failures.
Dune parses onchain data across 130+ chains for institutions like Visa, UBS, and Bloomberg. See how consolidating onto Quicknode took them from 16 to 91 chains, cut overages, and hit a 30-day go-live window on every launch.
- 91 chains91 of the 130+ chains Dune parses run through Quicknode as primary data infrastructure
- 200M+ 200M+ Daily API responses
- 30-day 30-day 30 days to go live on every new chain. Every time
Dune is the blockchain data and intelligence provider for institutions, turning raw onchain activity into structured, parsed datasets across stablecoins, tokens, lending, and trading. That data is delivered directly into the environment a team already runs: their warehouse, their BI tool, their API stack. Protocols, exchanges, and asset managers build decisions on it, so it has to be right every time. When a pipeline breaks upstream, the damage doesn't stay with Dune. It reaches every dashboard, every report, every number a team uses to make an important decision.
挑戰
Dune ingests raw blockchain data (traces, logs, receipts), both historically and live, across every chain it covers. For a while, that sourcing ran across multiple node providers, routing traffic between them manually and patching gaps as they appeared. Overages hit almost every month. Not from runaway growth. From the ordinary cost of covering more chains with billing models that didn't fit how Dune actually scaled. Finance had no clean number to work from. Engineering spent time on routing problems that had nothing to do with Dune's product. Then there is the 30-day rule. Every new chain Dune ingests has to be ready to query within 30 days: parsed, structured, and accurate from day one. Coverage that lags behind a mainnet launch is coverage that customers notice.
解決方案
Dune consolidated onto Quicknode as its primary provider.
The overages stopped. A drawdown plan replaced monthly billing variance with a fixed credit pool. Engineering went back to building the transformation logic Dune's customers actually depend on.
Quicknode's chain coverage runs close enough to Dune's expansion pace that new chain commitments land as execution problems, not sourcing emergencies.
結果
16 chains to 91 of the 130+ chains Dune parses run through Quicknode as primary data infrastructure. In 12 months.
30-day go-live window. Met on every chain. That's 75 windows.
Daily API responses: 70 million to over 200 million. The stack scaled with them.
"Dune is infrastructure for other people's infrastructure. When something breaks upstream, it doesn't stop with us. It lands everywhere our data does. Quicknode became our primary provider because the consistency held. At 200 million API responses a day across 91 chains, it still does. "— Jonathan Skrzypek, VP of EngineeringDune