Resolved after 2 hours 34 minutes, affecting WebSocket API and HTTP API, on October 25, 2026.
This incident has been resolved. From approximately 20:15 UTC to 21:57 UTC, the FFIOMD HTTP and WebSocket APIs served from the par1 data center were unavailable. The cause was a network disruption at our upstream provider’s par1 facility, triggered by excessive traffic from third-party systems. The provider isolated those systems and restored connectivity at 21:57 UTC. Services have been stable since. The jfk1 data center was not affected and stayed fully operational throughout the incident.
Affected components
Update timeline
- investigating Oct 25, 2026, 09:04 PM UTC
Coin Metrics is currently experiencing an outage which has partially impacted access to our FFIOMD HTTP and Websocket APIs. Only the par1 data center is impacted. We are actively investigating the issue and will share updates as they are available.
- investigating Oct 25, 2026, 09:40 PM UTC
Update: Starting at approximately 20:15 UTC, the FFIOMD HTTP and WebSocket APIs served from the par1 data center have been unavailable due to a network connectivity issue with an upstream provider. Requests and WebSocket connections to par1 may fail, time out, or deliver delayed data. The jfk1 data center is not affected and remains fully operational for both HTTP and WebSocket APIs. We are working with our network provider to restore par1 connectivity and will provide another update as soon as more information is available.
- monitoring Oct 25, 2026, 10:36 PM UTC
Our network provider has made a change that restored connectivity to the par1 data center. The FFIOMD HTTP and WebSocket APIs served from par1 are reachable again. The provider is still investigating the root cause. We are monitoring systems closely to confirm full stability. The jfk1 data center was not affected during this incident.
- resolved Oct 25, 2026, 11:39 PM UTC
This incident has been resolved. From approximately 20:15 UTC to 21:57 UTC, the FFIOMD HTTP and WebSocket APIs served from the par1 data center were unavailable. The cause was a network disruption at our upstream provider’s par1 facility, triggered by excessive traffic from third-party systems. The provider isolated those systems and restored connectivity at 21:57 UTC. Services have been stable since. The jfk1 data center was not affected and stayed fully operational throughout the incident.
Your product runs on more than Coin Metrics
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services