I'll say it again: "has Anyone where you work ever tried "strongly suggesting" to PWE to change ISPs?" Or can we expect this BS to happen again the next time Cogent decides to throttle your bandwith? Like in the next month or two?
We've been waiting for Zeb or Strum to update us: Zeb: "We cannot do anything about it until Cogencto fixes the issue themselves, for this is not a Server issue. It is an issue with users who have ISPs that route through Cogentco's Network in the Boston area to get to our game Servers, which are also in Boston. We cannot give an ETA until we hear back from Cogentco."
Have you still not heard back from Cogentco? I'm sure we're all glad to have the Cogent routes working again, but don't you feel obligated to follow-up with Cogentco about why this happened in the first place and what they're doing to prevent it from happening again?
If they don't have a good answer or nothing at all, don't you feel obligated to update the playerbase with a message from PWE stating something about plans for switching ISPs so we are not relying on Cogentco anymore?
This is NOT the first time that a substantial number of players can't access the game due to Cogentco.
silvergryphMember, NW M9 PlaytestPosts: 740Arc User
When you need an ISP that can handle the kind of traffic needed for an MMO, there is rarely a second choice in any given geographical area. And Cogentco is one of the top providers worldwide. It's the internet. There is exactly zero guarantee that all of this is going to work at any given moment.
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 8 ms 8 ms 9 ms cpe-24-209-160-1.wi.res.rr.com [24.209.160.1] 3 21 ms 22 ms 19 ms tge7-1.wksawi1301h.midwest.rr.com [24.164.235.113] 4 12 ms 11 ms 11 ms be41.milzwift01r.midwest.rr.com [65.31.113.76] 5 15 ms 15 ms 14 ms bu-ether18.chctilwc00w-bcr00.tbone.rr.com [66.109.6.206] 6 14 ms 15 ms 15 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20] 7 12 ms 13 ms 12 ms 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66] 8 15 ms 12 ms 12 ms te0-1-0-22.ccr41.ord03.atlas.cogentco.com [154.54.11.145] 9 14 ms 16 ms 13 ms be2216.ccr41.ord01.atlas.cogentco.com [154.54.24.201] 10 31 ms 21 ms 21 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86] 11 44 ms 48 ms 45 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89] 12 48 ms 48 ms 50 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9] 13 48 ms 48 ms 47 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134] 14 41 ms 43 ms 40 ms 38.111.40.114 15 41 ms 41 ms 41 ms 198.49.243.253 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 47 ms 142 ms 115 ms patchserverrebirth.crypticstudios.com [208.95.18 5.41]
When you need an ISP that can handle the kind of traffic needed for an MMO, there is rarely a second choice in any given geographical area. And Cogentco is one of the top providers worldwide. It's the internet. There is exactly zero guarantee that all of this is going to work at any given moment.
Really, is that how the internet works? Seriously though, many online retailers and service providers sign a contract with their ISPs which do in fact guarantee a typical uptime, anywhere from 95-99%. If leverage can't be found from competition, there are other negotiable things that can be considered. At this point, most players that have been affected by more than 5% downtime would really appreciate some sort of tangible good-will gesture from PWE, not silence.
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 2 ms 1 ms 1 ms 192.168.0.1 3 * * * Request timed out. 4 34 ms 26 ms 13 ms 10.162.11.21 5 70 ms 74 ms 71 ms 10.162.11.9 6 85 ms 79 ms * 200.79.231.81.static.cableonline.com.mx [200.79. 231.81] 7 79 ms 109 ms 80 ms 10.19.132.17 8 95 ms 88 ms 117 ms 63.245.6.137 9 * 134 ms 152 ms xe-10-2-3.edge2.Miami1.Level3.net [4.31.223.77]
10 128 ms 132 ms 121 ms ae-1-51.edge1.Miami2.Level3.net [4.69.138.75] 11 122 ms 128 ms 112 ms francetelecom-level3-ge.Atlanta1.Level3.net [4.6 8.110.170] 12 * 148 ms 136 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80 .41] 13 128 ms 258 ms 124 ms be2122.ccr41.atl01.atlas.cogentco.com [154.54.24 .193] 14 161 ms 169 ms 126 ms be2112.ccr41.dca01.atlas.cogentco.com [154.54.7. 157] 15 147 ms 135 ms 138 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31 .118] 16 175 ms 177 ms 161 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30 .14] 17 135 ms 151 ms 165 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c om [154.54.46.134] 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.
0
zebularMember, Neverwinter Moderator, NW M9 PlaytestPosts: 15,270Community Moderator
Closing this up as this issue is resolved and the latest posted tracerts suggest some other issue, whether end-user, isp, server, or cogent, I am not sure. We're not seeing any apparent server issues at present. Please use one of the Stickies in this Technical forum instead, or create a new thread on your particular trace for player support. If you wish to have game support take a look at your tracert, please file a Support Ticket. Thanks!
Comments
Or can we expect this BS to happen again the next time Cogent decides to throttle your bandwith? Like in the next month or two?
We've been waiting for Zeb or Strum to update us:
Zeb: "We cannot do anything about it until Cogencto fixes the issue themselves, for this is not a Server issue. It is an issue with users who have ISPs that route through Cogentco's Network in the Boston area to get to our game Servers, which are also in Boston. We cannot give an ETA until we hear back from Cogentco."
Have you still not heard back from Cogentco? I'm sure we're all glad to have the Cogent routes working again, but don't you feel obligated to follow-up with Cogentco about why this happened in the first place and what they're doing to prevent it from happening again?
If they don't have a good answer or nothing at all, don't you feel obligated to update the playerbase with a message from PWE stating something about plans for switching ISPs so we are not relying on Cogentco anymore?
This is NOT the first time that a substantial number of players can't access the game due to Cogentco.
D&D Home Page - What Class Are You? - Build A Character - D&D Compendium
Champions Online Advanced Forum Search
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\steve_000>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 8 ms 8 ms 9 ms cpe-24-209-160-1.wi.res.rr.com [24.209.160.1]
3 21 ms 22 ms 19 ms tge7-1.wksawi1301h.midwest.rr.com [24.164.235.113]
4 12 ms 11 ms 11 ms be41.milzwift01r.midwest.rr.com [65.31.113.76]
5 15 ms 15 ms 14 ms bu-ether18.chctilwc00w-bcr00.tbone.rr.com [66.109.6.206]
6 14 ms 15 ms 15 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
7 12 ms 13 ms 12 ms 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
8 15 ms 12 ms 12 ms te0-1-0-22.ccr41.ord03.atlas.cogentco.com [154.54.11.145]
9 14 ms 16 ms 13 ms be2216.ccr41.ord01.atlas.cogentco.com [154.54.24.201]
10 31 ms 21 ms 21 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
11 44 ms 48 ms 45 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
12 48 ms 48 ms 50 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
13 48 ms 48 ms 47 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
14 41 ms 43 ms 40 ms 38.111.40.114
15 41 ms 41 ms 41 ms 198.49.243.253
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 47 ms 142 ms 115 ms patchserverrebirth.crypticstudios.com [208.95.18
5.41]
Trace complete.
Seems not fixed to me.....
Seriously though, many online retailers and service providers sign a contract with their ISPs which do in fact guarantee a typical uptime, anywhere from 95-99%.
If leverage can't be found from competition, there are other negotiable things that can be considered. At this point, most players that have been affected by more than 5% downtime would really appreciate some sort of tangible good-will gesture from PWE, not silence.
D&D Home Page - What Class Are You? - Build A Character - D&D Compendium
C:\Users\Admin>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 2 ms 1 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 34 ms 26 ms 13 ms 10.162.11.21
5 70 ms 74 ms 71 ms 10.162.11.9
6 85 ms 79 ms * 200.79.231.81.static.cableonline.com.mx [200.79.
231.81]
7 79 ms 109 ms 80 ms 10.19.132.17
8 95 ms 88 ms 117 ms 63.245.6.137
9 * 134 ms 152 ms xe-10-2-3.edge2.Miami1.Level3.net [4.31.223.77]
10 128 ms 132 ms 121 ms ae-1-51.edge1.Miami2.Level3.net [4.69.138.75]
11 122 ms 128 ms 112 ms francetelecom-level3-ge.Atlanta1.Level3.net [4.6
8.110.170]
12 * 148 ms 136 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80
.41]
13 128 ms 258 ms 124 ms be2122.ccr41.atl01.atlas.cogentco.com [154.54.24
.193]
14 161 ms 169 ms 126 ms be2112.ccr41.dca01.atlas.cogentco.com [154.54.7.
157]
15 147 ms 135 ms 138 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
16 175 ms 177 ms 161 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
17 135 ms 151 ms 165 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
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.
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]