This incident is now resolved. Thanks for your patience! We'll continue to analyze the root cause and find out the way to avoid things like that in the future.

We have identified the root cause of the problem, and we're working with Nasdaq to get that fixed asap.

We are continuing working on that problem. There is no resolution yet.

We are continuing working on that problem. There are no updates yet.

Intraday data is missing for stocks and ETFs for the day of 13th Jan. We are working our market data provider to get that resolved asap.

We have not observed any anomalies since 15:01 EST today. We're marking the incident resolved. Internally, we'll proceed with the after-math, in order to avoid problems like that in the future.

We have identified and fixed the root cause of the problem. If you face a problem like that, then please refresh the web page, which should apply our fix for you.

We have identified a problem which causes custom indicators execution failure sporadically. It's not related to any specific scripts. It can lead to some alerts and bots being stopped by the system. We are currently working on resolving this problem.

We have not observed any anomalies ever since switching the entire system to a new set of servers. We have identified the root cause of the problem we've faced, and we're now working on a strategic resolution.

We have switched the entire system to a completely new set of servers. The system is stable now. We're monitoring it closely.
If you are still experiencing any instability, then you are likely to still be connected to the old servers. Please refresh the web page; doing so switches you to a new set of servers.

We continue working on stabilizing the platform.  All the services are operational, but certain services (like scanners and some charts) are still slower than normal.

We have seen reports of customers sporadically being unable to see their strategies, over the course of the incident. Rest assured that the content is not impacted. The reason for behavior like that is that browsers failed to fetch a list of strategies from our servers (because of sporadic problems with these servers).

We have managed to restore most of the platform's functionality. However, some features can still have degraded performance. We continue working on stabilizing the platform.

TrendSpider platform is not available for a number of customers. We're working to restore the functionality asap.

The incident was resolved, all systems are operational now

All the CME Group markets are halted due to a data center cooling issue. Please notice that it's not a problem of TrendSpider having no real time updates; it's the exchange per se stopped trading because of a major incident. Please refer to https://www.cmegroup.com/tools-information/cme-global-command-center-system-alerts.html to learn more. At the moment, we do not know when they will resume normal market operations.

This maintenance is now complete. Thanks for your patience.

On Saturday 22th Nov 18:00 to 22:00 EST, we'll be upgrading components of our core infrastructure. During that period of time, there might be brief interruptions in various TrendSpider services.

The incident had been resolved. We keep on working with Reamaze in order to ensure things like that never happen again.

Our support system provider, Reamaze, is having an incident. Submitting messages to the Customer Success team from within the platform is temporarily not available.

The incident had been resolved. We keep on working with Reamaze in order to ensure things like that never happen again.

Our support system provider, Reamaze, is having an incident. Submitting messages to the Customer Success team from within the platform is temporarily not available.

Systems are stable and working fine

We are aware of an issue with our Relative Performance feature, and this may affect scans, as well as other features that use this indicator. Our team is actively working to restore functionality.

The issue causing Congress Trades data to not work has been fully resolved. All systems are now operating normally.

We are investigating an issue where Congress Trades data is not working. Our team is actively working to restore functionality.

We've closing the incident, as it's evident that the root cause had been addressed, and the service was back to normal ever since.

We have identified the bottleneck and we believe that we have resolved the problem. We're now monitoring the system to ensure that it's stable.

We are currently investigating an issue that is causing all features based on custom JS to be very slow or non-operational. We are working to address as quickly as possible and appreciate your patience.

The problem is fixed

Right now we're having issues on calculating custom indicators on charts. 
It does not affect alerts, bots or any other system

We have identified the problem and working on a fix

The system is back to normal. We will keep on working on the aftermath with the data provider. We need to find out how to prevent cases like that in the future. We appreciate your patience.

We have restored all the functionality and we're now monitoring the system as it's getting back to normal. We're also working on the aftermath with the data provider.

We are now partially operational but services remain slower than usual.  Scanning remains disabled for now.

We are still working with the data provider to resolve the problem.

Our core data provider has an ongoing incident. Market data availability is impacted. Some charts and backtests won't load. We are working with the data provider to get that resolved asap.

We have resolved the issue that was causing Congress Trades to not appear within What's Happening Now.  Everything should be back to normal.  Please report any further issues to our support team.

We are investigating an issue that is causing Congress Trades data to not appear within What's Happening Now.   For now, you can visit: https://trendspider.com/markets/congress-trading/ to get information about Congress Trades.

The problem has reoccurred between 3pm and 4pm EST again. We've got a fix for the root cause which we will release in the next 3 hours.

We have identified the root cause and applied a patch. We'll now be working on preventing the same problem from occurring again in the future. Thanks for your patience!

Custom indicators runtime backend is slow. Some scans, backtests, bots and alerts using Custom indicators are not operational. We're investigating.

We have finished the maintenance, thanks for your patience.

On May 8th, from 6pm EST to 9pm EST, we'll be performing maintenance for the infrastructure related to market scanners. During this period, market scanners might be slower than normal. There might be 5-7 minutes of downtime for scanners during the maintenance.

Today, on 5th May 2025, alerts have missed checks in periods of time from 05:13 am NY to 05:56 am NY, and from 06:15 am NY to 07:01 am NY. That happened because of certain servers of ours have had hardware degradation, which we have not noticed in a timely manner. No other services were impacted (i.e., trading bots have not suffered). We have implemented more of monitoring checks, in order to detect cases like that faster in the future.

We're closing the incident, while we'll proceed with the data cleanup. We're sorry for trouble. We're also working with our data provider to find out where these weird ticks have originated from.

We have resolved the root cause of the problem. We are now gradually correcting data, weeding out bad ticks. This procedure will be completed in 28 minutes.

We have found out that some ETFs (like SPY) have wrong wicks. Namely, wrong High values which are obviously abnormal. We're working to fix that asap.

The problem had been resolved on Saturday, thanks for your patience! We'll continue to work on the after math, but we're closing the incident.

Things are back to normal. We are monitoring the system closely. We'll work on the after-math as well, to make sure it never happens again.

We are still working with our data provider to resolve the problem.

This is still the problem and we're working on resolving it. We're seeing that time frames of Daily and above are not operational for Cboe indexes and OTC Stock data as well.

Our data vendor is experiencing an incident, which leads to some time frames not working. Namely, Quarterly and above are impacted for US stocks/ETFs, and Daily and above are impacted for CME futures. We're working with the data provider to get that resolved asap.