Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms mynetwork.home [192.168.2.1]
2 12 ms 11 ms 12 ms bas2-longueuil15_lo0_SYMP.net.bell.ca [64.230.20
0.33]
3 11 ms 12 ms 12 ms dis2-stlambert20_5-1_100.net.bell.ca [64.230.38.
24]
4 24 ms 56 ms 33 ms agg2-montreal02_7-2-0.net.bell.ca [64.230.32.10]
5 20 ms 20 ms 23 ms core3-montreal02_xe0-8-2-0_core.net.bell.ca [64.
230.170.245]
6 24 ms 24 ms 24 ms newcore2-newyork83_so5-0-0_0 [64.230.187.236]
7 23 ms 24 ms 25 ms bx5-newyork83_pos0-4-0-0.net.bell.ca [64.230.187
.22]
8 22 ms 22 ms 22 ms te0-7-0-16.ccr21.jfk05.atlas.cogentco.com [154.5
4.10.205]
9 25 ms 24 ms 25 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
.57]
10 28 ms 27 ms 28 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
11 31 ms 31 ms 30 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 39 ms 35 ms 35 ms 38.111.40.114
13 28 ms 30 ms 32 ms patchserver2.crypticstudios.com [208.95.185.41]
So did you wait 325 seconds for the 'Path Ping' to complete ???
Nothing is particularly wrong with the 'Trace Route' so its not a network latency issue...
The inconsistent results of the 'Net Test' indicates a connection quality issue of some kind that is unrelated to the STO servers, as 'Net Test' talks to its own dedicated diagnostic server, not the STO servers...
So we need the 'Path Ping' complete results to pinpoint the problem....
Comments
So did you wait 325 seconds for the 'Path Ping' to complete ???
Nothing is particularly wrong with the 'Trace Route' so its not a network latency issue...
The inconsistent results of the 'Net Test' indicates a connection quality issue of some kind that is unrelated to the STO servers, as 'Net Test' talks to its own dedicated diagnostic server, not the STO servers...
So we need the 'Path Ping' complete results to pinpoint the problem....