JavaScript is required to use Bungie.net

토론장

원본 게시물 출처: Findings on New England Outage
12/12/2018 5:15:42 PM
4
(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
English

게시물 작성 언어:

 

다른 사용자들을 존중해주세요. 게시물을 제출하기 전에 한 숨 돌리고 운영 정책을 검토하세요. 취소 수정 화력팀 생성하기 게시

  • Thanks for the explanation, I live in the New England area and this clears things up for me, cheers mate

    게시물 작성 언어:

     

    다른 사용자들을 존중해주세요. 게시물을 제출하기 전에 한 숨 돌리고 운영 정책을 검토하세요. 취소 수정 화력팀 생성하기 게시

  • They fixed yesthurday. Just in time to rob more players in the dawning. Coincidence, not at all !

    게시물 작성 언어:

     

    다른 사용자들을 존중해주세요. 게시물을 제출하기 전에 한 숨 돌리고 운영 정책을 검토하세요. 취소 수정 화력팀 생성하기 게시

  • Glad to hear that things have cleared up for you folks! :) I was still seeing quite a few mentions of Comcast-esque issues from the Northeast, so I was just assuming that the problems were ongoing. Interestingly enough, now that you mention it, I don't believe we've gotten any [b]new[/b] reports of issues from our side today yet, either... ¯\_(ツ)_/¯

    게시물 작성 언어:

     

    다른 사용자들을 존중해주세요. 게시물을 제출하기 전에 한 숨 돌리고 운영 정책을 검토하세요. 취소 수정 화력팀 생성하기 게시

  • It still sucks that it took them so long, i still have lag issues but no more error codes. Worst part is how i missed a whole week of milestones.

    게시물 작성 언어:

     

    다른 사용자들을 존중해주세요. 게시물을 제출하기 전에 한 숨 돌리고 운영 정책을 검토하세요. 취소 수정 화력팀 생성하기 게시

회원님은 해당 콘텐츠를 볼 수 없습니다.
;
preload icon
preload icon
preload icon