Coin Metrics Outage History
Coin Metrics is up right nowPingoru has recorded 105 incidents for Coin Metrics: 105 in the last 12 months and 26 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 12 | 0 of 720 (0%) |
| May 2026 | 7 | 0 of 744 (0%) |
| June 2026 | 8 | 0 of 720 (0%) |
| July 2026 | 9 | 0 of 744 (0%) |
| August 2026 | 13 | 0 of 744 (0%) |
| September 2026 | 7 | 0 of 720 (0%) |
| October 2026 | 8 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 22 (0%) |
Incidents, newest first
Notice August 3, 2026 Trades, Candles and Volume Metrics Recalculation 7m Market Data Feed Changes
Started Aug 03, 2026, 06:45 PM UTC· resolved Aug 03, 2026, 06:53 PM UTC
- resolved Aug 03, 2026, 06:45 PM UTC
An issue with our data collection system caused a gap in Binance future trades and other downstream market data types, including candles and volume metrics. The historical data has been corrected and can now be backfilled as needed: Data Type: Trades, Candles, and Volume Metrics - Exchange: Binance futures - Frequencies Impacted: all - Time Range of Impact: 2026-07-29 - 2026-08-03
Notice August 3, 2026 Network Data Metrics Recalculation – Network Data Pro Changes
Started Aug 03, 2026, 06:20 PM UTC· resolved Aug 03, 2026, 06:20 PM UTC
- resolved Aug 03, 2026, 06:20 PM UTC
The following historical data has been corrected and can now be backfilled as needed: -Data Type: Network Data Metrics -Metrics: AdrBal1in100KCnt, AdrBal1in100MCnt, AdrBal1in10BCnt, AdrBal1in10KCnt, AdrBal1in10MCnt, AdrBal1in1BCnt, AdrBal1in1KCnt, AdrBal1in1MCnt, AdrBalCnt, AdrBalNtv0.001Cnt, AdrBalNtv0.01Cnt, AdrBalNtv0.1Cnt, AdrBalNtv1Cnt, AdrBalNtv10Cnt, AdrBalNtv100Cnt, AdrBalNtv100KCnt, AdrBalNtv10KCnt, AdrBalNtv1KCnt, AdrBalNtv1MCnt, AdrBalUSD1Cnt, AdrBalUSD10Cnt, AdrBalUSD100Cnt, AdrBalUSD100KCnt, AdrBalUSD10KCnt, AdrBalUSD10MCnt, AdrBalUSD1KCnt, AdrBalUSD1MCnt, CapMrktCurUSD, CapMrktFFUSD, CapMVRVFF, CapRealUSD, IssContNtv, IssContPctAnn, IssContPctDay, NVTAdj, NVTAdjFF, NVTAdjFF90, SplyAct10yr, SplyAct180d, SplyAct1d, SplyAct1yr, SplyAct2yr, SplyAct30d, SplyAct3yr, SplyAct4yr, SplyAct5yr, SplyAct7d, SplyAct90d, SplyActEver, SplyActPct1yr, SplyAdrBal1in100K, SplyAdrBal1in100M, SplyAdrBal1in10B, SplyAdrBal1in10K, SplyAdrBal1in10M, SplyAdrBal1in1B, SplyAdrBal1in1K, SplyAdrBal1in1M, SplyAdrBalNtv0.001, SplyAdrBalNtv0.01, SplyAdrBalNtv0.1, SplyAdrBalNtv1, SplyAdrBalNtv10, SplyAdrBalNtv100, SplyAdrBalNtv100K, SplyAdrBalNtv10K, SplyAdrBalNtv1K, SplyAdrBalNtv1M, SplyAdrBalUSD1, SplyAdrBalUSD10, SplyAdrBalUSD100, SplyAdrBalUSD100K, SplyAdrBalUSD10K, SplyAdrBalUSD10M, SplyAdrBalUSD1K, SplyAdrBalUSD1M, SplyAdrTop100, SplyAdrTop10Pct, SplyAdrTop1Pct, SplyCur, SplyExpFut10yrCMBI, SplyFF, SplyFound, SplyLost, SplyRes, SplyTeam, SplyWalBal1in100k, SplyWalBal1in100M, SplyWalBal1in10B, SplyWalBal1in10k, SplyWalBal1in10M, SplyWalBal1in1B, SplyWalBal1in1k, SplyWalBal1in1M, SplyWalBalNtv0.001, SplyWalBalNtv0.01, SplyWalBalNtv0.1, SplyWalBalNtv1, SplyWalBalNtv10, SplyWalBalNtv100, SplyWalBalNtv100k, SplyWalBalNtv10k, SplyWalBalNtv1k, SplyWalBalNtv1M, SplyWalBalUSD1, SplyWalBalUSD10, SplyWalBalUSD100, SplyWalBalUSD100k, SplyWalBalUSD10k, SplyWalBalUSD10M, SplyWalBalUSD1k, SplyWalBalUSD1M, TxTfrValAdjNtv, TxTfrValAdjUSD, TxTfrValNtv, VelCur1yr, VelCurAdj1yr, WalBalCnt -Asset: BTC -Frequencies Impacted: 1d -Time Range of Impact: genesis - present
Notice July 31, 2026 Trade Delays for Binance Futures 27d 21h Market Data Feed
Started Jul 31, 2026, 07:39 PM UTC· resolved Aug 28, 2026, 04:45 PM UTC
- investigating Jul 31, 2026, 07:39 PM UTC
We are currently experiencing delays affecting Binance Futures trades, which are also impacting dependent downstream metrics. We have identified the root cause of the issue and are actively working on a fix. We will provide updates as they become available.
- identified Aug 05, 2026, 04:39 PM UTC
This issue has been resolved for REST API users. WebSocket API users may still experience delays in Binance Futures trade data delivery. Our team is continuing to work on a comprehensive fix, and we'll provide further updates as they become available.
- identified Aug 26, 2026, 04:27 PM UTC
Delays in our historical trade collection process and incomplete real-time trade collection are impacting the completeness of Binance futures trades and candle data. We have identified the contributing factors and are implementing fixes to improve trade collection and prevent the historical feed from falling behind. Affected candles will be recalculated as the historical data catches up.
- monitoring Aug 27, 2026, 02:25 PM UTC
A fix has been implemented to backfill the affected historical Binance futures trade data. We expect the backfill to be completed within the next two days.
- resolved Aug 28, 2026, 04:45 PM UTC
We have corrected the Binance futures trade collection issue and recalculated affected candle data from 2026-07-28 through 2026-08-27. If you previously queried and persisted this candle data, please recollect it from our API to ensure you have the corrected values.
Notice July 22, 2026 Lagged Kraken Trades – WebSocket API
Started Jul 22, 2026, 02:42 PM UTC· resolved Jul 22, 2026, 02:42 PM UTC
- resolved Jul 22, 2026, 02:42 PM UTC
Our telemetry detected increased latency for Kraken trades on the FFIOMD API beginning at 21:29 UTC on 2026-07-21. We restarted our connections to the exchange, which has improved latency. We will continue to monitor our systems to ensure the issue is fully resolved.
Notice July 14, 2026 Reference Rates Recalculation – CM Prices Changes
Started Jul 14, 2026, 07:36 PM UTC· resolved Jul 14, 2026, 07:36 PM UTC
- resolved Jul 14, 2026, 07:36 PM UTC
The following historical data has been corrected and can now be backfilled as needed: - Data Type: Reference Rates - Assets: fun, gno, leo, paxg, wnxm, alpha, fxs, bit, toke, max_mastercardxstock, spyx, trx - Frequencies Impacted: 1s, 1h - Time Range of Impact: 2026-05-20 2026-06-17
Notice July 10, 2026 Network Data Metrics Recalculation – Network Data Pro Changes
Started Jul 10, 2026, 04:59 PM UTC· resolved Jul 10, 2026, 04:59 PM UTC
- resolved Jul 10, 2026, 04:59 PM UTC
We have updated the following data after identifying additional addresses. The historical data has been corrected and is now available for backfill as needed: -Data Type: Network Data Metrics -Asset(s): usdc_eth -Time Range of Impact: 2026-03-26 - Present -Metrics: FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowInKRKNtv, FlowInKRKUSD, FlowNetKRKNtv, FlowNetKRKUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowOutKRKNtv, FlowOutKRKUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInKRKCnt, FlowTfrOutKRKCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, SplyExNtv, SplyExUSD, SplyKRKNtv, SplyKRKUSD, TxExCnt -Frequencies Impacted: 1d -Metrics: FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowInKRKNtv, FlowInKRKUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowOutKRKNtv, FlowOutKRKUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInKRKCnt, FlowTfrOutKRKCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, TxExCnt -Frequencies Impacted: 1h
Notice July 9, 2026 Network Data Metrics Recalculation – Network Data Pro Changes
Started Jul 09, 2026, 06:11 PM UTC· resolved Jul 09, 2026, 06:11 PM UTC
- resolved Jul 09, 2026, 06:11 PM UTC
We have updated the following data after identifying additional addresses. The historical data has been corrected and is now available for backfill as needed: -Metrics: SplyFF, CapMrktFFUSD, NVTAdjFF, CapMVRVFF, NVTAdjFF90 -Asset(s): snx -Frequencies Impacted: 1d -Time Range of Impact: 2018-03-10 - 2026-07-09
Notice July 9, 2026 Candles Data Recalculation – Market Data Feed Changes
Started Jul 09, 2026, 06:06 PM UTC· resolved Jul 09, 2026, 06:06 PM UTC
- resolved Jul 09, 2026, 06:06 PM UTC
The following historical data has been corrected and can now be backfilled as needed: - Data Type: Spot Candles - Market(s): hyperliquid-link0-usdt0-spot - Time Range of Impact: 2025-08-28 - 2026-07-08 - Frequencies Impacted: 1m - 1d
Notice July 2, 2026 Data Notice: Toncoin (TON) is being renamed to Gram (GRAM) – Pro API v4, Network Data Pro, ATLAS
Started Jul 02, 2026, 03:12 PM UTC· resolved Jul 02, 2026, 03:12 PM UTC
- resolved Jul 02, 2026, 03:12 PM UTC
Following the TON community's on-chain governance vote, the native asset of The Open Network has rebranded from Toncoin (TON) to Gram (GRAM). This is a name and ticker change only — the underlying asset, blockchain, and our internal asset identifier are unchanged, and units map 1:1. There is no token swap. To address this rebranding, Network Data Pro metrics CapMrktEstUSD and PriceUSD will only be available under ticker GRAM.
Notice July 1, 2026 Market Data Metrics Recalculation – Market Data Feed Changes
Started Jul 01, 2026, 04:49 PM UTC· resolved Jul 01, 2026, 04:49 PM UTC
- resolved Jul 01, 2026, 04:49 PM UTC
An issue caused incorrect values for our realized volatility metrics. The following historical data has been corrected and can now be backfilled as needed: - Data Type: Realized Volatility Metrics - Metric Intervals: 60d, 90d, 120d, 180d, 270d, 1y - Frequencies Impacted: 1h - Time Range of Impact: 2010-07-19 - 2026-06-25
Notice July 1, 2026 Network Data Metrics Recalculation – Network Data Pro Changes
Started Jul 01, 2026, 04:32 PM UTC· resolved Jul 01, 2026, 04:32 PM UTC
- resolved Jul 01, 2026, 04:32 PM UTC
The following historical data has been improved due to the discovery of new addresses and can now be backfilled as needed: -Data Type: Network Data Metrics -Asset(s): usdc_eth -Metrics: FlowInMXCNtv, FlowInMXCUSD, FlowNetMXCNtv, FlowNetMXCUSD, FlowOutMXCNtv, FlowOutMXCUSD, FlowTfrInBMXCnt, FlowTfrInMXCCnt, FlowTfrOutBMXCnt, FlowTfrOutMXCCnt, SplyMXCNtv, SplyMXCUSD -Frequencies Impacted: 1d -Time Range of Impact: 2026-06-04 - 2026-06-24 -Metrics: FlowInCBSNtv, FlowInCBSUSD, FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowNetCBSNtv, FlowNetCBSUSD, FlowOutCBSNtv, FlowOutCBSUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInCBSCnt, FlowTfrOutCBSCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, SplyCBSNtv, SplyCBSUSD, SplyExNtv, SplyExUSD, TxExCnt -Frequencies Impacted: 1d -Time Range of Impact: full history
Notice June 30, 2026 Data Notice: Toncoin (TON) is being renamed to Gram (GRAM) 1d Pro API v4, Market Data Feed, CM Prices, Indexes
Started Jun 30, 2026, 04:18 PM UTC· resolved Jul 01, 2026, 05:00 PM UTC
- resolved Jun 30, 2026, 04:18 PM UTC
Following the TON community's on-chain governance vote, the native asset of The Open Network has rebranded from Toncoin (TON) to Gram (GRAM). This is a name and ticker change only — the underlying asset, blockchain, and our internal asset identifier are unchanged, and units map 1:1. There is no token swap. What's changing: Effective on 2026-06-30 at 17:00 UTC, - Ticker `ton` → `gram`; display name Toncoin → Gram. - The legacy `ton` ticker remains an accepted alias and will continue to resolve in API queries. Impact by data type: Some data types will preserve history under the GRAM ticker, while others require a historical re-keying to retain history. For data types that require re-keying, no action is being performed at this stage; a migration to unify all series under GRAM is planned for a later date. - Reference Data (assets, markets, pairs) — ✅ Seamless. Relabeled to GRAM; identifiers move from `*-ton-*` to `*-gram-*`. Legacy `ton` identifiers continue to resolve. - Market Data (spot trades, candles, quotes, order books) — ✅ Seamless. Continuous history; queryable under both the new and legacy identifiers. - Principal Market Price — ✅ Seamless. Continuous history. - Indexes (incl. CMBITM, CMBISCPE) — ✅ Seamless. Index levels continue uninterrupted; GRAM replaces TON as a constituent. - Reference Rates — ⚠️ Split at cutover. The GRAM series begins 2026-06-30 12:00 UTC; earlier history remains available under the `ton` ticker until the later migration. - Asset & Market Metrics — ⚠️ Split at cutover. GRAM from 2026-06-30 12:00 UTC onward; pre-rebrand history under `ton`. - Derivatives (futures, perpetuals) — 🆕 New series. New GRAM contracts appear as venues relist them; existing TON contracts remain as separate historical series. What you may need to do: - Update any TON/GRAM display labels in your applications. - For a continuous Reference Rate or Metrics series spanning the rebrand, query `ton` for data before 2026-06-30 17:00 UTC and `gram` from that time forward.
Notice June 24, 2026 Network Data Metrics Recalculation 5m Network Data Pro Changes
Started Jun 24, 2026, 06:35 PM UTC· resolved Jun 24, 2026, 06:41 PM UTC
- resolved Jun 24, 2026, 06:35 PM UTC
The following historical data has been updated due to newly discovered addresses, and can now be backfilled as needed: -Data Type: Network Data Metrics -Metrics: FlowInEtfInclNtv, FlowInEtfInclUSD, FlowInEtfNtv, FlowInEtfUSD, FlowInVLKNtv, FlowInVLKUSD, FlowNetVLKNtv, FlowNetVLKUSD, FlowOutEtfInclNtv, FlowOutEtfInclUSD, FlowOutEtfNtv, FlowOutEtfUSD, FlowOutVLKNtv, FlowOutVLKUSD, FlowTfrFromEtfCnt, FlowTfrFromEtfInclCnt, FlowTfrInVLKCnt, FlowTfrOutVLKCnt, FlowTfrToEtfCnt, FlowTfrToEtfInclCnt, SplyEtfNtv, SplyEtfUSD, SplyVLKNtv, SplyVLKUSD, TxEtfCnt -Asset(s): BTC -Frequencies Impacted: 1d -Time Range of Impact: 2026-04-29 - Present
Notice June 8, 2026 Candles Data Recalculation – Market Data Feed Changes
Started Jun 08, 2026, 04:29 PM UTC· resolved Jun 08, 2026, 04:29 PM UTC
- resolved Jun 08, 2026, 04:29 PM UTC
The following historical data has been corrected and can now be backfilled as needed: - Data Type: Future Candles and Volume Metrics - Exchange: CME - Time Range of Impact: 2026-05-08 - 2026-06-08 - Frequencies Impacted: all
Notice June 5, 2026 Candles Data Recalculation – Market Data Feed Changes
Started Jun 05, 2026, 01:27 PM UTC· resolved Jun 05, 2026, 01:27 PM UTC
- resolved Jun 05, 2026, 01:27 PM UTC
We identified and corrected gaps in the historical candle data for the affected market. The historical data has been corrected and can now be backfilled as needed: - Data Type: Spot Candles - Markets: okex-edge_edgex-eur-spot - Time Range of Impact: 2026-05-06 - 2026-05-18 - Frequencies Impacted: all
Notice June 3, 2026 Supply Metric Lag 5d Network Data Pro
Started Jun 03, 2026, 01:34 PM UTC· resolved Jun 08, 2026, 01:49 PM UTC
- investigating Jun 03, 2026, 01:34 PM UTC
Metric Current Supply (SplyCur) is delayed for asset SOL. Our team is investigating the issue, and we will provide updates as they are available.
- resolved Jun 08, 2026, 01:49 PM UTC
This incident was resolved on 2026-06-04. Data flow has been restored, and the affected service is operating normally.
Notice June 3, 2026 ATLAS Data Delayed 2d Network Data Pro, ATLAS
Started Jun 03, 2026, 01:22 PM UTC· resolved Jun 05, 2026, 01:28 PM UTC
- identified Jun 03, 2026, 01:22 PM UTC
We are currently experiencing delays in ATLAS for asset ZEC. Our team has identified the root cause and is actively working on a resolution. We will provide updates as they become available.
- identified Jun 04, 2026, 01:46 PM UTC
End of day Network Data metrics for ZEC have also been impacted by these delays. We are continuing to work on a resolution and will provide updates as they become available.
- resolved Jun 05, 2026, 01:28 PM UTC
This issue has been resolved with full data restoration. Data is now flowing as expected.
Notice June 2, 2026 Candles Data Recalculation – Market Data Feed Changes
Started Jun 02, 2026, 02:33 PM UTC· resolved Jun 02, 2026, 02:33 PM UTC
- resolved Jun 02, 2026, 02:33 PM UTC
The following historical data has been corrected and can now be backfilled as needed: - Data Type: Futures Candles - Market: hyperliquid xyz:JPY future - Time Range of Impact: 2026-01-07 - 2026-05-18 - Frequencies Impacted: 1m - 1d
Notice June 2, 2026 Candles and Volume Data Recalculation 3h Market Data Feed Changes
Started Jun 02, 2026, 09:00 AM UTC· resolved Jun 02, 2026, 12:00 PM UTC
- resolved Jun 02, 2026, 02:39 PM UTC
The following historical data has been corrected and can now be backfilled as needed: - Data Type: Spot Candles, Spot Volume Metrics - Exchanges: Binance - Time Range of Impact: 2026-05-31 09:00 - 2026-06-01 12:00:00 - Frequencies Impacted: all
Notice May 19, 2026 FFIOMD WS API Delays – WebSocket API
Started May 19, 2026, 08:43 PM UTC· resolved May 19, 2026, 08:43 PM UTC
- resolved May 19, 2026, 08:43 PM UTC
We experienced a brief outage for FFIOMD WebSocket API trades and quotes in our European data center due to an internal networking issue that started at 026-05-19 20:28:07.000. No data was lost due to redundancy, and data is now flowing as expected.
Notice May 15, 2026 ATLAS Data Delayed 2d 23h ATLAS
Started May 15, 2026, 04:08 PM UTC· resolved May 18, 2026, 03:54 PM UTC
- investigating May 15, 2026, 04:08 PM UTC
ATLAS data for asset BCH is delayed. We are currently investigating this issue, and will provide updates as they are available.
- resolved May 18, 2026, 03:54 PM UTC
Data is flowing as expected for BCH on ATLAS. This incident resolved on 2026-05-15.
Notice May 12, 2026 Network Data Metrics Recalculation – Network Data Pro Changes
Started May 12, 2026, 04:16 PM UTC· resolved May 12, 2026, 04:16 PM UTC
- resolved May 12, 2026, 04:16 PM UTC
Due to newly discovered addresses, historical data has been corrected and can now be backfilled as needed: -Data Type: Network Data Metrics -Asset: btc -Metrics: FlowInARKNtv, FlowInARKUSD, FlowInBLKNtv, FlowInBLKUSD, FlowInEtfInclNtv, FlowInEtfInclUSD, FlowInEtfNtv, FlowInEtfUSD, FlowInINVNtv, FlowInINVUSD, FlowInVLKNtv, FlowInVLKUSD, FlowNetARKNtv, FlowNetARKUSD, FlowNetBLKNtv, FlowNetBLKUSD, FlowNetINVNtv, FlowNetINVUSD, FlowNetVLKNtv, FlowNetVLKUSD, FlowOutARKNtv, FlowOutARKUSD, FlowOutBLKNtv, FlowOutBLKUSD, FlowOutEtfInclNtv, FlowOutEtfInclUSD, FlowOutEtfNtv, FlowOutEtfUSD, FlowOutINVNtv, FlowOutINVUSD, FlowOutVLKNtv, FlowOutVLKUSD, FlowTfrFromEtfCnt, FlowTfrFromEtfInclCnt, FlowTfrInARKCnt, FlowTfrInBLKCnt, FlowTfrInINVCnt, FlowTfrInVLKCnt, FlowTfrOutARKCnt, FlowTfrOutBLKCnt, FlowTfrOutINVCnt, FlowTfrOutVLKCnt, FlowTfrToEtfCnt, FlowTfrToEtfInclCnt, SplyARKNtv, SplyARKUSD, SplyBLKNtv, SplyBLKUSD, SplyEtfNtv, SplyEtfUSD, SplyINVNtv, SplyINVUSD, SplyVLKNtv, SplyVLKUSD, TxEtfCnt -Frequencies Impacted: 1d -Time Range of Impact: 2024-05-09 - Present -Asset: eth -Metrics: FlowInExInclNtv, FlowInExInclUSD, FlowInExNtv, FlowInExUSD, FlowInKRKNtv, FlowInKRKUSD, FlowMinerIn0HopAllExNtv, FlowMinerIn0HopAllExUSD, FlowMinerIn1HopAllExNtv, FlowMinerIn1HopAllExUSD, FlowMinerIn1HopAllKRKNtv, FlowMinerIn1HopAllKRKUSD, FlowMinerOut0HopAllExNtv, FlowMinerOut0HopAllExUSD, FlowMinerOut1HopAllExNtv, FlowMinerOut1HopAllExUSD, FlowMinerOut1HopAllKRKNtv, FlowMinerOut1HopAllKRKUSD, FlowNetKRKNtv, FlowNetKRKUSD, FlowOutExInclNtv, FlowOutExInclUSD, FlowOutExNtv, FlowOutExUSD, FlowOutKRKNtv, FlowOutKRKUSD, FlowTfrFromExCnt, FlowTfrFromExInclCnt, FlowTfrInKRKCnt, FlowTfrOutKRKCnt, FlowTfrToExCnt, FlowTfrToExInclCnt, SplyExNtv, SplyExUSD, SplyKRKNtv, SplyKRKUSD, TxExCnt -Frequencies Impacted: 1d -Time Range of Impact: 2025-08-17 - Present
Notice May 8, 2026 Data Outage at Coinbase 3d 17h Market Data Vendor
Started May 08, 2026, 07:52 PM UTC· resolved May 12, 2026, 01:16 PM UTC
- monitoring May 08, 2026, 07:52 PM UTC
Coinbase is currently experiencing an outage impacting market data.
- resolved May 12, 2026, 01:16 PM UTC
Data from Coinbase recovered and is now flowing as expected. The outage ended on 2026-05-08 at 20:00 UTC.
Notice May 8, 2026 Data Outage at Coinbase 11h 31m Market Data Vendor
Started May 08, 2026, 02:15 AM UTC· resolved May 08, 2026, 01:47 PM UTC
- monitoring May 08, 2026, 02:15 AM UTC
Coinbase is currently experiencing an outage impacting trades and quotes data. For more information, follow Coinbase’s incident report here - https://status.coinbase.com/
- resolved May 08, 2026, 01:47 PM UTC
Data from Coinbase recovered and is now flowing as expected. The outage ended at 09:30 UTC and lasted a total of 8.5 hours. For more information, follow Coinbase’s incident report here - https://status.coinbase.com/.
Notice May 6, 2026 End of Day Metrics Delayed 1d 22h Network Data Pro
Started May 06, 2026, 03:40 PM UTC· resolved May 08, 2026, 01:53 PM UTC
- identified May 06, 2026, 03:40 PM UTC
Our end-of-day network data metrics for Canton Coin (CC) are currently delayed. We have identified the underlying issue and are in the process of testing a fix. We will share updates here as they become available.
- resolved May 08, 2026, 01:53 PM UTC
Our end-of-day network data metrics for Canton Coin have recovered, and data is flowing as expected.