MetaTrader 4 feeds
Backup data feeds and switching in MetaTrader 4.
An MT4 backup feed is normally active and receiving data. List order, symbol coverage, and timeout policy determine when it can take over.
- Enabled feeds can run at the same time.
- List order establishes source priority.
- Reconnect behavior and source switching are separate.
Coverage comes first
A backup can take over only for symbols it supplies and is allowed to publish.
Silence is not bad data
Platform switching reacts to missing quotes; a wrong but active source needs upstream protection.
Test the return
A failover test should include switch-back, not only the move to the backup.
On this page
MT4 can keep several enabled feeds connected and use their order as a priority. For a symbol available from more than one eligible feed, the higher-priority source is preferred and a lower entry can act as backup.
Priority, coverage, and health are different
A feed’s position says which source should win. It does not prove that the feed:
- carries the symbol;
- passes the configured symbol mask;
- is licensed for the instrument;
- is publishing at the expected cadence; or
- is independent of the primary provider and network path.
Build a coverage matrix before relying on the list order.
Swipe or scroll horizontally to see all columns
| Symbol group | Primary | Backup | Normal cadence | Failure test |
|---|---|---|---|---|
| FX majors | Source A | Source B | Continuous in session | Stop A quotes |
| Metals | Source A | Source C | Includes daily break | Test after reopening |
| Crypto | Source D | Source E | 24/7 | Test weekend behavior |
Switching and reconnecting answer different questions
The feeder switch timeout governs how long missing quotes are tolerated before a lower-priority feed can be used. Per-feed inactivity and retry settings govern attempts to restore one connection.
Tune them together. A very short switch timeout may react to a normal market pause; a long timeout may leave a live symbol stale. The appropriate value depends on quote cadence and sessions, not only network latency.
When the preferred source returns, MT4 can return to it automatically. Include that transition in testing because an unstable source may recover briefly and fail again.
Reordering is a live change
Moving a feed changes policy for every overlapping symbol. It can also restart feed activity, so make the change in a controlled window and verify source ownership afterwards.
Avoid using priority changes as an incident-time experiment. Agree the order, switch conditions, and rollback before production.
Two feeds can share one failure
Redundancy is weak when primary and backup share:
- the same upstream provider;
- the same credentials or entitlement;
- the same feed module and defect;
- the same server or network route; or
- the same incorrect symbol mapping.
Platform-level backup feeds protect one part of the path. Redundant delivery also considers separate pricing instances, endpoints, and rule agreement.
Run a complete failover test
- Confirm both feeds are connected and current.
- Compare several shared symbols before the test.
- Stop only the primary quote flow in a controlled way.
- Measure the last primary tick, first backup tick, and any gap.
- Check unaffected symbols and client-visible prices.
- Restore the primary and observe switch-back.
- Save journal and tick evidence with the active configuration.
MT4 switching is primarily a response to absent quotes. A source that continues publishing a plausible but wrong price may remain preferred. Cross-source validation belongs in an upstream quote-protection layer .
A feed shaped around your setup
Test the failure case, not just the happy path.
Tell us how your MT4 feed should behave when a source goes quiet. We’ll describe how primary and backup delivery can be verified together.