Skip to main content
Trader problem · Diagnose

cTrader Connection Unstable: What Helps

cTrader drops, lags, or shows delayed quotes. The diagnostic is the same as MT4 and MT5 - it's a TCP connection over your network to a remote server. The fix options are also the same.

TL;DR

cTrader connects to Spotware's infrastructure over TCP - the same fundamental mechanism as MT4 and MT5. If your route to their servers has high latency, packet loss, or instability, cTrader shows stream latency warnings, delayed quotes, and connection drops. The diagnostic ladder is identical: Wi-Fi first, then router, then ISP routing to the cTrader server region, then a proxy or VPS.

Symptom
Stream latency warning, frozen quotes, or repeated disconnections in cTrader.
Root cause
Latency or packet loss between your machine and cTrader's server infrastructure.
What differs
cTrader shows stream latency explicitly - MT4/MT5 do not. Same problem, more visible.

What's actually happening

cTrader maintains a persistent connection to the cTrader server for your broker, which runs on Spotware's infrastructure. This is a TCP connection - exactly like MT4 - and it requires consistent, low-latency packet delivery to stay stable and keep quotes current.

cTrader is actually more transparent about this than MT4. It shows a "stream latency" indicator in the interface, which tells you the delay between when the server generated a quote and when your platform received it. If that number is high or jumping, your route is the problem.

The connection uses standard ports (usually 443) and behaves the same way as any other trading platform TCP connection under the hood. All the same network variables - ISP routing, Wi-Fi packet loss, router timeouts - apply equally to cTrader.

Quick self-diagnosis - 5 minutes

  1. Check the stream latency indicator
    cTrader shows stream latency in the bottom bar. Under 50 ms is healthy. 100+ ms and jumping means your route to the cTrader server is adding significant delay. Note whether the number spikes at specific times or is consistently high.
  2. Switch to Ethernet
    If stream latency drops and connection stabilizes on a wired connection, Wi-Fi is the cause. This is the most common and cheapest fix.
  3. Ping the cTrader server
    Your broker will have cTrader server addresses in their platform settings. Run ping that-server-address.com and note the RTT. Compare to the stream latency shown in cTrader - they should roughly match (stream latency includes server processing, so it may be slightly higher).
  4. Test via mobile hotspot
    If stream latency drops significantly on mobile data, your ISP's path to Spotware's infrastructure is the variable. Mobile data often uses different backbone routing.
  5. Test at different times of day
    If instability is worse at London or NY open, it's ISP route congestion during peak hours - not a permanent routing failure.

What actually fixes this - honest ranking

1

Ethernet over Wi-Fi

The fastest and cheapest improvement. Wi-Fi jitter and packet loss are the most common causes of stream latency spikes. Wired connections eliminate both. Check the stream latency indicator before and after.

2

TradersProxy - clean route to cTrader's infrastructure

TradersProxy routes TCP traffic to trading server infrastructure. cTrader connections route through the proxy the same as MT4 or MT5. If your ISP's path to Spotware's server region is poor, a cleaner routed path reduces stream latency and improves connection stability.

3

VPS near the cTrader server region

For cTrader algo traders (cBots) who need 24/7 uptime and minimal latency, a VPS in the same datacenter region as the cTrader server achieves the lowest possible stream latency. Management overhead is the tradeoff.

4

Change ISP or use a different network

If your ISP consistently provides a poor route to Spotware's infrastructure and a proxy doesn't solve it, a different ISP may use a different backbone path to those servers. Verify by testing on mobile data first.

If the route is the problem, a dedicated trading proxy is the fix at the infrastructure level — a relay node co-located near your broker's datacenter replaces the unstable public internet hops with a dedicated path. 7-day trial on Starter →

When it's not a network problem

  • Spotware platform outage. Check Spotware's status page and your broker's social channels during widespread connection issues. A platform outage will affect all users regardless of their network quality.
  • Broker-side cTrader server overload. Some brokers underprovision their cTrader server capacity. During peak sessions, the server processing backlog adds to stream latency independent of your network speed.
  • cTrader software bug. Occasionally a cTrader platform update introduces bugs affecting connection stability. Check Spotware's changelog and community forums if issues started after an update.
  • Firewall or antivirus interference. Security software that intercepts TCP connections can break cTrader's protocol the same way it can break MT4. Add cTrader to your exclusion list if you suspect this.
FAQ

cTrader uses the FIX protocol over TCP and connects to a different infrastructure than MT4 or MT5. The underlying stability principles are the same - TCP connection to a remote server - but the endpoint is Spotware's cTrader infrastructure rather than MetaTrader's brokerserver. Routing issues affect both identically; the diagnostic steps are the same.

Yes. TradersProxy routes TCP traffic at the network layer. cTrader's FIX/TCP connections route through the proxy the same way MT4 connections do. The proxy improves the network path for any TCP-based trading platform.

The cTrader web platform uses WebSocket connections over HTTPS. While the underlying protocol differs from the desktop app, it still depends on the route to Spotware's servers. Latency and packet loss affect the web platform similarly to the desktop.

Your browser loads content from CDNs optimised for fast delivery worldwide. cTrader connects to a specific server infrastructure for your broker - which routes through different network paths. The two routes are independent, so your browser can feel fast while cTrader lags.

cTrader shows a stream latency indicator that reflects the delay between the server's quote time and when it arrives on your platform. High stream latency means your route to the cTrader server is adding delay to quote delivery - you're seeing prices that are slightly older than what the server is currently sending.