FTMO Server Down? Match the Platform and Clock to the Published Notice
An “FTMO server down” search needs a platform, a timestamp and an observation. FTMO publishes dated trading updates for CFDs and Futures, and their maintenance notices can use different clocks. This guide reads selected 22 October 2026 notices as worked examples; it is not a live uptime monitor or a claim that a service is down now.
Continue with this site's separate research worksheet
Start with the product-specific notice
The CFD notice dated 22 October scheduled maintenance for MT4, MT5, TradingView and cTrader on 24 October, 08:00-12:00 in the stated MetaTrader GMT+3 clock. The selected Futures notice instead scheduled NinjaTrader and Tradovate maintenance on 23 October, 18:00-20:00 ET, also affecting TradingView.
These are published schedules, not incidents independently observed by this guide. TradingView appearing in both notices does not make the CFD and Futures environments or their timestamps interchangeable.
Normalize a clock before matching an event
For the dated CFD example, 08:00-12:00 at GMT+3 corresponds to 05:00-09:00 UTC. Keep the original timezone beside the converted window so the calculation remains inspectable.
Imagine an invented observation at 06:00 UTC on 24 October. It falls inside that announced CFD window, which makes scheduled maintenance a relevant explanation to check. A different invented observation at 10:00 UTC falls outside that window. Neither comparison establishes the actual cause of a connection problem.
| Field | What to retain | Interpretation boundary |
|---|---|---|
| Product and application | CFD or Futures; exact platform | A shared app name is not the same environment |
| Clock | Date, original timezone and optional UTC conversion | Do not compare clock labels alone |
| Visible symptom | Redacted message and action attempted | A symptom is not a proven cause |
| Recovery | A separately observed successful action | A scheduled end is not observed recovery |
Describe the symptom instead of naming a cause
A website that will not load, a terminal login failure, an order rejection and a market without fresh quotes are different symptoms. Record the exact application, market, observation time and visible message before treating them as one server-wide event.
Do not put a password, access token or private account document into a public status comparison. A useful private incident note can retain the relevant application and redacted message without exposing credentials.
Keep a notice separate from a resolution
Check the current provider notice and the relevant official support route for an account-specific problem. An announced end time is not proof that a particular connection recovered, just as an old incident does not establish a present outage.
No account login, order, support message or uptime probe was performed for this article. Canadian readers should retain the applicable named timezone rather than assuming one Canadian local clock. The optional HashHedge link is a separate programme invitation and does not fix an existing FTMO connection or transfer an account.
Sources and rule dates
- FTMO CFDs: dated 22 October 2026 maintenance notice
Checked 2026-10-24. Selected scheduled CFD window, platforms and source clock; mutable latest-notice page, not an uptime measurement. - FTMO Futures: dated 22 October 2026 maintenance notice
Checked 2026-10-24. Selected scheduled Futures window, ET clock and named platforms; no actual interruption, recovery or personal-account observation.