Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Admin>tracert crypticstudios.com
Tracing route to crypticstudios.com [208.95.185.46]
over a maximum of 30 hops:
1 39 ms 37 ms
2 23 ms 18 ms
3 10 ms 12 ms
4 14 ms 15 ms
5 22 ms 19 ms 18 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 17 ms 18 ms 18 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 20 ms 18 ms 18 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
8 18 ms 19 ms 18 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.
234]
9 28 ms 31 ms 24 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40
.74]
10 35 ms 31 ms 31 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
11 31 ms 30 ms 31 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 30 ms 34 ms 35 ms 38.111.40.114
13 31 ms 31 ms 32 ms sitedown.crypticstudios.com [208.95.185.46]
Trace complete.
Previous tracert was going through gtt.net instead on congentco
Previous tracert was going through gtt.net instead on congentco
Though in reality, the 'Trace Route' is showing excellent network latency values. So what ever is causing your problems, its not a network latency issue...
Now if we only had the 'Net Test' diagnostic results (which test for open network ports and sustained network throughput) and the 'Path Ping' results (which checks for lost or thrown away data packets along your connection route) ...
So 'Net Test' shows that you can't maintain a consistent sustained network connection throughput, which hints at a intermittent connection quality issue of some kind, possibly network load based...
Now a 100% Packet loss could be caused by the backbone router being configured not to support the network protocol that 'Path Ping' uses, but if this was the case, you would normally expect this behavior on all the nodes of the Cogent Backbone, and this is not the case...
So assuming that the issue is being caused by traffic congestion on the Cogent Backbone, you should open a Ticket with Cryptic with the 'Net Test' and 'Path Ping' information, so that Cryptic/PWE can kick Cogent a few more times to try to get this addressed...
You can also try the 'Proxy' setting in the Launcher Option Menu to see if this setting will let you bypass the suspected network congestion... It may, or may not work, but it doesn't hurt to try, as you can always change the settings back later...
Comments
Though in reality, the 'Trace Route' is showing excellent network latency values. So what ever is causing your problems, its not a network latency issue...
Now if we only had the 'Net Test' diagnostic results (which test for open network ports and sustained network throughput) and the 'Path Ping' results (which checks for lost or thrown away data packets along your connection route) ...
So 'Net Test' shows that you can't maintain a consistent sustained network connection throughput, which hints at a intermittent connection quality issue of some kind, possibly network load based...
Now a 100% Packet loss could be caused by the backbone router being configured not to support the network protocol that 'Path Ping' uses, but if this was the case, you would normally expect this behavior on all the nodes of the Cogent Backbone, and this is not the case...
So assuming that the issue is being caused by traffic congestion on the Cogent Backbone, you should open a Ticket with Cryptic with the 'Net Test' and 'Path Ping' information, so that Cryptic/PWE can kick Cogent a few more times to try to get this addressed...
You can also try the 'Proxy' setting in the Launcher Option Menu to see if this setting will let you bypass the suspected network congestion... It may, or may not work, but it doesn't hurt to try, as you can always change the settings back later...