{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/12/2018 6:54:25 PM
18
Unless you live in New England where most of us went 6 days with “we’re investigating” then all of a sudden streamers and more people lose access and it’s miraculously fixed in a couple hours. Biggest slap in the face to every Destiny player in New England was how fast they fixed it once the problem scaled to the streamer level.
English
-
Lol, always comes back to the streamers huh?
-
Yea I agree with that I live in New England and I’m a non streamer and it was annoying trying to even go into the tower let alone do my milestones.
-
My heart goes out, man. Las Vegas area went down for a good four days right as the Festival of the Lost was going to end. All I wanted to do was log in and drop bright dust on the Black Cat Shell and couldn't do it. Happily the issue resolved riiight before Reset/Festival end, but it was extremely irritating.
-
Ahhh that is frustrating. Sorry to hear that.
-
That must have sucked. I just heard the complaints and when I got home from work, everything worked fine.
-
Edited by dblbkflp: 12/12/2018 8:19:58 PMI love in New England and hd no issues other than yesterday. What was going on? Ah i see, i do not have comcast.
-
You were one of the lucky ones! Basically the same issues as yesterday, just dating back to last week when BA launched.
-
I think it had fvck all to do with streamers and that's all a coincidence, because any NE streamer would have been affected like everybody else in that area at the same time. From everything I was seeing, only Comcast customers were being affected, which it should have been obvious after hundreds of "Comcast customer here..." comments. So it wasn't Bungie's complete fault probably and makes sense because all they could say was "we're investigating". That usually means they don't know where or what the cause is. My guess is Comcast messed something up and Bungie's investigating was more or less sitting on phone calls/emails with Comcast techs waiting for answers from them. Then out of the blue some tech(s) solved the problem and it took a few hours to propagate across the NE.
-
Maybe. But it’s wildly coincidental that the issue was resolved as soon as it got widespread attention...Comcast or not. Must have just been some form of miracle...
-
Edited by GrundleBeans: 12/12/2018 8:12:09 PMI'm pretty sure there was already widespread attention for days. I still swear every other person I saw on here complaining that was in the NE were all saying they were Comcast customers and not a single one ever said anything like "hey, I wonder if this has to do with Comcast more than Bungie..." Just a thought.
-
When destiny is the only thing that doesn't work rite, it's hard to blame your internet provider. My understanding is comcast customers could access other games, go online, etc., but destiny crashed, kicked them, or "animal" error.
-
No, it was not only Destiny. If you read further, someone else pointed out that other companies/services were also being affected.
-
Only going by a friend who has comcast. He says this has happened before when a big destiny or playstation update has hit. He mentioned a ps4 problem about a year ago with comcast.
-
That was my original thought as a Comcast customer, I wouldn’t have been surprised if it was them. But I play with other friends in the region that have Verizon, and other providers that had the same issues. Comcast just has a huge market share up here hence most posts stating Comcast. Either way, we’ll never know the real reason. Just very peculiar how quickly the issue was fixed once it went global and videos started popping up on YouTube about it. That’s my sole observation.
-
Edited by GrundleBeans: 12/12/2018 8:26:35 PMSome ISPs, especially in different areas, share infrastructure where cables are laid. It wouldn't surprise me in some parts if multiple ISPs were having the same issue (like a blackout), but I thought it was obvious Comcast was the primary source of the problem when a) everyone in an isolated region of the US were all having the same issue and b) 99%+ are using the same ISP. It might have involved Bungie regional servers as well, but it still points to Comcast being a blocker to the fix. [quote]videos started popping up on YouTube about it.[/quote] I think it's merely coincidence that you think YouTubers had anything to do with Bungie taking action when really it makes sense YouTubers start reporting on it only after it had become an issue for more than a couple days. So videos would only add a bit more fuel to the PR fire at the tail end, not be the start of it. And it was very clear from the dozens of Bungie staff posts that they were aware of the issue and trying to find a fix the entire time.
-
Another user provided a bit of incite in another post, if I find it again, I'll edit it into this post. The gist was that while it was mostly Comcast customers affected, there were others. Here's the rub though, it was an interchange company called Level 3 that was having issue apparently. Neither Comcast nor Bungie could really do anything to fix the problem from the sounds of it.
-
Edited by GrundleBeans: 12/12/2018 8:45:27 PMThat clears things up. So essentially there was a middle-man that was affecting outgoing connections to Destiny and incoming connections from Destiny to mostly Comcast customers in the NE region. It really had nothing to do with Bungie, but I can see how during the investigation they didn't know that it was Level 3 until days into it so they couldn't really tell us if they knew anything until maybe hours before they figured out the problem. Not to defend Bungie cause they still could have done a better job trying to inform, but goes to show people here will jump to blame Bungie about any problem first and foremost without patience or understanding.
-
Edited by toneDef Weary: 12/12/2018 8:51:57 PMI'm definitely the type to lay blame where it is due, but I also try not to place blame where it doesn't belong. Some just don't have that same level of patience as us. Here's that comment by the way, I put it as a spoiler as it's a tad long. [spoiler]sporks (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[/spoiler] And here is the topic it came from. [url]https://www.bungie.net/en/Forums/Post/250094365?sort=0&page=0[/url]
