Same here from Bonnie Scotland (and yes, it's raining, why do you ask?) - traceroute is fine until it reaches Boston, then it sinks faster than a crate of tea in a tax dispute.
I am also having an issue with my launcher not being able to connect to the patch sever. I use Verizon DSL, with the fastest DSL they offer in my area. What is odd, is that everything was fine last night, I was able to login with no issues. Maybe just a weird quirk of seeing a que screen, stating that I was 1 of 1 in line to sign on. But that went away and I was able to sign on fairly quickly.
Here is my Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms TomatoNET.TomatoSandwich [192.168.2.1]
2 27 ms 26 ms 25 ms 10.9.79.1
3 27 ms 26 ms 26 ms P0-3-0-1.BSTNMA-LCR-22.verizon-gni.net [130.81.193.238]
4 26 ms 26 ms 25 ms ae0-0.BOS-BB-RTR2.verizon-gni.net [130.81.209.94]
5 29 ms 28 ms 29 ms 0.so-0-2-0.XL4.BOS4.ALTER.NET [152.63.16.141]
6 28 ms 28 ms 28 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
7 34 ms 34 ms 32 ms internap-gw.customer.alter.net [65.207.236.58]
8 43 ms 32 ms 46 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 45 ms 35 ms 35 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 36 ms * * 208.95.185.41
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
I guess for the most part none of them meet the minimum for column 2. And the bolded lines are what didn't meet all three columns.
Generally though, I tend not to have issues online with STO. The only rare instances where I may have an issue with rubberbanding or disconnects is when I really hammer my internet connection with high bandwidth stuff while playing STO. Generally I tend to play STO while watching netflix in HD, which I do not have many issues doing.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 1 ms 1 ms 2 ms 192.168.99.1
3 8 ms 6 ms 6 ms 192.168.50.1
4 6 ms 7 ms 11 ms 68-188-12-17.static.stls.mo.charter.com [68.188.
12.17]
5 18 ms 16 ms 14 ms 10.174.64.1
6 12 ms 15 ms 15 ms acr01osbhmo-tge-4-3.osbh.mo.charter.com [96.34.5
6.14]
7 13 ms 17 ms 14 ms dtr01osbhmo-tge-0-6-1-0.osbh.mo.charter.com [96.
34.50.34]
8 19 ms 18 ms 27 ms dtr01blvlil-tge-0-4-0-1.blvl.il.charter.com [96.
34.48.125]
9 29 ms 32 ms 26 ms bbr01blvlil-tge-0-0-0-0.blvl.il.charter.com [96.
34.2.20]
10 20 ms 30 ms 18 ms 206.181.23.109
11 * 138 ms 30 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177]
12 * 29 ms 32 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194]
13 33 ms 30 ms 25 ms te0-7-0-8.ccr21.ord03.atlas.cogentco.com [154.54
.10.181]
14 25 ms 27 ms 26 ms te0-3-0-0.mpd21.ord01.atlas.cogentco.com [154.54
.5.17]
15 51 ms 52 ms 56 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.45.246]
16 62 ms 61 ms 63 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22
i googled and researched all i could about cogentco... evidently they are HORRIBLE and well known for bottlenecks and downtime on thier routing servers...
2 tries from the last 20 mins (2 different dyn. IPs)
1 55 ms 45 ms 45 ms *
2 46 ms 48 ms 47 ms 217.237.156.74
3 53 ms 54 ms 52 ms 194.25.6.82
4 53 ms 54 ms 54 ms te0-7-0-1.ccr21.fra03.atlas.cogentco.com [130.17.14.149]
5 78 ms 78 ms 77 ms te0-4-0-2.ccr21.ams03.atlas.cogentco.com [154.5.39.181]
6 77 ms 77 ms 78 ms te0-3-0-2.ccr21.lpl01.atlas.cogentco.com [154.5.37.94]
7 138 ms 138 ms 139 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com [154.5.31.229]
8 288 ms 208 ms 207 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.4]
9 * * * Zeit?berschreitung der Anforderung.
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 140 ms * * playstartrekonline.eu [208.95.185.44]
28 * * 137 ms playstartrekonline.eu [208.95.185.44]
Ablaufverfolgung beendet.
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 46 ms 45 ms 45 ms *
2 47 ms 48 ms 53 ms 217.237.156.70
3 54 ms 53 ms 53 ms 194.25.6.78
4 55 ms 54 ms 54 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [130.117.14.105]
5 78 ms 94 ms 94 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.117.1.162]
6 87 ms 88 ms 89 ms te0-2-0-7.ccr21.lpl01.atlas.cogentco.com [154.54.37.90]
7 138 ms 139 ms 138 ms te0-7-0-3.ccr21.bos01.atlas.cogentco.com [154.54.31.169]
8 166 ms 144 ms 138 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
9 * * 138 ms 38.111.40.114
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
I like the DNS/updated route explanation. It seems to fit the facts as we know them, including the different traces from mobile connections vs broadband connections...
If they could push the working route out to the hops that are hanging...?
I just finished a vortex elite and got 95 omega marks when the server said that it goes down for maintenance in one min, so I felt I'm lucky.... Now I cannot say the same...
Those that are saying the problem is in Boston are ignoring the TraceRTs that fail despite not being routed through MA. They're also ignoring the successful 3G network tracert through Boston. If the problems were out of house these inconsistencies wouldn't exist.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms BTHomeHub.home [192.168.1.254]
2 8 ms 9 ms 9 ms 217.32.147.97
3 9 ms 9 ms 9 ms 217.32.147.141
4 13 ms 13 ms 13 ms 212.140.206.82
5 13 ms 13 ms 12 ms 217.41.169.193
6 13 ms 14 ms 13 ms 217.41.169.109
7 13 ms 13 ms 13 ms 109.159.251.247
8 27 ms 24 ms 24 ms core1-te-0-13-0-12.ilford.ukcore.bt.net [109.159
.251.127]
9 20 ms 20 ms 20 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 22 ms 23 ms 23 ms 166-49-211-157.eu.bt.net [166.49.211.157]
11 23 ms 22 ms 23 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 20 ms 20 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 23 ms 22 ms 23 ms te0-5-0-6.mpd21.lon13.atlas.cogentco.com [154.54
.74.50]
14 95 ms 97 ms 97 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.30.129]
15 95 ms 94 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 101 ms 105 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
19 96 ms * * www.playstartrekonline.com [208.95.185.44]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Looks like mine fails at the same hop everybody else's does.
I think the Iranians were trying to hit Israel with a Computer Virus and it was deflected to Boston. :eek:
That's my story and I'm sticking to it! :P
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
Ok guys. i just checked Champions as well. Get the same problem so it is clearly a server issue there end from most EU countries and perhaps others which are using the EU proxy??
So, it looks like those that can tether to a mobile ISP can patch, start the game, get to the character screen, then disconnect and launch from the actual .exe file, if I am keeping up on all the posts correctly. So patching is the issue.
So it seems possible a route hasn't been pushed to the regular ISPs that has been sucessfully pushed to the mobile ISPs for getting to the patcher. Again, a rough guess.
Comments
Here is my Tracert:
Also Nettest Results:
I guess for the most part none of them meet the minimum for column 2. And the bolded lines are what didn't meet all three columns.
Generally though, I tend not to have issues online with STO. The only rare instances where I may have an issue with rubberbanding or disconnects is when I really hammer my internet connection with high bandwidth stuff while playing STO. Generally I tend to play STO while watching netflix in HD, which I do not have many issues doing.
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 1 ms 1 ms 2 ms 192.168.99.1
3 8 ms 6 ms 6 ms 192.168.50.1
4 6 ms 7 ms 11 ms 68-188-12-17.static.stls.mo.charter.com [68.188.
12.17]
5 18 ms 16 ms 14 ms 10.174.64.1
6 12 ms 15 ms 15 ms acr01osbhmo-tge-4-3.osbh.mo.charter.com [96.34.5
6.14]
7 13 ms 17 ms 14 ms dtr01osbhmo-tge-0-6-1-0.osbh.mo.charter.com [96.
34.50.34]
8 19 ms 18 ms 27 ms dtr01blvlil-tge-0-4-0-1.blvl.il.charter.com [96.
34.48.125]
9 29 ms 32 ms 26 ms bbr01blvlil-tge-0-0-0-0.blvl.il.charter.com [96.
34.2.20]
10 20 ms 30 ms 18 ms 206.181.23.109
11 * 138 ms 30 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177]
12 * 29 ms 32 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194]
13 33 ms 30 ms 25 ms te0-7-0-8.ccr21.ord03.atlas.cogentco.com [154.54
.10.181]
14 25 ms 27 ms 26 ms te0-3-0-0.mpd21.ord01.atlas.cogentco.com [154.54
.5.17]
15 51 ms 52 ms 56 ms te0-4-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.45.246]
16 62 ms 61 ms 63 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22
i googled and researched all i could about cogentco... evidently they are HORRIBLE and well known for bottlenecks and downtime on thier routing servers...
1 55 ms 45 ms 45 ms *
2 46 ms 48 ms 47 ms 217.237.156.74
3 53 ms 54 ms 52 ms 194.25.6.82
4 53 ms 54 ms 54 ms te0-7-0-1.ccr21.fra03.atlas.cogentco.com [130.17.14.149]
5 78 ms 78 ms 77 ms te0-4-0-2.ccr21.ams03.atlas.cogentco.com [154.5.39.181]
6 77 ms 77 ms 78 ms te0-3-0-2.ccr21.lpl01.atlas.cogentco.com [154.5.37.94]
7 138 ms 138 ms 139 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com [154.5.31.229]
8 288 ms 208 ms 207 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.4]
9 * * * Zeit?berschreitung der Anforderung.
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 140 ms * * playstartrekonline.eu [208.95.185.44]
28 * * 137 ms playstartrekonline.eu [208.95.185.44]
Ablaufverfolgung beendet.
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 46 ms 45 ms 45 ms *
2 47 ms 48 ms 53 ms 217.237.156.70
3 54 ms 53 ms 53 ms 194.25.6.78
4 55 ms 54 ms 54 ms te0-7-0-7.ccr21.fra03.atlas.cogentco.com [130.117.14.105]
5 78 ms 94 ms 94 ms te0-2-0-2.ccr21.ams03.atlas.cogentco.com [130.117.1.162]
6 87 ms 88 ms 89 ms te0-2-0-7.ccr21.lpl01.atlas.cogentco.com [154.54.37.90]
7 138 ms 139 ms 138 ms te0-7-0-3.ccr21.bos01.atlas.cogentco.com [154.54.31.169]
8 166 ms 144 ms 138 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
9 * * 138 ms 38.111.40.114
10 * * * Zeit?berschreitung der Anforderung.
11 * * * Zeit?berschreitung der Anforderung.
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
Was starting to think it was my ISP, they've messed with game connections before...
I'll try to be patient
If they could push the working route out to the hops that are hanging...?
....screwed like the rest of us.
Sorry I cant get on but wont post my details either....if you want to hack try 24.132........
http://sto-forum.perfectworld.com/showpost.php?p=7690471&postcount=490
tracert pacthserver.crypticstudios.com
Unable to resolve target system name pacthserver.crypticstudios.com.
C:\User\>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 50 ms 16 ms 46 ms ***-PC [0.0.0.0]
2 54 ms 14 ms 37 ms popl-core-2b-ae4-2185.network.virginmedia.net [62.255.161.201]
3 42 ms 29 ms 37 ms popl-bb-1b-ae9-0.network.virginmedia.net [82.14.127.245]
4 107 ms 84 ms 7 ms popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
5 25 ms 22 ms 15 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]
6 39 ms 16 ms 30 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
7 38 ms 15 ms 35 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.117.15.5]
8 26 ms 30 ms 55 ms te0-0-0-7.mpd21.ams03.atlas.cogentco.com [130.117.2.61]
9 37 ms 23 ms 55 ms te0-5-0-7.ccr22.lpl01.atlas.cogentco.com [130.117.50.85]
10 107 ms 88 ms 89 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [154.54.31.189]
11 101 ms 216 ms 215 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\>
Pretty much the same issues as everyone else.
P.S My internet connection is fine and my computer is more than adequate for this game.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms BTHomeHub.home [192.168.1.254]
2 8 ms 9 ms 9 ms 217.32.147.97
3 9 ms 9 ms 9 ms 217.32.147.141
4 13 ms 13 ms 13 ms 212.140.206.82
5 13 ms 13 ms 12 ms 217.41.169.193
6 13 ms 14 ms 13 ms 217.41.169.109
7 13 ms 13 ms 13 ms 109.159.251.247
8 27 ms 24 ms 24 ms core1-te-0-13-0-12.ilford.ukcore.bt.net [109.159
.251.127]
9 20 ms 20 ms 20 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 22 ms 23 ms 23 ms 166-49-211-157.eu.bt.net [166.49.211.157]
11 23 ms 22 ms 23 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 20 ms 20 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 23 ms 22 ms 23 ms te0-5-0-6.mpd21.lon13.atlas.cogentco.com [154.54
.74.50]
14 95 ms 97 ms 97 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.30.129]
15 95 ms 94 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 101 ms 105 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
19 96 ms * * www.playstartrekonline.com [208.95.185.44]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Looks like mine fails at the same hop everybody else's does.
I also can't access the main website.
One is logged on right now and as stable as a rock.
Also, as you can see, I can log on here and post.
Everything I've seen on here points to a problem with the patch server, though why some can get on and not others is a mystery.
All the trace logs seem to point at Cogent. Maybe that's where the problem is.
I have noticed though that www.startrekonline.com does not seem to load either.
That's my story and I'm sticking to it! :P
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
1 <1 ms <1 ms <1 ms ***.***.***.*** (IP Removed)
2 13 ms 13 ms 13 ms ***.***.***.*** (IP Removed)
3 18 ms 15 ms 15 ms ***.***.***.*** (IP Removed)
4 16 ms 15 ms 16 ms ***.***.***.*** (IP Removed)
5 24 ms 24 ms 24 ms ***.***.***.*** (IP Removed)
6 25 ms 25 ms 25 ms 0.xe-7-2-0.XL3.NYC1.ALTER.NET [152.63.6.145]
7 34 ms 34 ms 34 ms 0.ge-4-0-0.XL3.BOS4.ALTER.NET [152.63.17.30]
8 38 ms 38 ms 38 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
9 34 ms 35 ms 36 ms internap-gw.customer.alter.net [65.207.236.58]
10 39 ms 39 ms 38 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 35 ms 34 ms 34 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
So it seems possible a route hasn't been pushed to the regular ISPs that has been sucessfully pushed to the mobile ISPs for getting to the patcher. Again, a rough guess.