Guessing here but 1. Ping the router to see what the latency on your internal network is 2. Ping the slingshot host to see what the latency is between you and them - primary dns is 188.8.131.52 3. Ping google to see what the latency is to there
Would also do it at different times of the day and hopefully the app you are using will provide some sort of traceroute functionality
Are you getting dropped connections from slingshot quite often?
I did a quick look on the online help for ss and the IP is for their primary DNS server so its a good candidate to hit first and baseline what your connection is like using ping (guessing)
also, try doing a tracert from the windows command line: tracert -d 184.108.40.206 It will tell you the number of hops it takes for the request to get to the destination, which is the slingshot dns - for me I get:
2 11 ms 11 ms 11 ms 220.127.116.11 << xtra 3 * * * Request timed out. 4 21 ms 20 ms 20 ms 18.104.22.168 << global gateway interface/telecom 5 20 ms 20 ms 20 ms 22.214.171.124 6 21 ms 21 ms 21 ms 126.96.36.199 7 22 ms 21 ms 21 ms 188.8.131.52 8 21 ms 21 ms 21 ms 184.108.40.206 9 21 ms 21 ms 21 ms 220.127.116.11 << Callplus server - primary dns
your traceroute will look different to this
the delays start hitting when I get to telecom - 18.104.22.168 (http://tools.whois.net/whoisbyip/ will give you the server information).