How to Measure TradingView Latency in TradersPost

‍Can You Determine TradingView’s Latency?

Yes, traders can estimate TradingView’s latency when sending signals to TradersPost by using the “time now” parameter in the JSON message.

▶

This parameter records when the alert was triggered in TradingView, allowing traders to compare it with the time the alert was received by TradersPost. The difference between these two timestamps provides a rough estimate of the latency. This difference covers only the trip from TradingView to TradersPost. It will not reveal delayed chart data, which TradingView lists as 10 to 20 minutes behind for many exchanges unless you have real-time data¹.

Key Latency Insights

• Typical Delay: Most signals take about one second to travel from TradingView to TradersPost.

• No Sub-Second Precision: TradingView gives the “time now” value only to the nearest second, so latency measurements may not be exact².

• Rare Delays: While most alerts are near-instant, occasional delays of up to 30 seconds have been reported due to TradingView’s internal queuing process.

How TradingView Processes Alerts

1. An alert is triggered based on the algorithm’s conditions.

2. The alert is queued in TradingView before being sent via webhook.

3. TradersPost receives and processes the signal.

Since alerts are queued before sending, latency can vary slightly depending on TradingView’s server load at that moment.

Conclusion

Traders can use the “time now” parameter to measure TradingView’s latency when sending alerts to TradersPost. While most signals arrive within one second, occasional delays can occur due to TradingView’s queuing system.

References

¹ tradingview.com, Market Data
² tradingview.com, How to use a variable value in alert