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 25 (0%) |
Incidents, newest first
Notice February 19, 2026 Data Outage at Bitstamp – Market Data Vendor, WebSocket API
Started Feb 19, 2026, 03:27 PM UTC· resolved Feb 19, 2026, 03:27 PM UTC
- resolved Feb 19, 2026, 03:27 PM UTC
Bitstamp experienced an outage impacting spot trades data. This data has since recovered, and is now flowing as expected. The outage ended at 15:23 UTC and lasted a total of 10 minutes.
Notice February 18, 2026 Network Data Metric Delay 1h 50m Network Data Pro Changes, Network Data Pro
Started Feb 18, 2026, 04:28 PM UTC· resolved Feb 18, 2026, 06:18 PM UTC
No vendor updates were posted for this incident.
Notice February 17, 2026 Delayed Data on catalog-v2/market-metrics 13d 17h Market Data Feed
Started Feb 17, 2026, 05:25 PM UTC· resolved Mar 03, 2026, 10:33 AM UTC
- investigating Feb 17, 2026, 05:25 PM UTC
Data from the catalog-v2/market-metrics endpoint is currently delayed. We are investigating the cause of the issue and will share updates as they are available.
- resolved Mar 03, 2026, 10:33 AM UTC
A fix has been deployed, and this incident has resolved. Data is flowing as expected.
Notice January 26, 2026 Gemini Trade Delays 55d 21h Market Data Vendor, WebSocket API
Started Jan 26, 2026, 05:45 PM UTC· resolved Mar 23, 2026, 02:51 PM UTC
- monitoring Jan 20, 2026, 04:09 PM UTC
We are observing occurrences of intermittent trade lags across both data centers for Gemini trading pairs. We believe the issue stems from the exchange, and are monitoring the situation accordingly.
- monitoring Jan 26, 2026, 05:45 PM UTC
Our alerting observed this behavior again on 2026-01-26 at 10:37 and 13:08 UTC.
- monitoring Jan 29, 2026, 10:18 AM UTC
Our alerting observed this behavior again between 2026-01-28 22:11:53 UTC to 2026-01-29 00:14:43 UTC.
- monitoring Jan 29, 2026, 04:06 PM UTC
Our alerting observed this behavior again today at 2026-01-29T15:44:36 UTC.
- monitoring Jan 30, 2026, 09:37 PM UTC
Our alerting observed this behavior again on 2026-01-30 at 00:14 UTC.
- monitoring Feb 09, 2026, 09:15 PM UTC
Our alerting observed this behavior again on 2026-02-09 at 21:07 UTC.
- monitoring Feb 19, 2026, 07:10 PM UTC
Our alerting observed this behavior again on 2026-02-19 at 19:01 UTC.
- monitoring Feb 27, 2026, 09:39 AM UTC
Our alerting observed this behavior again on 2026-02-27 at 08:48 UTC.
- monitoring Mar 02, 2026, 12:53 PM UTC
Our alerting observed this behavior again on 2026-03-02 at 12:44 UTC.
- monitoring Mar 02, 2026, 10:58 PM UTC
Our alerting observed this behavior again on 2026-03-02 21:36 and 22:44 UTC
- monitoring Mar 05, 2026, 08:16 PM UTC
Our alerting observed this behavior again on 2026-03-05 19:13:20 UTC
- monitoring Mar 11, 2026, 12:08 PM UTC
Our alerting observed this behavior again on 2026-03-11 08:40:30 UTC
- monitoring Mar 13, 2026, 11:16 AM UTC
Our alerting observed this behavior again on 2026-03-13 02:34 UTC, 02:35 UTC, 02:36 UTC and 03:23 UTC
- monitoring Mar 16, 2026, 10:40 AM UTC
Our alerting observed this behavior again on 2026-03-14 02:02UTC
- monitoring Mar 17, 2026, 05:07 PM UTC
Our alerting observed this behavior again on 2026-03-17 at 16:56 UTC.
- monitoring Mar 18, 2026, 01:18 PM UTC
Our alerting observed this behavior again on 2026-03-18 at 10:23UTC
- monitoring Mar 23, 2026, 11:57 AM UTC
Our alerting observed this behavior again on 2026-03-20 at 20:13UTC, 2026-03-21 at 00:36UTC, 2026-03-22 at 10:23UTC and 2026-03-23 at 02:23UTC.
- resolved Mar 23, 2026, 02:51 PM UTC
Trade delays have been identified as an ongoing issue caused by out-of-order trades received via Gemini’s API. As this behavior is persistent and outside our direct control, we will no longer actively track updates under this incident. We will open a new incident if conditions change or the issue shows signs of improvement.