MT5 Execution Latency Analysis: 2800ms Delay Between "market buy" and "accepted" - VPS vs Broker Issue?
"Access server NY1" is the access from your MT5 to the broker's server. It is not order executed/processing time.
As to the logs ... it is the logs of your MQL5 VPS or it is the log of your home Metatrader?
In anyway. as I see - it is the executed/processing time which is related to the broker itself sorry.
You can try to monitor from the other days but monitor the MQL5 VPS logs only.
-------------------
Monitor VPS (summary post): #1
- 2017.03.31
- www.mql5.com
"Access server NY1" is the access from your MT5 to the broker's server. It is not order executed/processing time.
As to the logs ... it is the logs of your MQL5 VPS or it is the log of your home Metatrader?
In anyway. as I see - it is the executed/processing time which is related to the broker itself sorry.
You can try to monitor from the other days but monitor the MQL5 VPS logs only.
-------------------
Monitor VPS (summary post): #1
Thank you very much for your response and technical clarification!
To clarify, this log is from a 3rd-party Forex VPS (co-located in the same data center region), rather than the built-in MQL5 VPS service.
My VPS network latency (ping) to the broker’s access server is consistently maintained at <1ms. However, the processing time between market buy and accepted market buy fluctuates wildly across different days—ranging from tens of milliseconds, to a few hundred ms, 1000ms, and spiking up to 2800ms as shown in the screenshot.
Could you please re-confirm: since the network ping is solid at <1ms, does a delay between market buy (sent from terminal) and accepted (acknowledged by broker) mean the latency bottleneck is strictly and entirely on the broker's server/bridge side, even when using a 3rd-party VPS?
I want to be 100% certain before presenting this log trace to IC Markets support. Thanks again for your expertise!
Could you please re-confirm: since the network ping is solid at <1ms, does a delay between market buy (sent from terminal) and accepted (acknowledged by broker) mean the latency bottleneck is strictly and entirely on the broker's server/bridge side, even when using a 3rd-party VPS?
<1ms is the time for your MT5 to reach the broker's server, and it is not a order/trade processing time.
-----------------
In case of order/trade processing time ... how many trades do you have for 1ms? ok ... for 1 seconds ... one million trades for 1 second every second? Not? So, you are not making high-frequency trades (HFT).
And in this case - you should not case much about order/trade processing time at all.
Of course, 2800m is a little big order/trade processing time so I am suggesting you to monitor the situation - just in case it was some "ping on Friday during the high impacted news events" or something to be similar.
There is an execution delay of 2800ms, and both my VPS provider and IC Markets are deflecting responsibility.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi MQL5 Community / Admins,
I am troubleshooting a severe execution latency issue on MT5 (IC Markets) running on a Forex VPS located in the same data center region. There is an execution delay of 2800ms, and both my VPS provider and IC Markets are deflecting responsibility.
Here is the exact log sequence from the MT5 Terminal:
As seen in the logs, the time gap between market buy and accepted market buy takes 2800ms.
I would appreciate your technical guidance on the following points:
Timestamp Definitions: Does market buy represent the exact millisecond the request left the local MT5 Terminal socket on the VPS, or just when the EA called OrderSend() ?
Broker Server Handling: Does the accepted log entry get generated the moment IC Markets' Trade Server receives the packet, or after it passes internal risk/margin checks and bridge routing?
Isolating Responsibility: If my MT5 Journal logs show a stable ping of <2ms to the IC Markets trade server during this period, does a 2800ms gap between market buy and accepted conclusively prove that the delay occurred inside the broker's trade server/bridge infrastructure, rather than a VPS network latency issue?
Any insights into how to officially present this log analysis to broker support/compliance would be greatly appreciated. Thanks!