Problem Exness.com - issues with gold price around NFP release

[Naseebkhan1996]

I am writing this review to warn traders about severe internal server execution delays on Exness during high-impact news events.

On September 4, 2026, at exactly 16:30:01 server time (during the Non-Farm Payrolls release), I had two open buy positions on XAU/USD. Both positions shared an identical Stop Loss price of 4468.352 to protect my account balance of $1,012.

The market experienced a gap, which I understand happens during NFP. However, Exness's internal routing queue failed catastrophically, creating an artificial, predatory execution delay between my two simultaneous orders within the exact same second:

1. Order #1377081323 (0.10 Lots) - Closed at 4441.650
2. Order #1377079129 (0.30 Lots) - Closed at 4433.944

There was a massive $7.70 USD per ounce price difference between my own identical trades executed at the exact same moment (16:30:01). This proves that Exness's internal server processing queue suffered massive lag, severely delaying the execution of my second order and completely wiping my $1,012 balance to zero.

I raised a formal dispute with Exness, and they rejected it with a generic, automated copy-paste response citing their market gap policy, completely ignoring their internal processing delay.

I have officially escalated this case to the Financial Commission for an independent technical audit of Exness’s execution logs. I advise all traders to be highly cautious about trusting Exness's infrastructure with their risk management during news events.

 

[FxMaster]

I am writing this review to warn traders about severe internal server execution delays on Exness during high-impact news events.

On September 4, 2026, at exactly 16:30:01 server time (during the Non-Farm Payrolls release), I had two open buy positions on XAU/USD. Both positions shared an identical Stop Loss price of 4468.352 to protect my account balance of $1,012.

The market experienced a gap, which I understand happens during NFP. However, Exness's internal routing queue failed catastrophically, creating an artificial, predatory execution delay between my two simultaneous orders within the exact same second:

1. Order #1377081323 (0.10 Lots) - Closed at 4441.650
2. Order #1377079129 (0.30 Lots) - Closed at 4433.944

There was a massive $7.70 USD per ounce price difference between my own identical trades executed at the exact same moment (16:30:01). This proves that Exness's internal server processing queue suffered massive lag, severely delaying the execution of my second order and completely wiping my $1,012 balance to zero.

I raised a formal dispute with Exness, and they rejected it with a generic, automated copy-paste response citing their market gap policy, completely ignoring their internal processing delay.

I have officially escalated this case to the Financial Commission for an independent technical audit of Exness’s execution logs. I advise all traders to be highly cautious about trusting Exness's infrastructure with their risk management during news events.

@ExnessOfficial, could you please look at this?

 

[Naseebkhan1996]

I am writing this review to warn traders about severe internal server execution delays on Exness during high-impact news events.

On September 4, 2026, at exactly 16:30:01 server time (during the Non-Farm Payrolls release), I had two open buy positions on XAU/USD. Both positions shared an identical Stop Loss price of 4468.352 to protect my account balance of $1,012.

The market experienced a gap, which I understand happens during NFP. However, Exness's internal routing queue failed catastrophically, creating an artificial, predatory execution delay between my two simultaneous orders within the exact same second:

1. Order #1377081323 (0.10 Lots) - Closed at 4441.650
2. Order #1377079129 (0.30 Lots) - Closed at 4433.944

There was a massive $7.70 USD per ounce price difference between my own identical trades executed at the exact same moment (16:30:01). This proves that Exness's internal server processing queue suffered massive lag, severely delaying the execution of my second order and completely wiping my $1,012 balance to zero.

I raised a formal dispute with Exness, and they rejected it with a generic, automated copy-paste response citing their market gap policy, completely ignoring their internal processing delay.

I have officially escalated this case to the Financial Commission for an independent technical audit of Exness’s execution logs. I advise all traders to be highly cautious about trusting Exness's infrastructure with their risk management during news events.

UPDATE: Exness has replied to my internal dispute with their raw tick logs, and it completely confirms internal server queue latency!

According to the official logs they sent me, both of my positions triggered at the exact same moment at 4463.646. However, Exness explicitly admitted in writing: "due to a considerable number of activated pending orders inside the activation queue, its execution would only be possible after several ticks."

Because of this internal server bottleneck, they filled my first order at 4441.65, let multiple market ticks pass, and finally filled my second trade at 4433.944. This $7.70 price discrepancy occurred entirely inside their own processing queue within the same second, completely washing my $1,012 balance to zero.

I have forwarded this black-and-white admission of platform performance failure directly to the Financial Commission for Case #17866. @ExnessOfficial, your own technical team has confirmed the lag.

 

[ExnessOfficial]

Hello Naseebkhan199,

As the matter is now under review through the Financial Commission, we will not be able to continue further communication on this matter.

Any further updates will be handled through the official regulatory channel.

Thank you.

 

[Naseebkhan1996]

Hello Naseebkhan199,

As the matter is now under review through the Financial Commission, we will not be able to continue further communication on this matter.

Any further updates will be handled through the official regulatory channel.

Thank you.

Thank you for the acknowledgment, @ExnessOfficial I accept that further technical details will now be mediated officially through the Financial Commission (Complaint #17866). I have already provided the Dispute Resolution Committee with the full email correspondence from your Technical Specialist, explicitly highlighting the internal server activation queue bottlenecks that caused the $7.70 price execution variance between my identical simultaneous trades.I will leave this thread open and will post the Financial Commission’s final official verdict here for transparency so the entire trading community can see the outcome.