Hey folks! I just got an update. It's not what we want to hear but at least it means they have found the issue! The connection issue has been pinpointed to being an issue on the Internet Service Provider that the Cryptic Servers connect to and through. Alas, this means the Tech Team and Developers cannot resolve the issue, so we are now waiting for our ISP to correct the issue. We do apologize it has taken so long to find the cause but at least now the wheels are in motion to get this resolved.
Thanks for the update Zebular- nice to know what the issue is precisely and that there is a solution in the works. I've had too much time to do stuff around the house on my day off, ha ha ha...
yay it just started working for me on Xbox again, I have been trying VPN stuff with no success and it looks like its fixed now (it was working also this morning but stopped again after a few hours). Hopefully it stays working
Hey folks! I just got an update. It's not what we want to hear but at least it means they have found the issue! The connection issue has been pinpointed to being an issue on the Internet Service Provider that the Cryptic Servers connect to and through. Alas, this means the Tech Team and Developers cannot resolve the issue, so we are now waiting for our ISP to correct the issue. We do apologize it has taken so long to find the cause but at least now the wheels are in motion to get this resolved.
Zebular - was there and estimate given by your ISP on resolution of the aformentioned issue.
Q
Sorry, nay I haven't been told any ETA yet. When we get word, we'll update here and in the Sticky asap.
I've been browsing the Comcast forums for the same issues; I'm seeing the same problems, but from 2013. x_x So, hopefully, Cogent and Comcast will (eventually) fix the problems.
My pleasure! Just wish is was better news.
Zeb can you let them know that they still need to fix the giant HAMSTER of a client they just gave us for the weekend also? I mean it doesn't take rocket science to see that the UI is now riddled with memory leaks and is affecting literally every single user over time. Hell I wouldn't be surprised if your ISP issue is related to all of your customers constantly relaunching the game 3 times an hour to refresh their UI and FPS.
Basic infrastructure design requires at LEAST 2 different Internet providers that use distinct tier 1 networks so that outages like this can be prevented or at the very least, heavily mitigated. Seems this basic design wasn't followed, so here we are. And Cryptic blames their ISP? No! I blame bad network design.
Oh and btw, back down we go, no Neverwinter for me again got about 2 hours of fun in for a sunday. If only I could invoke via the gateway...oh wait gateway is down too sigh. They need to pay for better ISP this is ridiculous. How do they not have major sway with their ISP. I bet this is magically fixed September 1st when their bandwidth meter resets and their ISP stops throttling them.
In all seriousness, I hope that the double RP weekend ALSO counts as a double AD weekend or something, to compensate us for lost time :P
This isn't a Comcast problem though. If you do a search for "Cogent" on the STO forums you'll see there have been problems with them for years.
It is past time Cryptic found a new ISP, if another is available.
Now there may be something screwy with a connection between Comcast and Cogent but it's not on Comcast's end. Comcast techs have traced the problem to outside their network, in this case to Cogent, like usual.
This is nothing new unfortunately. If you're new to Cryptic games you'd best get used to this because come November or December it will happen again. It always does.
In all seriousness, I hope that the double RP weekend ALSO counts as a double AD weekend or something, to compensate us for lost time :P
This isn't a Comcast problem though. If you do a search for "Cogent" on the STO forums you'll see there have been problems with them for years.
It is past time Cryptic found a new ISP, if another is available.
Now there may be something screwy with a connection between Comcast and Cogent but it's not on Comcast's end. Comcast techs have traced the problem to outside their network, in this case to Cogent, like usual.
This is nothing new unfortunately. If you're new to Cryptic games you'd best get used to this because come November or December it will happen again. It always does.
Im not an expert on internet backbone hubs and stuff,, but when it comes to this page im thinking 0's across the board is BAD! Found another page that showed every major city across the world screaming in the RED showing " attacks" on the net... wasn't any other details,, so im not sure how to interpret that,, but I think something bigger is going on than just a server farm in boston have ISP issues. Strange that Netflix seems to working perfectly though.
Performing a traceroute to various locations using Cogent's looking glass tool doesn't reveal anything (using the Boston CoLo as the source), and Cogent's network status report is normal. Hmm...
BTW - we've been tracking this problem over in the STO forums as well. It seems to be peering points with Cogent that's the problem, not other ISPs. Definitely a lot of issues with Comcast -> Cogent links, but certain routes are fine.
I'm also seeing issues with various VPNs on the US east coast that don't touch Comcast's network. Some other VPN Tunnels are fine.
Cogent needs to be your previous provider, seriously what kind of idiots take 3 days to identify a problem? And then can't fix it once they find it...they may be cheap, but this weekend showed the true cost. Wake up!
I'm sticking with my new theory, and I'm already 1 for 1 on theories this weekend. Its the end of the month and they are dangerously close to overage charges on bandwidth so they are cycling their users off. I was finally able to get on earlier after leaving the launcher open waiting, and when I went afk the lag had returned after attempting to relogin. Smells very much of throttling. I will be right when September 1st creeps around and the problem is gone
Well after the ISP update thing you guys posted I was able to play for a good 30 mins. Started to have problems with the game, when the skirmish was about to be over... poof. Disconnected from server.
zebularMember, Neverwinter Moderator, NW M9 PlaytestPosts: 15,270Community Moderator
edited August 2015
Even if switching providers was an option, that wouldn't necessarily fix anything. Such could make it even worse. As well, it doesn't matter what provider one uses, users will still be going through networks such as Cogent, Comcast, AT&T, etc, etc. That's how the internet works. The internet is not a straight line and you don't stay on "your" network connecting around the World. The whole "Net Neutrality" movement enlightened and taught a lot of users how the internet works and these sorts of issues just continue to do that, which is a good thing even if it is horrible to experience.
The more people to learn, understand, and experience how the internet works means that the future will hopefully be a better place as such experiences drive our youth to imagine and create a better world. Alas, right now we are subject to a fickle internet ruled by a monopoly of agencies and corporations. Eeks, sounds like I may need to invest in some tin foil, sorry for that rant!
Ugh, I had to do something social because I could not play your game. Oh, well. I'll live.
Good luck with all this. I'm sure it will get better.
0
zebularMember, Neverwinter Moderator, NW M9 PlaytestPosts: 15,270Community Moderator
edited August 2015
Update, 2015-08-30 @ 6:20pm PDT:
Alas, we don't have any news to deliver as of yet. We're still waiting for a response from Cogentco, where the issue is. So, there is not much that can be done until then. We'll continue to update the Sticky and this thread as we have more information.
Tracing route to patchserver.crypticstudios.com [208.95.185.41] over a maximum of 30 hops: 3 9 ms 9 ms 10 ms ge-6-2-sr01.millersburg.pa.panjde.comcast.net [6 8.86.214.73] 4 10 ms 18 ms 14 ms be-23-ar03.norristown.pa.panjde.comcast.net [69. 139.192.101] 5 44 ms 27 ms 13 ms he-0-10-0-1-ar03.newcastle.de.panjde.comcast.net [68.85.159.229] 6 17 ms 15 ms 16 ms be-33287-cr02.newyork.ny.ibone.comcast.net [68.8 6.93.173] 7 34 ms 48 ms 34 ms be-10305-cr02.350ecermak.il.ibone.comcast.net [6 8.86.85.202] 8 35 ms 34 ms 35 ms be-10506-cr01.350ecermak.il.ibone.comcast.net [6 8.86.86.230] 9 60 ms 60 ms 61 ms be-11317-cr02.denver.co.ibone.comcast.net [68.86 .84.230] 10 56 ms 57 ms 57 ms ae-15-0-pe01.910fifteenth.co.ibone.comcast.net [ 68.86.84.118] 11 56 ms 59 ms 59 ms te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.c om [154.54.10.33] 12 59 ms 57 ms 56 ms te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54 .83.33] 13 70 ms 64 ms 72 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26 .122] 14 65 ms 61 ms 62 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6. 118] 15 79 ms 67 ms 65 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43 .178] 16 65 ms 68 ms 62 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43 .185] 17 62 ms 65 ms 61 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43 .13] 18 72 ms 62 ms 63 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c om [154.54.46.130] 19 62 ms 61 ms 70 ms 38.111.40.114 20 61 ms 64 ms 69 ms 198.49.243.253 21 * * * Request timed out. 22 65 ms 71 ms 66 ms xboxpatchserver.crypticstudios.com [208.95.185.4 1]
> @zebular said: > Even if switching providers was an option, that wouldn't necessarily fix anything. Such could make it even worse. As well, it doesn't matter what provider one uses, users will still be going through networks such as Cogent, Comcast, AT&T, etc, etc. That's how the internet works. The internet is not a straight line and you don't stay on "your" network connecting around the World. The whole "Net Neutrality" movement enlightened and taught a lot of users how the internet works and these sorts of issues just continue to do that, which is a good thing even if it is horrible to experience. > > The more people to learn, understand, and experience how the internet works means that the future will hopefully be a better place as such experiences drive our youth to imagine and create a better world. Alas, right now we are subject to a fickle internet ruled by a monopoly of agencies and corporations. Eeks, sounds like I may need to invest in some tin foil, sorry for that rant!
Well this is partly true... Most the datacenters I work with have no less than 3 ISPs and redundant hot and cold sites for exactly this type of issue. Your head node should always be dynamic so in the case of a bad external network route, or ISP outage, you can redirect your users to a working node.
Failover and redundancy are #1 anytime you are hosting systems. My clients would kill me if I bound them to a single ISP and had a connection mess like this. Even simple DNS redirection to a different circuit would be better than what has happened. Yes DNS takes time to propagate, but with a short TTL, it probably would have been up sooner than what we are seeing now. Many applications even test multiple routes for the fastest and more reliable route before establishing a connection.
I don't mean to directly disagree, but there are more facts than what had been posted.
Additionally, Cogent has always been the low cost provider who has had to beg, borrow and steal in the past to get carrier agreements. I know that has changed recently, but for my clients with Cogent, I always recommend a more reliable backup circuit.
Comments
It is past time Cryptic found a new ISP, if another is available.
Now there may be something screwy with a connection between Comcast and Cogent but it's not on Comcast's end. Comcast techs have traced the problem to outside their network, in this case to Cogent, like usual.
This is nothing new unfortunately. If you're new to Cryptic games you'd best get used to this because come November or December it will happen again. It always does.
Riker has NO CLASS
Delta Rising is the best expansion ever - Bombay style
http://www.internettrafficreport.com/namerica.htm
THis is the one that shows the ATTACK... if anything its got some HUGE numbers on it... Cyberattack?
https://www.akamai.com/us/en/solutions/intelligent-platform/visualizing-akamai/real-time-web-monitor.jsp
Fleet Admiral In charge of Bacon
Fighting 5th Attack Squadron
The Devils Henchman
I'm also seeing issues with various VPNs on the US east coast that don't touch Comcast's network. Some other VPN Tunnels are fine.
> worked for a little while and now back to server not responding
My exact experience as well.
The more people to learn, understand, and experience how the internet works means that the future will hopefully be a better place as such experiences drive our youth to imagine and create a better world. Alas, right now we are subject to a fickle internet ruled by a monopoly of agencies and corporations. Eeks, sounds like I may need to invest in some tin foil, sorry for that rant!
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]
Good luck with all this. I'm sure it will get better.
Alas, we don't have any news to deliver as of yet. We're still waiting for a response from Cogentco, where the issue is. So, there is not much that can be done until then. We'll continue to update the Sticky and this thread as we have more information.
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]
over a maximum of 30 hops:
3 9 ms 9 ms 10 ms ge-6-2-sr01.millersburg.pa.panjde.comcast.net [6
8.86.214.73]
4 10 ms 18 ms 14 ms be-23-ar03.norristown.pa.panjde.comcast.net [69.
139.192.101]
5 44 ms 27 ms 13 ms he-0-10-0-1-ar03.newcastle.de.panjde.comcast.net
[68.85.159.229]
6 17 ms 15 ms 16 ms be-33287-cr02.newyork.ny.ibone.comcast.net [68.8
6.93.173]
7 34 ms 48 ms 34 ms be-10305-cr02.350ecermak.il.ibone.comcast.net [6
8.86.85.202]
8 35 ms 34 ms 35 ms be-10506-cr01.350ecermak.il.ibone.comcast.net [6
8.86.86.230]
9 60 ms 60 ms 61 ms be-11317-cr02.denver.co.ibone.comcast.net [68.86
.84.230]
10 56 ms 57 ms 57 ms ae-15-0-pe01.910fifteenth.co.ibone.comcast.net [
68.86.84.118]
11 56 ms 59 ms 59 ms te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.c
om [154.54.10.33]
12 59 ms 57 ms 56 ms te0-1-0-3.ccr22.den01.atlas.cogentco.com [154.54
.83.33]
13 70 ms 64 ms 72 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26
.122]
14 65 ms 61 ms 62 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
15 79 ms 67 ms 65 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43
.178]
16 65 ms 68 ms 62 ms be2189.ccr22.alb02.atlas.cogentco.com [154.54.43
.185]
17 62 ms 65 ms 61 ms be2302.ccr22.bos01.atlas.cogentco.com [154.54.43
.13]
18 72 ms 62 ms 63 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
19 62 ms 61 ms 70 ms 38.111.40.114
20 61 ms 64 ms 69 ms 198.49.243.253
21 * * * Request timed out.
22 65 ms 71 ms 66 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]
Trace complete.
I'm just going to leave this here...
> Even if switching providers was an option, that wouldn't necessarily fix anything. Such could make it even worse. As well, it doesn't matter what provider one uses, users will still be going through networks such as Cogent, Comcast, AT&T, etc, etc. That's how the internet works. The internet is not a straight line and you don't stay on "your" network connecting around the World. The whole "Net Neutrality" movement enlightened and taught a lot of users how the internet works and these sorts of issues just continue to do that, which is a good thing even if it is horrible to experience.
>
> The more people to learn, understand, and experience how the internet works means that the future will hopefully be a better place as such experiences drive our youth to imagine and create a better world. Alas, right now we are subject to a fickle internet ruled by a monopoly of agencies and corporations. Eeks, sounds like I may need to invest in some tin foil, sorry for that rant!
Well this is partly true... Most the datacenters I work with have no less than 3 ISPs and redundant hot and cold sites for exactly this type of issue. Your head node should always be dynamic so in the case of a bad external network route, or ISP outage, you can redirect your users to a working node.
Failover and redundancy are #1 anytime you are hosting systems. My clients would kill me if I bound them to a single ISP and had a connection mess like this. Even simple DNS redirection to a different circuit would be better than what has happened. Yes DNS takes time to propagate, but with a short TTL, it probably would have been up sooner than what we are seeing now. Many applications even test multiple routes for the fastest and more reliable route before establishing a connection.
I don't mean to directly disagree, but there are more facts than what had been posted.
Additionally, Cogent has always been the low cost provider who has had to beg, borrow and steal in the past to get carrier agreements. I know that has changed recently, but for my clients with Cogent, I always recommend a more reliable backup circuit.