Metaquotes feed just blew up, demo accounts destroyed.

What in the hell happened here? Clearly a glitch on Metaquotes end... Can this be reversed? Now my journal across all my Metaquotes terminals are being spammed with these old ticks every 1ms filling my journal logs up massively every second.

This was a Metaquotes demo account.



Just confirming that you're not alone.  Did the same thing for me today. AUDJPY trade went crazy on me, LOL - now it's old ticks as far as the eye can see.  Hard testing in these conditions. Looks like ver 6290
if you searched this site then you would find that the mq server is notoreously unreliable. do not use it for trading or data analysis. it is for testing of the mt5 program only, not for trading.

Same problem here, still active on 2026.10.28. Some details that may help MetaQuotes find it:


- Start: 2026.10.27 about 19:00 server time. All MetaQuotes-Demo symbols I checked are affected (XAUUSD, EURUSD, AUDNZD, AUDCHF, AUDJPY, GBPUSD).

- Seen on builds 6230, 6285, 6286 and 6290, on access points IN 1, IN 2, HK 1 and EU 2, with 3 different demo accounts, and on the mobile app. Same result through a VPN, so it is not a local network problem. Another broker's server gives normal ticks on the same PC at the same time.

- Thousands of journal errors per hour (128,070 lines on one terminal today). The tick time is 1970.01.01 and the prices are invalid:

  old tick XAUUSD (tick: 1970.01.01 00:17:04.000, last: 2026.10.27 20:31:48.731) 17931331.13/1.94

  old tick AUDNZD (tick: 1970.01.01 00:00:00.000, last: 2026.10.27 20:29:30.030) 17931.33000/0.00000

- Valid ticks now arrive only in short bursts at about second :00 or :30 of each minute, so charts update about once per minute.

- XAUUSD ticks per hour (CopyTicks): 2026.10.27 15:00 = 45,262, 16:00 = 46,330, 18:00 = 27,136, 19:00 = 1,508, 20:00 = 681, 2026.10.28 03:00 = 370.

  EURUSD: about 12,700/hour -> about 150-240/hour.

- The tick history downloaded from the server for hours when my terminal was offline has the same sparse pattern, so the stored server history is affected too.


Please check the MetaQuotes-Demo tick feed. Journal excerpt attached.

easerver1 #:



Forum on trading, automated trading systems and testing trading strategies

Metaquotes feed just blew up, demo accounts destroyed.

Michael Charles Schefe, 2026.10.28 02:52

if you searched this site then you would find that the mq server is notoreously unreliable. do not use it for trading or data analysis. it is for testing of the mt5 program only, not for trading.

Forum on trading, automated trading systems and testing trading strategies

i cannot find ustechx100 on my mt5

Sergey Golubev, 2021.11.22 06:02

The charts, the price on the charts, the symbols to trade, and the names of the symbols, and the time of the price on the chart - all of them are related to the brokers only.
So, if you want to trade some symbol so you should find the broker which is allowing this symbol for traders (because it is nothing to do with Metatrader platform application at all).

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

Forum on trading, automated trading systems and testing trading strategies

Need help

Sergey Golubev, 2021.07.19 18:17

Find Metatrader broker (there are a lot of Metatrader brokers, use google to find), and open the account according to their condition on their websites.
Try with demo first.

1. The article - MQL5.community - User Memo 

2. MetaTrader 5 Help - Open an Account

3. Where Do I start from?
https://www.mql5.com/en/forum/212020 

4. Broker selection - the thread with some advices

5. MetaTrader 5 Help - Trading Platform — User Manual 

6. How to make a search on the forum
https://www.mql5.com/en/forum/193510 

7. Find a Server by the Broker's Name: 
https://www.mql5.com/en/forum/214820




I am experiencing the same issue on October 28, 2026. My MetaQuotes-Demo account has frozen or delayed quotes on MT5 desktop (Ubuntu 24.04, Wine 11.20 Staging, build 6290), mobile, and the web terminal. The Journal repeatedly reports old tick and old last price warnings with timestamps from 1970/1971 and invalid zero-valued quotes. My Ubuntu system clock is synchronized. Can anyone confirm whether the MetaQuotes-Demo feed has been fixed?

Deepanshu Sondagar #:

I am experiencing the same issue on October 28, 2026. My MetaQuotes-Demo account has frozen or delayed quotes on MT5 desktop (Ubuntu 24.04, Wine 11.20 Staging, build 6290), mobile, and the web terminal. The Journal repeatedly reports old tick and old last price warnings with timestamps from 1970/1971 and invalid zero-valued quotes. My Ubuntu system clock is synchronized. Can anyone confirm whether the MetaQuotes-Demo feed has been fixed?

This MetaQuotes-Demo account is mostly used to update to beta build and to test beta builds. And the accounts with the brokers (MetaQuotes is not a broker) should be used in any other cases.
read post 
Metaquotes feed just blew up, demo accounts destroyed.
Metaquotes feed just blew up, demo accounts destroyed.
  • 2026.10.27
  • www.mql5.com
What in the hell happened here? Clearly a glitch on Metaquotes end... Can this be reversed...
Sergey Golubev #:
This MetaQuotes-Demo account is mostly used to update to beta build and to test beta builds. And the accounts with the brokers (MetaQuotes is not a broker) should be used in any other cases.
read post 
So i use different broker for demo account ..
At this time, October 28, 2026, 10:40 AM, the issue is still ongoing.
The issue was resolved today at 12:04; the tick volume has returned to normal.
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)"