(Sorry for the cross post from another thread, but here goes...) 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

I live in new england and I haven't actually had any problems with this.

They are working with them but this problem lies with Comcast and it has already been determined as thus. Comcast is more than likely purging and blocking P2P traffic (especially with the repeal of NN) and that is what is causing problems here as that is the basis of Destiny's network architecture. It's easy to see it's Comcast's problem because I have a friend in MA that have Comcast. They cannot get on. BUT if they use either a wireless hotspot or the one is using a GSM hotspot from his work, and the other took his console into work where they do not have Comcast and are able to connect fine. Comcast will say, "No we are not throttling P2P!" But i caught them in Tucson at my other home doing the EXACT thing and tested, proved to them that they were and they finally admitted they were trying out new architecture to block P2P traffic (to limit people from file sharing/torrenting). I have this distinct impression they are trying it out in different areas slowly but will eventually fully implement this. And sadly, there is nothing Bungie can do about it.

In other news Tom Brady just deflated the internet users around the world and this is what Tom Brady had to say"Bill Belichick put me up to it,"but Whether we wanted it or not, we've stepped into a war with the Cabal on Mars. So let's get to taking out their command, one by one. Valus Ta'aurc. From what I can gather, he commands the Siege Dancers from an Imperial Land Tank just outside of Rubicon. He's well protected, but with the right team, we can punch through those defenses, take this beast out, and break their grip on Freehold.

Just adding my name to the list. From my gamertag you can figure out where I live. The error codes for me are most pervasive in the Forge content {I get kicked just trying to go to EDZ or Nessus) and in trying to join fireteams with friends or LFG to do anything else. Gave up last night trying to play with friends. I do manage to play other parts of the game with randoms, i.e., strikes, Gambit, etc., with only an occasional kick. After several kicks did manage to complete Gofannon with randoms. Verizon strung fiber behind my place last week getting ready to offer FIOS. Hurry up Verizon!

Only workaround I've heard so far is by using a VPN (some are free), but I'm not exactly sure how they work with consoles. Might be worth a shot though. [i](Someone said it fixed the issue for them, not sure if they were on PC or console)[/i] EDIT : Got VPN to connect with no issues > https://www.bungie.net/en/Forums/Post/250083327?sort=0&page=0 Got VPN to connect with no issues > https://www.bungie.net/en/Forums/Post/250063772?sort=0&page=0&path=1 Got VPN to connect with no issues > https://www.bungie.net/en/Forums/Post/250038294?sort=0&page=0

I’m from New England with Comcast/Xfinity and have also experienced error codes daily in the past week since Black Armory. I lost streaks, forge rewards, and couldn’t do the raid this week because of it.

I would suggest QUIT playing this game. Its the best thing you will ever do in your entire gaming experience.

My dlc is gone when I was able to get on. Like, it says that I don't even own it. My friend gifted me the doc a few months back and I got to 400 light level but its just gone. Should I go straight to Microsoft support or wait it out?