Execution Times and Alert Speed
Understand PineHook's MT5 and cTrader latency figures, what each timer includes, and how to diagnose slow TradingView alert execution.
Last updated: 2026-10-08
What the public figures measure#
The status page publishes a separate median for MT5 and for cTrader, each covering the previous seven full UTC days and updated at 00:00 UTC. Both measure PineHook's own alert handling, so they don't promise when TradingView sends a webhook or when your broker fills an order.
| Platform | Public median | Start | End and exclusions |
|---|---|---|---|
| MT5 | Delivery (D) | Webhook enters PineHook | Alert is queued for the MT5 Expert Advisor. This does not mean the EA received it or a trade executed. |
| cTrader | PineHook processing (D + E) | Webhook enters PineHook | D is relay time to the queue. E is local bridge processing on completed alerts. Measured broker reads and trading-call waits are excluded. |
Both figures leave out intentional delays and time spent waiting for an offline destination. The cTrader figure covers more of PineHook's processing than the MT5 one, so the two aren't directly comparable, and each is calculated from individual alerts rather than by adding medians together.
Read your Signal Logs#
Open Signal Logs and select the relevant license. Each alert can show these parts of its timeline:
- D (Delivery): PineHook's webhook processing until the alert reaches its delivery queue.
- E (Execution handling): MT5 EA or cTrader bridge handling, with measured broker time removed. For cTrader, measured broker API reads are also removed.
- T (Transport or external reads): For MT5, the network and terminal pickup portion when the EA reports enough timing data. For cTrader, measured broker API reads.
- B (Broker): Measured trading-call time. A broker response is not always the same as a final fill.
A missing value means the timing wasn't available, not that the stage took no time. Older MT5 EAs may not report B or T separately, in which case their E can include the confirmation round trip.
The public medians and your own alert's timeline answer different questions, since the MT5 median uses D and the cTrader median uses D + E. How long a trade takes to execute also depends on your broker, your network location, the order type and market conditions.
When an alert feels slow#
- Refresh Signal Logs, since the page doesn't update on its own when an alert completes.
- Find the alert and compare D, E, T and B. A large D points to PineHook's processing, a large E to the EA or cTrader handling, a large T to the network or broker reads, and a large B to the broker itself.
- Check for an intentional delay, an offline destination or a recovered alert, since none of these waits count toward the public medians.
- On MT5, make sure the computer running the EA syncs its clock automatically. The Experts tab may show the broker's timezone, so comparing it with the dashboard's UTC times can suggest a delay that isn't there.
- If the breakdown still looks wrong, contact support with the alert's ID and the license name, but never your broker password.
The status page shows overall medians and service health, while Signal Logs shows what happened to each of your alerts.