Is Coin Metrics down?

Effective September 22, 2026, we will update the representation of scaled futures contracts to provide consistent values for base, pair, size_asset, and contract_size across futures markets in the /reference-data/markets and /catalog-v2/markets endpoints. After this change, base and size_asset will consistently identify the underlying asset, while contract_size will represent the number of underlying units represented by one contract. For example, markets currently represented as 1000bonk or kshib will be updated to bonk and shib, respectively. Exchange-native identifiers will remain available in base_native, and existing symbol and market identifiers will not change. We will also introduce a new price_scale field to indicate how many units of size_asset are represented by the quoted price. This will allow users to calculate the underlying asset price and notional value consistently across futures markets without relying on exchange-specific symbol parsing. Trade, quote, funding rate, open interest, liquidation, price, and amount data will not be modified. **Action may be required for users who query markets using base, pair, or asset values. Queries that currently reference scaled asset identifiers may need to be updated. Users with exchange-specific logic to adjust contract quantities should also review those adjustments, as amount × contract_size will provide the correct underlying quantity following this change.

Our real-time ETH network data metrics (1m, 1h, and 1b) are currently delayed. We have deployed a fix and are monitoring the results. We will provide additional updates here as they become available.

The delay impacting real-time ETH network data metrics (1m, 1h, and 1b) has been resolved. The fix was deployed successfully, and the affected metrics are now processing as expected.

The following historical data has been corrected and can now be backfilled as needed: Data Type: Network Data Metrics -Metrics: PriceUSD, CapMrktEstUSD -Asset(s): opn_openticketingecosystem, opn -Frequencies Impacted: 1d -Time Range of Impact: full history -Metrics: FlowInBMXNtv, FlowInBMXUSD, FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowNetBMXNtv, FlowNetBMXUSD, FlowOutBMXNtv, FlowOutBMXUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInBMXCnt, FlowTfrOutBMXCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, SplyBMXNtv, SplyBMXUSD, SplyExNtv, SplyExUSD, TxExCnt -Asset(s): pyusd_eth, usd1_eth, usdc_base.eth, usdg_eth, usds_eth -Frequencies Impacted: 1h, 1d -Time Range of Impact: full history -Metrics: FlowInBMXNtv, FlowInBMXUSD, FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowOutBMXNtv, FlowOutBMXUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInBMXCnt, FlowTfrOutBMXCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, TxExCnt -Asset(s): pyusd_eth, usd1_eth, usdc_base.eth, usdg_eth, usds_eth -Frequencies Impacted: 1h, 1d -Time Range of Impact: full history

Users may be experiencing delays when pulling trade data for Binance futures markets via our WebSocket API. Downstream datasets, including candles, may also be impacted. Our team is working to deploy a fix and will provide updates here as they become available.

This incident was resolved on September 10, and our monitoring confirms that data delivery has resumed and is operating as expected.

The following historical data has been corrected and can now be backfilled as needed: - Data Types: Candles, Volume Metrics, Annualized Basis Metrics - Markets: Binance Futures Markets - Time Range of Impact: 2026-07-28 - 2026-08-20 - Frequencies Impacted: all