In order to troubleshoot your connection, you can perform a PING test on servers just in front of our servers and perform a TRACEROUTE to our trading servers.
1. PING TEST
Open a command prompt window by going to the Windows start button and type CMD.
Then, click on the result:
Type in the command:
ping 22.214.171.124 -n 100
This will test your response time when you connect to us via Internap. Review the results:
Ping statistics for 126.96.36.199:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 57ms, Average = 31ms
Any lost packets mean your connection is impaired and your experience with us might not be ideal. You may want to notify your internet provider to see if your modem or line needs servicing. If your average time is more than 500ms, your data broadcasted is a half-second behind the actual time.
2. TRACEROUTE TEST
With the command prompt still open, type in the command:
Tracing route to td-prod-gainfutures-com.trafficmanager.net [188.8.131.52]
over a maximum of 30 hops:
1 1 ms 2 ms <1 ms router.asus.com [192.168.2.1]
2 2 ms 1 ms 1 ms 192.168.1.254
3 29 ms 21 ms 20 ms x-x-x-1.lightspeed.clmboh.sbcglobal.net [x.x.x.1]
4 * * * Request timed out.
5 31 ms 30 ms 30 ms x.x.x.x
6 33 ms 31 ms 30 ms cgcil403igs.ip.att.net [184.108.40.206]
7 30 ms 30 ms 29 ms be3039.ccr41.ord03.atlas.cogentco.com [220.127.116.11]
8 32 ms 35 ms 38 ms 18.104.22.168
9 30 ms 29 ms 30 ms 173-219-221-161.suddenlink.net [22.214.171.124]
The number of hops will increase the chance of issues as your connection is reliant on more parties to route you to our servers. Anything over 15 hops is not ideal and may cause latency. Any hop with more than 500 ms is not ideal and may cause prices or orders to be lagged. You might see some hops with "request timed out," as shown in hop 4. This is ok, it just means the switch is not pingable.