MetaTrader 5 feeds
Backup feeds, gateways, and switching in MetaTrader 5.
MT5 can receive from several feeds and select a source per symbol. Priority, quote timeout, gateway ownership, and depth recovery all affect continuity.
- Source selection is evaluated per symbol.
- Gateway ownership can override ordinary feed priority.
- Market Depth needs its own recovery check.
One list, many symbols
A priority change can affect every overlapping instrument, while individual symbols may switch at different times.
Watch activation
History-server status, counters, and journal records provide evidence of source changes.
Test the whole book
Bid/Ask may recover before a complete Market Depth snapshot is available.
On this page
MT5 can keep several feeds active and select among them for each symbol. Feed order establishes preference, while the history server’s data-feed timeout determines how long missing quotes are tolerated before another eligible source is used.
Per-symbol switching
Because selection is per symbol, one feed can remain active for EURUSD while another takes over XAUUSD. That limits the effect of a partial provider outage, but it also means a simple “feed connected” status does not describe the whole book.
Monitor source ownership for representative symbols, not only process health.
Gateway ownership comes first
If a gateway supplies quotes for the same symbol, it can take precedence over ordinary data feeds. Map gateway and feed coverage explicitly so a backup test does not produce an unexpected source.
For each instrument group, record:
- preferred feed or gateway;
- eligible backup sources;
- expected quote cadence;
- switch timeout;
- source to which the platform should return; and
- required evidence of the transition.
Connection timeout and switch timeout differ
Per-feed timeouts control connection recovery. The data-feed timeout controls when a silent source is no longer used for a symbol. A process can remain connected while one instrument stops updating, so connection status alone is insufficient.
Set the switch policy against normal session behavior. A quiet exchange or a scheduled break must not be treated as a failure.
Market Depth recovers differently
After a source change, top-of-book prices may appear before a complete book is rebuilt. Incremental depth updates are meaningful only when they follow a known snapshot.
For depth-enabled instruments, test:
- the last complete primary book;
- the first backup Bid/Ask update;
- the first complete backup snapshot;
- any period with stale or incomplete levels; and
- the same sequence on switch-back.
Reordering is a production change
Moving a feed changes preference for all overlapping symbols and can restart feed activity. Export the current configuration, use a quiet window, and verify both quotes and Market Depth after the change.
The platform cannot judge an active wrong source
Switching responds to missing eligible data. A source that continues sending a plausible but wrong price may stay active. Use upstream quote protection to compare sources and detect stale or abnormal inputs.
For complete resilience, combine platform selection with independent feed endpoints and rule agreement as described in redundant delivery .
A feed shaped around your setup
Rehearse the switch before you need it.
Tell us which sources back each other today. We’ll describe how a primary and backup feed can be disconnected and verified safely.