> For the complete documentation index, see [llms.txt](https://help.topstepx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.topstepx.com/settings/charts-and-data/data-update-speed.md).

# Data Update Speed

TopstepX provides 3 data refresh speeds for you to choose from:

* Slow (750ms)
* Medium (default - 250ms) 
* Fast (50ms).

We pipe exchange data updates at very fast refresh intervals directly into the TradingView charting library, via your web browser. This may cause issues with outdated or slow browsers, which can struggle to keep up with these updates. 

If you experience any kind of delay or data lag on your charts, please reduce your data refresh speed & consider reducing the amount of indicators / drawings shown.

Please note: chart refresh lag does *not* effect trading and orders, as all trading and order execution occurs in our server side order engine. Traders are advised to monitor their [Positions tab](/components/positions.md) at all times.

<figure><img src="/files/Cf1nP1p0JwQDgez8Or6I" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.topstepx.com/settings/charts-and-data/data-update-speed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.