Metaquotes feed just blew up, demo accounts destroyed. - page 2

New comment
Julio Alonso Martinez #:
My question for a moderator now would be: "Will MetaTrader update its database to include the correct tick volumes for the period between October 27, 19:00, and October 28, 12:04? (time based on MetaQuotes Demo server)"

I (as a forum moderator) do not know. I only know that MetaQuotes Demo server is mostly used to update MT5 to beta build and to test beta builds for possible error on software in beta builds.
And the brokers should be used for any other cases (trading and testing). Because MetaQuotes is not a broker. 

---------------------

As I see here - the people are using MetaQuotes Demo server for trading and testing of the EA - which is very strange for me sorry.

Sergey, thank you. I understand the recommendation to use a broker demo for future testing, and that moderators may not know the repair policy. Could you please flag a reproducible server-accounting discrepancy from this incident to the MetaQuotes-Demo server administrator or development team, and confirm the correct private escalation route?

The remaining issue is affected account/deal history, even where current tick flow appears to have recovered. We observed a server stop-out with a booked loss incompatible with the reported normal fill-price movement and contract size. A private report with exact deal IDs and a reproducible currency-conversion calculation was sent to support@mql5.com today, followed by the small supporting journal/deal extract. I can provide it privately to the responsible technical team.

Is there an official mechanism to correct erroneous bookings and review consequential stop-outs while preserving the existing history? Can MetaQuotes confirm the status of affected stored tick history and conversion/valuation data?

This request is specifically for technical escalation and preservation/correction of the damaged MetaQuotes-Demo research record; no account identifiers, credentials or EA source are included here.

I don't have any issue with MetaQuotes-Demo.

LeviHuck #:
Sergey, thank you. I understand the recommendation to use a broker demo for future testing, and that moderators may not know the repair policy. Could you please flag a reproducible server-accounting discrepancy from this incident to the MetaQuotes-Demo server administrator or development team, and confirm the correct private escalation route?

As far as I know - this issue was fixed - 

Forum on trading, automated trading systems and testing trading strategies

Urgent: Critical Bug in MT5 Demo Server Caused Account Blowout

Alain Verleyen, 2026.10.28 15:44

...

As far as I can see, it has already been fixed.

-------------------

As to next investigation so I do not think the service desk will make a research about it in deep way - simple because this MetaQuotes-Demo server should not be used for trading and testing for example ...


Anyway, if someone from the service desk reads those threads (there are several threads on this English forum and several posts on Russian forum about this issue) so he/they may clarify some technical situation and so on.

LeviHuck #:
Sergey, thank you. I understand the recommendation to use a broker demo for future testing, and that moderators may not know the repair policy. Could you please flag a reproducible server-accounting discrepancy from this incident to the MetaQuotes-Demo server administrator or development team, and confirm the correct private escalation route?

The remaining issue is affected account/deal history, even where current tick flow appears to have recovered. We observed a server stop-out with a booked loss incompatible with the reported normal fill-price movement and contract size. A private report with exact deal IDs and a reproducible currency-conversion calculation was sent to support@mql5.com today, followed by the small supporting journal/deal extract. I can provide it privately to the responsible technical team.

Is there an official mechanism to correct erroneous bookings and review consequential stop-outs while preserving the existing history? Can MetaQuotes confirm the status of affected stored tick history and conversion/valuation data?

This request is specifically for technical escalation and preservation/correction of the damaged MetaQuotes-Demo research record; no account identifiers, credentials or EA source are included here.
Let me know if you have any success, I too have emailed them but I do not expect a reply. I guess my fault for using their demo feed for testing but my thought was well surely the company that designed the software should have one of the more reliable and accurate feeds...
Steven Donald Halcovitch #:
Let me know if you have any success, I too have emailed them but I do not expect a reply. I guess my fault for using their demo feed for testing but my thought was well surely the company that designed the software should have one of the more reliable and accurate feeds...

No one is at fault. You merely didn't know that the MQ demo feed is chaotic. I only use the latest Beta MT5 Build with the MQ demo feed to test basic functionality of new code that I develop, and to completely unleash the AI Assistant.

While I have no inside information regarding the specific cause of that chaos, I do know that shady "prop firms" have used bootleg instances of MT5 as their own free trading platform along with the demo feed. Just imagine the burden that must have placed on the free demo feed (servers). One sure fire way to put at end to that could certainly be... to blow up the feed, periodically at least.

Quick update: still no reply from support, not even an acknowledgement. I’m now on build 6292, but my account balance hasn’t changed. The erroneous loss and resulting forced closures remain unresolved.

I’ve got EA tests scheduled, so I’ll have to move the affected setups manually to broker demo accounts to continue testing before taking anything live. It’s a pain in the arse, frankly, after the time already spent.

I understand the point about using broker demos going forward, but restoring the feed hasn’t corrected my account. Has anyone had an actual response from support, or had their account corrected?
12
New comment