Why is my TradingView delayed?

Separate the data feed from the screen and the order

Use the first observation that differs from your expectation to choose a branch. A different price alone does not measure delay: the two displays may use different sources or quote types.

Follow the symbol and subscription decision tree

Begin with Symbol search and record the listing exchange. Open the chart market-status menu; TradingView identifies the relevant subscription there. Keep a screenshot of the status and observation time before making changes.

• If the status reports a delay, use Learn more to inspect the required package. Check active data subscriptions under Settings and billing, Subscriptions, Real-time market data.
• If you already buy data through a broker, check TradingView's supported broker/exchange verification list. Eligible subscriptions can be verified through the Trading Panel; support and renewal requirements depend on that pairing.
• If the status is real-time but another chart differs, check its provider. TradingView's default US stock feed comes from Cboe and can differ from primary-exchange data, especially in less active periods.
• If the source matches, check that the market session is open and that new trades are occurring. An unchanged last-trade price alone does not establish a broken connection.
• If updates still look slow, record several observations, then compare the same symbol in a fresh chart session. This is a diagnostic comparison, not a way to remove exchange restrictions.

Treat chart updates and broker quotes as separate checks

TradingView documents that its free plan updates data every few seconds, while paid plans update faster when trades occur. That screen-update distinction does not establish a fixed delay for every instrument or connection. Cboe data can also have fewer price updates than primary-exchange data because the underlying trading activity differs.

• For an eligible broker subscription, check when verification expires and reconnect through the Trading Panel as required. Do not assume every broker or exchange participates.
• The Order Panel and buy/sell buttons use broker quotes. For example, TradingView documents that its own data packages do not remove delayed Interactive Brokers bid/ask quotes; broker-side access is required.
• For a late execution, preserve the broker order ID, submission, acknowledgement, and fill records. The difference between a chart price and a fill price alone cannot identify execution latency.
• If multiple instruments stop updating unexpectedly, retain the timestamps and reproduction steps for support. Include the selected source and session so support can distinguish stale delivery from a quiet market.

Worked example: compare the right clocks

These invented timestamps illustrate the arithmetic; they are not measured TradingView performance. Assume all clocks are synchronized in UTC and that the quote record includes an event timestamp for the exact same feed and event. Without that timestamp, the first calculation cannot be made from a candle label alone.

• 14:45:04 minus 14:30:00 = 904 seconds. This is quote age at observation; it does not separately measure exchange delay, network transit, or time spent waiting before you looked.
• 14:45:08 minus 14:45:05 = 3 seconds. That interval concerns notification arrival and cannot explain the earlier quote age.
• If 14:30 were only the opening label of a 15-minute candle, the 904-second subtraction would not measure quote age. Price can update throughout that candle.
• Record clock uncertainty and the observation method. A screenshot taken after an update provides a different measurement from an instrumented arrival log.

Use timestamps according to what they represent

Pine time identifies the bar opening, and time_close identifies its closing time. timenow refers to script execution time and updates when the script executes. None of these is a universal exchange-event receipt timestamp. Subtracting a bar opening from the current clock mixes bar age with any data delay.

• Use one time zone in the diagnostic record. Preserve the original timestamp and its meaning rather than comparing differently formatted local clocks.
• A fresh execution timestamp does not certify the age of every price used by the script. Verify feed access and requested data contexts separately.
• For an alert that waits for bar close, separate the intended confirmation rule from delivery time. Inspect the alert log before changing notification settings.
• Running script alerts retain their creation-time script and settings. Recreate an alert after changing the relevant script or inputs, then use the dedicated alert-delay guide for delivery diagnosis.

Give a coding agent a timing requirement it can review

After resolving the data-source question, use Pineify's Pine Script AI Coding Agent to review editable signal code. A useful request names the symbol, timeframe, requested data, confirmation rule, and meaning of each displayed timestamp. Keep the chart subscription check outside the script.

• Example review brief: Explain which signals use a closed bar, identify every requested symbol and timeframe, and label bar time separately from execution time. Treat data freshness as unverified until the feed has been checked.
• Inspect the returned code and test its behavior on the intended chart. A script can document assumptions about its inputs; it cannot grant real-time exchange access.