Latency due to routing?


I'm based in Perth, Western Australia. When I signed up with my FCM I was asked what would be the closest CQG exchange, and I chose Sydney. My FCM have confirmed this choice.

When I connect via Multicharts I connect to the following websocket URL: wss://

When I do a traceroute to that address I end up in Singapore via Japan, please see the output from traceroute that confirms this:

traceroute to (, 64 hops max, 52 byte packets
1 nb604n.home ( 1.507 ms 1.023 ms 0.968 ms
2 ( 7.877 ms 8.464 ms 8.294 ms
3 ( 8.161 ms 8.038 ms 12.018 ms
4 ( 157.118 ms 159.138 ms 177.636 ms
5 ( 200.047 ms 154.918 ms 160.110 ms
6 ( 73.518 ms 56.433 ms 56.022 ms
7 ( 155.085 ms 157.971 ms 154.648 ms
8 ( 159.044 ms 155.157 ms 161.314 ms
9 ( 297.929 ms 306.777 ms 309.455 ms
10 ( 304.850 ms 296.498 ms 224.084 ms
11 ( 222.633 ms ( 259.048 ms ( 296.709 ms
12 ( 305.959 ms ( 308.005 ms ( 293.655 ms
13 ( 304.391 ms 296.951 ms 224.342 ms

My ping time is about 250ms to Singapore, but if I ping one of the Sydney CQG servers it's about 50ms. This is a massive difference for me as I'm a short term trader.

PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=119 time=57.869 ms

Compared with:

PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=116 time=314.538 ms
64 bytes from icmp_seq=1 ttl=116 time=439.184 ms
64 bytes from icmp_seq=2 ttl=116 time=258.224 ms

Is it possible for me to connect to Sydney CQG servers???

Thanks in advance,



  • Hi Kevin,

    Sorry to hear about the connectivity issues. Please check with Multicharts to see if they can change your connection; as we don't have that ability. You may also want to check with your ISP to see why you are being routed through Japan which is adding some latency.
  • I can change the address, but what address should I change it to? The one I used in the example before was one I found for CQG Net & doesn't accept websocket connections (was:// protocol)


  • sorry that should be wss:// protocol
  • Hi Kevin. There are two issues here. First is the location of the CQG servers. Currently there are WebAPI servers located in Singapore but not in Australia. Our server operations group has advised us that discussions are underway regarding adding servers in Sydney but at the moment there is no ETA for that. Compounding this is the second issue which is that recent typhoons have caused damage to undersea cables providing internet service to Australia. Many latency issues have been reported due to the routing changes that had to be made. Here's one link providing some further details on that:
    Hope this information helps. Let us know if you have any further questions.

  • Thanks for the update. It makes sense now, hopefully they repair the cables quickly and I'll keep a lookout for the Sydney WebAPI
Sign In or Register to comment.