Not really seeing as it's only affecting a small minority of players. They know about it, but they need to find that 1 thing in common with you guys, so they know whats wrong. They cant just say "ok, we fixed it" within a day or two. it takes time to track the problem down, work on a fix and push it to live, knowing there will be no further problems.

there are more then this thread expressing the issue...i think it is more then you think.
and yes, while i understand they are working on it, if not one says anything, then they think its all hunky dorey..and it is not. more so this close to launch.

edit: ok this is BS....three times in a row now while trying to access either a system or the bridge...ugh!

It seems to occur more on multipart missions which culminate in beaming down somewhere. I've also observed that it seems to occur more frequently when you are part of a team, disconnecting both players.

this getting worse for the first week and half of open beta i never experienced this error but the last three days been getting more frequently today so much so i wasn't able to log in for the final event.

This just happened at a very inopportune time...just finished that gawdawful mission in the artificial wormhole made by the Hirogen...was finally about to escape, it does the warp animation....and then the loading screen goes to the game server not responding error and kicks me out. Come ON, now....how did we go from this never happening during closed beta or even the early, massively over-populated parts of open beta, and now a few days before launch it's happening almost constantly? I've been holding back my complaints somewhat, but this total lockout for five or ten minutes (if you're lucky) is a serious showstopper. Can we get some Dev love, please? At least tell us you're looking into it?

This just happened at a very inopportune time...just finished that gawdawful mission in the artificial wormhole made by the Hirogen...was finally about to escape, it does the warp animation....and then the loading screen goes to the game server not responding error and kicks me out. Come ON, now....how did we go from this never happening during closed beta or even the early, massively over-populated parts of open beta, and now a few days before launch it's happening almost constantly? I've been holding back my complaints somewhat, but this total lockout for five or ten minutes (if you're lucky) is a serious showstopper. Can we get some Dev love, please? At least tell us you're looking into it?