View Single Post
Career Officer
Join Date: Jun 2012
Posts: 2,196
# 77
12-19-2012, 11:32 PM
Quote:
Originally Posted by ames1 View Post
Here are my test results.
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 * 192.168.0.1
2 * * * Request timed out.
3 29 ms 15 ms 15 ms 64.59.147.213
4 31 ms 22 ms 23 ms 66.163.69.145
5 37 ms 33 ms 23 ms rc4wt-pos14-0-0.wa.shawcable.net [66.163.76.130]
6 39 ms 18 ms 14 ms xe-11-0-0.edge1.Seattle3.Level3.net [4.59.232.85]
7 238 ms 209 ms 228 ms te7-8.ccr02.sea02.atlas.cogentco.com [154.54.12.25]
8 * 232 ms 203 ms te2-7.ccr02.sea01.atlas.cogentco.com [154.54.85.181]

9 55 ms 70 ms 62 ms te0-7-0-4.ccr21.slc01.atlas.cogentco.com [154.54.80.10]
10 81 ms 79 ms * te4-3.ccr01.den01.atlas.cogentco.com [154.54.0.41]
11 89 ms * 79 ms te0-2-0-7.ccr21.mci01.atlas.cogentco.com [154.54.82.206]
12 * 71 ms 70 ms te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
13 97 ms 97 ms 95 ms te0-1-0-6.ccr22.bos01.atlas.cogentco.com [154.54.43.206]
14 96 ms 98 ms 109 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
15 100 ms 95 ms 101 ms 38.111.40.114
16 106 ms 106 ms 110 ms 208.95.185.41

Trace complete.
Looks like the issue is the gateway onto the Cogent Communications backbone in Seattle. You might want to contact your ISP (presumably Shaw Cable) and see if their aware of this problem...