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.

We're done with this maintenance. Thanks for your patience!

We have moved the maintenance to Sat 01st Mar, 0am to 6am EST. So it will start 8 hours earlier than previously planned.

On Sat 01st Mar, from 8am to 2pm EST we'll be performing maintenance which is going to improve the system performance and stability. We do not expect any downtime during this maintenance, but there can be a brief period of time (up to 5 minutes) when the Alerts will not be visible in the user interface. However, Alerts will keep on working and firing during this period, as usual.

We have established a plan for gradually resolving this problem over the course of 5-6 days. Today we've applied the first batch of changes. Every day scanners will be becoming slightly faster. We're closing the incident and we'll keep on working on that.

We are still investigating what we could do in the short term in order to resolve the problem.

Significantly elevated demand for intraday scanning on US Equities (time frames below 5min) has caused the entire infrastructure of scanning to become slow. We're currently assessing our options for mitigating that.

This is a record about the past event. While we believe that have notified everyone upfront, there's a small chance that we have missed a few customers while doing so. On Tuesday 11th Jan, around 8pm EST, we have released an update to how the Strategy Tester works with Raindrop and Heikin Ashi chart types. Here's what has changed.

Prior to this change, the Strategy Tester used specific Heikin Ashi and Raindrop data points (like Open/Left etc) for both (a) evaluating your criteria to make trading decisions and (b) deriving theoretical execution prices. However, deriving execution prices from Heikin Ashi or Raindrop charts often results in unrealistic numbers. For example, Open of a Heiken Ashi candle is defined as the midpoint between the previous candle's Open and Close. This is rarely equal to the actual current market price when the corresponding candle has opened.

After this release, strategies based on Raindrop and Heikin Ashi charts keep on making trading decisions basing on the corresponding charts, but they derive execution prices from the underlying raw OHLC data instead. Here's an example of how things will change for a strategy based on Heikin Ashi, with the entry condition like 'enter whenever Close > Open':

Before: Strategy Tester checks the current HA candle, which is HA.Open=228.8, HA.Close=229.6. HA.Close is above HA.Open, so it's time to enter. Entry price would be equal to HA.Open, which is 228.8.

After: Strategy Tester checks the current HA candle, which is HA.Open=228.8, HA.Close=229.6. HA.Close is above HA.Open, so it's time to enter. The underlying Japanese candle for the same time period is Candle.Open=229.9, Candle.Close=229.1. The trade decision remains as HA.Close>HA.Open, but the entry price would be equal to Candle.Open = 229.9, and not HA.Open as before.

This change has changed the results of backtests on Raindrop and Heikin Ashi. If you were running Trading Bots based on these strategies, they were automatically stopped by the system. Please reach out if you have any questions or need further clarification.

This issue has been resolved.

We have identified an issue causing entry and exit signals not to appear on charts for both Trading Bots and the Strategy Tester. This issue is purely visual and does not affect the performance of either tool.

We'll be implementing "maximum pending scans per customer" limitation soon, in order to avoid disruptions like that in the future. Thanks for your patience.

We have stabilized scanning and it's now back to normal. We're monitoring the situation closely.

Market scanners are currently slower. We're working to resolve that asap.

We have restored 4 decimals for the US stocks and ETFs. To be clear, this change is primarily related to how data is being transported. On your charts, you're still seeing 2 decimals, but 4 decimals are used when calculating indicators — just the way it used to be. Thanks for your patience.

Because of a human error, price data precision for US stock/ETF data is currently limited to 2 decimal places. We're working on getting back to 4 decimal places asap. This price data precision loss led to some of the trading bots failing because of sanity check errors.

We have rolled up a patch which addresses the issue for the vast majority of tickers. We're now working with our data provider to resolve the incident on their end. Thanks for your patience.

We've identified the root cause for some of the Index futures having a portion of historical candles missing. We're working on a fix.

We have identified and fixed the root cause of this issue. Please refresh the web page with platform in order to have the patch applied during the market hours. Otherwise, it will be automatically applied after hours. Thanks for your patience.

In some cases certain indicators don't display MTFA values properly. We're investigating.

We have implemented a patch for that. We're working with our data provider to find out what was the root cause of that. Thanks for your patience.

Some Energy futures have historical data partially missing. We're investigating.

This is now finished, thanks for your patience.

On Friday 27th Sept, we'll be running maintenance for our market data connections. We'll start after market closes. No downtime is expected.

We've fixed the root cause of the problem. It's not the "last price" what was wrong, it was the history. Because of a technical issue on our end, for some spreads we've been displaying history belonging to other spreads. I.e., for RB V24-X24 we were displaying history of RB V24-X24-Z24. We're currently implementing additional checks to ensure that it never happens again.

We're currently observing some CME exchange traded spreads receiving real time ticks with wrong prices. We're working to fix that.

We have enabled the News data again. While we're closing the incident, we'll keep on monitoring the system. Thanks for your patience.

We are still working on restoring access to the News data.

We've had to temporarily disable the News data again. We're investigating further.

We have restored access to all the feeds. We're monitoring the system.

We're restoring feeds one by one and monitoring the system.