Host Connectivity Failure

Update timeline

1. resolved Feb 15, 2026, 07:00 PM UTC

   Type: Incident Duration: 3 hours and 21 minutes Affected Components: Crypto Low Latency Top-of-Book Benchmark Endpoint, , Crypto Prices Endpoint, Tiingo API Website, News Feed Endpoint, Crypto Low-Latency Last Price Benchmark Endpoint, End-of-Day Prices Endpoint, Equity Fundamentals Endpoint, IEX Real-time Equity Endpoint, FX Prices Endpoint, Mutual Fund & ETF Fee Endpoint, Tiingo API → Feb 15, 19:00:04 GMT+0 - Identified - We identified the issue and are issuing a failover. All affected clients should switch to secondary sites during this time. Feb 15, 19:30:07 GMT+0 - Monitoring - We are proceeding with a full failover while we await host resolution. Secondary sites remain fully functional. Feb 15, 20:19:19 GMT+0 - Identified - We are continuing the failover and awaiting host updates. We anticipate an additional 1-2 hours. Feb 15, 21:42:25 GMT+0 - Monitoring - Services are recovering from our failover initiation. Host continues to investigate root cause. Feb 15, 21:58:54 GMT+0 - Monitoring - Services are operational, we are monitoring the failover. Feb 15, 22:21:18 GMT+0 - Resolved - This incident has been resolved and we will continue to monitor the failover stability as well as continue comms with our host. Feb 16, 02:00:48 GMT+0 - Postmortem - On February 15th, our primary hosting facility experienced an infrastructure-level power failure that impacted several nodes, including systems supporting our primary data site. As a result, the primary data site was temporarily unavailable. We initiated full infrastructure rebuild procedures and performed comprehensive data integrity validation before restoring and republishing Benchmark and Crypto feeds. Full restoration was completed in approximately 2.5 hours, followed by a controlled and gradual reactivation of dependent services. Our secondary site remained fully operational throughout the event and was designed to support this exact scenario. Enterprise and Institutional clients ingesting crypto feeds via the secondary endpoint should have experienced minimal or no disruption, assuming standard integration configuration. We are continuing to review the event in coordination with our infrastructure provider.