Tiingo Inc Outage History

Started Oct 21, 2026, 04:10 AM UTC· resolved Oct 21, 2026, 02:09 PM UTC

1. monitoring Oct 21, 2026, 04:10 AM UTC

   Blue Ocean ATS is experiencing technical difficulties and the ATS is HALTed. Please see message from their team below **BLUE OCEAN ATS Clients** October 20, 2026 Blue Ocean ATS has experienced intermittent network connectivity issues at our external network provider this evening that have impacted client connectivity. As the issue remains unresolved, we have halted all trading on the Blue Ocean ATS as of 23:46:41. We are working to restore service and will provide an update once trading is able to resume. We apologize for the disruption and appreciate your patience. Blue Ocean ATS

2. resolved Oct 21, 2026, 02:09 PM UTC

   Blue Ocean ATS resumed trading at 2:30am ET.

Read the full incident report →

Started Sep 21, 2026, 03:24 PM UTC· resolved Sep 21, 2026, 03:24 PM UTC

1. resolved Sep 21, 2026, 03:24 PM UTC

   $19

Read the full incident report →

Started Aug 07, 2026, 10:55 PM UTC· resolved Aug 08, 2026, 12:43 AM UTC

1. investigating Aug 07, 2026, 10:55 PM UTC

   We are currently investigating an incident of REST APIs having an outage. WebSockets remain functional.

2. resolved Aug 08, 2026, 12:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 18, 2026, 08:00 AM UTC· resolved Apr 18, 2026, 08:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 30, 2026, 11:18 PM UTC· resolved Mar 31, 2026, 02:38 AM UTC

1. monitoring Mar 30, 2026, 11:18 PM UTC

   Prices are loading now.

2. resolved Mar 31, 2026, 01:46 AM UTC

   Prices are back to normal schedules.

3. monitoring Mar 31, 2026, 02:38 AM UTC

   Earlier today we launched a massive update to our corp actions processing to boost coverage and reliability. This required jobs to be run after market close which delayed our EOD prices. This was a one-off event..

4. resolved Mar 31, 2026, 02:38 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Feb 15, 2026, 07:00 PM UTC· resolved Feb 15, 2026, 10:21 PM UTC

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

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

2. monitoring Feb 15, 2026, 07:30 PM UTC

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

3. identified Feb 15, 2026, 08:19 PM UTC

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

4. monitoring Feb 15, 2026, 09:42 PM UTC

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

5. monitoring Feb 15, 2026, 09:58 PM UTC

   Services are operational, we are monitoring the failover. .

6. resolved Feb 15, 2026, 10:21 PM UTC

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

7. monitoring Feb 16, 2026, 02:00 AM UTC

   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..

Read the full incident report →

Started Feb 14, 2026, 12:30 AM UTC· resolved Feb 14, 2026, 03:46 AM UTC

1. monitoring Feb 14, 2026, 12:30 AM UTC

   We have identified the cause resulting in delayed EOD data today. It has been resolved and we are monitoring..

2. resolved Feb 14, 2026, 03:46 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Feb 10, 2026, 01:21 PM UTC· resolved Feb 10, 2026, 01:28 PM UTC

1. identified Feb 10, 2026, 01:21 PM UTC

   Potentally delayed data on Crypto Benchmarks - recommend using secondary site.

2. identified Feb 10, 2026, 01:22 PM UTC

   Issue identified with host node - recovering process. Recommendation switch to secondary site. .

3. resolved Feb 10, 2026, 01:28 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 13, 2026, 03:19 AM UTC· resolved Jan 13, 2026, 03:32 AM UTC

1. identified Jan 13, 2026, 03:19 AM UTC

   Identified the issue related to our host. Initiating a failover. Secondary sites remain functional. .

2. monitoring Jan 13, 2026, 03:28 AM UTC

   Failover complete. FX and Crypto operational. Benchmarks coming online in 5 minutes. Secondary sites continue to remain fully functional. .

3. resolved Jan 13, 2026, 03:32 AM UTC

   Services fully resolved on primary site. .

Read the full incident report →

Started Nov 02, 2025, 04:13 AM UTC· resolved Nov 02, 2025, 04:58 AM UTC

1. identified Nov 02, 2025, 04:13 AM UTC

   Binance data is inaccessible at present. Service is unaffected on our secondary site. If access is available, we recommend switching to the secondary site if Binance is desired. .

2. monitoring Nov 02, 2025, 04:37 AM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Nov 02, 2025, 04:58 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 13, 2025, 01:47 PM UTC· resolved Oct 13, 2025, 05:54 PM UTC

1. investigating Oct 13, 2025, 01:47 PM UTC

   We are currently investigating this incident..

2. identified Oct 13, 2025, 03:47 PM UTC

   Issue is upstream between IEX connectivity layer - waiting on upstream firms to fix. .

3. resolved Oct 13, 2025, 05:54 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jun 24, 2025, 02:06 PM UTC· resolved Jun 24, 2025, 02:22 PM UTC

1. identified Jun 24, 2025, 02:06 PM UTC

   We have identified the issue and are failing over .

2. resolved Jun 24, 2025, 02:22 PM UTC

   This incident has been resolved..

Read the full incident report →

Started May 20, 2025, 01:42 PM UTC· resolved May 21, 2025, 01:30 AM UTC

