Cryptic Launcher Autoupdate Problem
View Single Post
Join Date: Nov 2012
11-19-2012, 02:31 PM
Originally Posted by
Strange problem (and annoying it is).
Anyone care to compare tracerts for the problem?
I get the following: (early hops cut out for personal privacy reasons)
What I'm seeing implies that the problem is with Cogent Communications, who are probably the ISP for STO. What do other people see in route traces?
UPDATE: A friend who can connect traced it for me and got:
So, looking at the hop that he can make that I can't, it's something to do with:
Think someone messed up a routing table at cryptic? Or is it just some of us being filtered for some strange reason?
Same here, bos06.atlas.cogentco.com is the last step. Another couple of people from my ISP are in the same boat.
4 21 ms 8 ms 9 ms brnt-bb-1a-ae10-0.network.virginmedia.net [18.104.22.168]
5 9 ms 9 ms 9 ms brnt-bb-1b-ae0-0.network.virginmedia.net [22.214.171.124]
6 10 ms 10 ms 9 ms popl-bb-1a-as7-0.network.virginmedia.net [126.96.36.199]
7 15 ms 9 ms 9 ms popl-tmr-1-ae4-0.network.virginmedia.net [188.8.131.52]
8 17 ms 17 ms 25 ms amst-ic-1-as0-0.network.virginmedia.net [184.108.40.206]
9 26 ms 16 ms 18 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [220.127.116.11]
10 40 ms 17 ms 17 ms te0-0-0-7.mpd22.ams03.atlas.cogentco.com [18.104.22.168]
11 45 ms 28 ms 29 ms te0-4-0-7.ccr21.lpl01.atlas.cogentco.com [22.214.171.124]
12 94 ms 95 ms 92 ms te0-3-0-3.ccr22.bos01.atlas.cogentco.com [126.96.36.199]
13 109 ms 222 ms 162 ms te3-4.ccr01.bos06.atlas.cogentco.com [188.8.131.52]
14 * * * Request timed out.
15 * * * Request timed out.
Cogent are a high level network supplier and don't deal with us mere mortals, so someone at Cryptic needs to phone up Cogent and get them to sort it out.
PS : What's really fun is when Cogent network goes boom when I'm starting an STF, so when I do get back in I'm hit with the deadbeat leavers penalty. Thanks Cryptic.