Tiingo Inc - Host Connectivity Failure – Incident details

Host Connectivity Failure

Resolved
Major outage
Started 3 months agoLasted about 3 hours

Affected

Tiingo API

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 9:21 PM

Tiingo API Website

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 12:00 AM

End-of-Day Prices Endpoint

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 9:21 PM

IEX Real-time Equity Endpoint

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 12:00 AM

News Feed Endpoint

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 12:00 AM

Equity Fundamentals Endpoint

Major outage from 7:00 PM to 9:58 PM, Operational from 9:58 PM to 12:00 AM

Updates
  • Postmortem
    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.

  • Resolved
    Resolved

    This incident has been resolved and we will continue to monitor the failover stability as well as continue comms with our host.

  • Update
    Update

    Services are operational, we are monitoring the failover.

  • Monitoring
    Monitoring

    Services are recovering from our failover initiation. Host continues to investigate root cause.

  • Identified
    Identified

    We are continuing the failover and awaiting host updates. We anticipate an additional 1-2 hours.

  • Monitoring
    Monitoring

    We are proceeding with a full failover while we await host resolution. Secondary sites remain fully functional.

  • Identified
    Identified

    We identified the issue and are issuing a failover. All affected clients should switch to secondary sites during this time.