1. identified May 20, 2025, 01:42 PM UTC

   Right now there is a internet backbone issue that is largely affecting some residential ISP customers. This is because of congestion we're noticing at a Telia data center. If your connection routes to Telia (before routing to Equinix) you may notice delayed connections. We have alerted the proper channels to see if they can address this issue. Usually when internet backbone issue, there is little we can do, but often they last 1-2 days before getting resolved. Internet backbone issues are issues in the network between our servers and your machines - the issues we do not have direct control over. If connecting via major data centers (AWS, GCP, Equinix, Azure, OVH, etc.) you should not notice any slowdown and most customers should not be affected..

2. monitoring May 20, 2025, 05:56 PM UTC

   We've implemented a temporary workaround that should help improve speeds for a bit while internet backbone issue resolves itself. .

3. resolved May 21, 2025, 01:30 AM UTC

   Issue has been resolved .

Read the full incident report →

Started May 17, 2025, 07:14 AM UTC· resolved May 17, 2025, 07:45 AM UTC

1. investigating May 17, 2025, 07:14 AM UTC

   We are currently investigating this incident..

2. monitoring May 17, 2025, 07:41 AM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved May 17, 2025, 07:45 AM UTC

   Implemented a fix.

Read the full incident report →

Started Apr 05, 2025, 01:53 AM UTC· resolved Apr 06, 2025, 01:21 PM UTC

1. investigating Apr 05, 2025, 01:53 AM UTC

   We are currently investigating this incident..

2. identified Apr 05, 2025, 01:54 AM UTC

   Issue is identified with issues at at the Equinix level.

3. monitoring Apr 05, 2025, 02:01 AM UTC

   Still awaiting resolution from host. .

4. identified Apr 05, 2025, 02:18 AM UTC

   Equinix has confirmed their fiber connections is down for NY5/NY7.

5. investigating Apr 05, 2025, 03:30 AM UTC

   Update Received as of 03:25 UTC: Equinix's Network and Development team are actively investigating the issue. .

6. identified Apr 05, 2025, 05:54 AM UTC

   Recieved update as of 05:02 UTC: Equinix is working to establish alternative routing paths. .

7. identified Apr 05, 2025, 08:24 AM UTC

   Received update as of 08:22 UTC: Equinix has established alternative cross-connects, and working to bring the link active..

8. monitoring Apr 05, 2025, 09:30 AM UTC

   Equinix has resolved the incident. They have confirmed this was due to a fiber cut..

9. resolved Apr 06, 2025, 01:21 PM UTC

   Resolved due to internal checks and Equinix verification. .

Read the full incident report →

Started Mar 10, 2025, 03:51 PM UTC· resolved Mar 10, 2025, 05:09 PM UTC

1. investigating Mar 10, 2025, 03:51 PM UTC

   We are currently investigating this incident affecting IEX REST Data. WebSockets are performing as normal. .

2. identified Mar 10, 2025, 04:01 PM UTC

   We have identified the issue and are preparing for maintenance. We do not expect other services, other than IEX and EOD REST API to experience issues for maintenance. We will temporarily be bringing down EOD REST Data and IEX REST Data during the maintenance in the next several minutes. .

3. monitoring Mar 10, 2025, 04:12 PM UTC

   We are implementing a fix and running maintenance now. No other services other than IEX REST are presently affected. If you need IEX Data, please switch to WebSocket. .

4. resolved Mar 10, 2025, 05:09 PM UTC

   Emergency maintenance is complete, IEX REST is back up and running. .

Read the full incident report →

Started Mar 02, 2025, 02:40 PM UTC· resolved Mar 03, 2025, 02:03 AM UTC

1. investigating Mar 02, 2025, 02:40 PM UTC

   We are currently investigating this incident..

2. monitoring Mar 02, 2025, 02:50 PM UTC

   Services are recovering.

3. resolved Mar 03, 2025, 02:03 AM UTC

   Issue is resolved. Throughout this week we will be running maintenance to resolve this issue. No customer impact is expected during these maintenance windows..

Read the full incident report →

Started Jan 17, 2025, 06:49 PM UTC· resolved Jan 18, 2025, 12:59 AM UTC

1. investigating Jan 17, 2025, 06:49 PM UTC

   Our host (Equinix Metal) is experiencing issues. We are awaiting on their resolution..

2. identified Jan 17, 2025, 07:10 PM UTC

   Issue appears with our host, they are recovering. .

3. monitoring Jan 17, 2025, 07:19 PM UTC

   We are monitoring the host's fix .

4. resolved Jan 18, 2025, 12:59 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 13, 2025, 02:53 PM UTC· resolved Jan 13, 2025, 04:21 PM UTC

1. identified Jan 13, 2025, 02:53 PM UTC

   Issue is related to upstream cross-connect provider. They have been notified.

2. identified Jan 13, 2025, 03:21 PM UTC

   Issue is related to network connectivity at the exchange connectivity level. Investigation happening on-site at the data center..

3. resolved Jan 13, 2025, 04:21 PM UTC

   This incident has been resolved. There was an issue with the connectivity networking that has been fixed. .

Read the full incident report →

Started Dec 23, 2024, 04:24 PM UTC· resolved Dec 23, 2024, 04:24 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →