View Single Post
Career Officer
Join Date: Jun 2012
Posts: 2,449
# 5
10-05-2013, 08:14 AM
Quote:
Originally Posted by starmada1 View Post
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bau>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * 25 ms 26 ms dvnp-dsl-gw14.dvnp.qwest.net [65.103.57.14]
3 26 ms 25 ms 41 ms dvnp-agw1.inet.qwest.net [67.7.0.105]
4 26 ms 26 ms 26 ms dvn-core-01.inet.qwest.net [205.171.164.93]
5 * * * Request timed out.
6 * * * Request timed out.
7 31 ms 31 ms 30 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
8 51 ms 52 ms 53 ms be101.ccr21.ord03.atlas.cogentco.com [154.54.13.
93]

9 53 ms 53 ms 53 ms be2005.ccr21.ord01.atlas.cogentco.com [66.28.4.7
3]
10 67 ms 56 ms 67 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
11 57 ms 67 ms 56 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 57 ms 66 ms 110 ms 38.111.40.114
13 68 ms 68 ms 67 ms 208.95.185.41

Trace complete.

I'm not trying to point fingers or place blame, I'm just curious about what's going on. Are these results good or bad?
The latency value, by itself, isn't bad. There is a suspicious increase of latency on the Qwest Communication gateway to the Cogent backbone...

The question that needs to be asked is whats your connection throughput. (And this is what the 'Net Test' diagnostics would show.) A low throughput could indicate a issue with severe packet drop somewhere in the route to the STO servers. A failed connection could indicate a configuration problem with the Firewall/Router or possibly ISP blocking.

So with whats been presented so far, there is not enough information to determine what the problem is...