I'm in FL 4 errors since I started playing this morning. 2 guitar errors, 1 something berry, and don't remember the other one.

I’m in Texas and can’t play at all. I played 2 crucible matches and they didn’t count towards milestone or bounties. Seems it’s not just the NE.

In Texas, same here.

[quote]I'm part of the NE outage but I was still able to connect and play quite a bit. Now I cannot even log in or load anything. Started being worse immediately after dawning update. Honestly what does it take for Bungie to fix an issue? People have been reporting this for 5 days now. It's clearly a major issue, assign more people to it and figure it out so the NE gamers can grind with everyone else![/quote] Im getting them here in Central Washington. What's up?

I'm not affiliated with Bungie or Comcast, nor am I located in the New England area, but I feel like I should pass along what I know about the situation. I'm a systems and network administrator for a completely unrelated SaaS company, but our customers in the New England area who are using Comcast have been having some serious issues with our services since the evening of December 6th. From what I can gather, the timing lines up with when Destiny 2 players in the northeast started having issues. We have a much smaller user-base, with only hundreds of thousands of users, but there's a small percentage of our users having nagging intermittent issues with our services. Most are in the Northeast, and most have Comcast, but all of them have one single thing in common -- their network traffic is heading towards our datacenters via a handoff with Level3 in Boston. The vast majority of them use Comcast in the Northeast, but we've observed identical issues from other ISPs in the area (notably Cox), as well as from other areas (some in Virginia, to as far away as Florida)... but, again, in 100% of the instances since 12/6, their traffic was headed towards our datacenters via Level3 in Boston. So, I can't speak for Comcast, nor for Bungie, but from my perspective there appears to be an issue with Comcast's (and others') handoff to Level3 in Boston. If that's the case, it's largely out of Bungie's hands, and possibly not even something that Comcast can play a part in fixing (though Comcast should be better about picking up on stuff like this, and sending it up the chain). We've been attempting to work with our largest customers in the Northeast to communicate with Comcast, as it's impossible for us to communicate directly with them, but they're being expectedly pigheaded about the whole issue. I feel for you guys, since Bungie isn't being overly forthcoming about the issues. But, as a service provider, I can relate with them as well... there's often very little that can be done from our end in such situations. This is something that happens quite often -- typically not for such an extended period of time, but it's definitely not unheard of. All I can really say is, direct your anger towards something useful. In this specific case (not considering any other issues that Bungie may or may not have), there's probably nothing that Bungie can do, so don't get on their case too hard :) -AW

Same thing in getting in FL