{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/7/2018 7:01:50 PM
56
-
Investigate harder then this game is practically unplayable
-
Investigating? Or just hoping and praying it will go away on its own? 4+ DAYS NOW.
-
when is this getting fixed
-
Editado por Sergeant_SLY: 12/11/2018 2:12:34 AMNow now... @BNGHelp1 is very very busy investigating the issue >>> http://prntscr.com/ltc34z
-
[quote]Hello, We are investigating this issue.[/quote] loading... ..... ..... ..... .... zzzzzz
-
[quote]Hello, We are investigating this issue.[/quote] I was temporarily suspended from competitive crucible because of this issue and can’t partake in any team activities as it happens more frequently
-
I had to stop playing. I'm in NH and constantly getting kicked for error codes. Trying to level up to do the raid is next to impossible because of this problem. I do have comcast but dont believe this to be a comcast issue. when we gonna get some relief here. Was fine till the recent updates.
-
WHO DO I COMPLAIN TO ABOUT LOSING GLORY POINTS BECAUSE I GOT DISCONNECTED TWICE, (ONCE WHILE WE WERE AHEAD), DURING COMP MATCHES???
-
So any statement as to why this is happening or how this is going to be a fix for the future OR HOW PPL CANT DO THE NEW RAID AT ALL DUE TO BEING KICKED OUT IS BEING ADDRESSED
-
Fix it already! “We are investigating the issue” ffs fix this bullshit already, there’s no reason you should be investigating, you should be fixing!!!!
-
m UK and thank gawd lucky up to now (touch wood) but, my buddy is MA and had probs since this new dlc dropped... it really is BS... He left behind unable level up etc. not even acknowledge by bungie really... the game has issues anyway and currently lots broken but, this... this... not even acknowledging a problem making people think going crazy and leaving them in dark, unable to level up for a dlc they paid for... no wonder people leave and dont come back... you need help your CUSTOMERS... Come on bungo if it was Tess at Eververse you be patched up in mins... but, what players dont matter ??
-
Bungie while your at it can you return our glory points for the two matches we lost and got suspended for due to your GRAPE issue? That’d be great, thanks
-
So when do we get a real response and not this generic one?
-
It is almost a joke now. I keep seeing the same response and then i see a new response from a moderator with a link to this one. I'm thinking "yay some info on what is going on" and then it loads and i see the same response. lol.
-
Damn, let them finish tweeting about worlds first and fixing blind well matchmaking, first! Theyll get on it after their morning coffee on monday.
-
Don't doubt it. Maybe I'll be able to load into the Tower first try sometime in early 2019.
-
Hey, so this problem seems to only be effecting Comcast customers, specifically those who route through the Boston hub. The source of the problem is almost certainly in Comcast's internal network. Users on the PC side can temporarily work around the issue with a VPN, on the console side you can tether to your phone's wifi hotspot if your data plan can handle it! Bungie may be able to fix the issue with a patch, but the cause of the problem is almost assuredly an incorrectly configured interconnect in Comcast's network.
-
It’s definitely not Comcast. I have set up a port forward. I fully reconfigured my wireless network and got a new router. I have NEVER had an issue with my set up until this week. It’s not Comcast. This is a Bungie problem.
-
Unfortunately it’s not on Comcast, I’ve troubleshot everything on their end that I can. I also have 0 problems with any other game across any other console I own, this is solely on Bungie’s side.
-
The issue popped up as soon as they fixed the Blind Well glitch. Since that was fixed the Northeast has been left with an unplayable game. As for this whole “it’s on Comcast” thing, it’s not. I spent yesterday morning on the phone with them, moving up the line of tech support until they finally hard reset my entire modem on their end and forced an update. Everything else about my internet is flawless. Comcast may SEEM to be the problem because everyone with the issue says they have Comcast, but that’s literally because they are the main service provider in this area. 90% or more of the Northeast uses Comcast, with a few on Frontier and Verizon (both of which have users suffering the exact same issue). This issue is 100% on Bungie, and they need to fix it ASAP and even find a way to compensate those of us that have been left with an unplayable game for 4+ days now.
-
Preach brother, preach! I've been constantly suspended from competitive matches as of late because of the fact that I kept getting error codes either during matchmaking or during the game itself. People like me who have lost progress with glory ranking and all the others who have lost out on countless opportunities in the game, be it with the raid or grinding, are honestly obligated by Bungie, in a sense, to be compensated.
-
I'd buy that if [b]everything[/b] else didn't work flawlessly...
-
The problem is literally only effecting Comcast customers who route through the Boston PoP. The problem is 100% on Comcast's side. Bungie may have changed something about how the game communicates in the recent patch (though I doubt it, errors didn't start showing up for me until Wednesday at the earliest), but if it's only effecting Comcast customers routing through Boston (and it is), the simplest explanation is that Comcast has an incorrectly configured (or malfunctioning) piece of equipment at that location.
-
I dont rout threw boston. I still got problems. Im in Plymouth county.
-
It's adorable that you think you know with certainty who it is "literally" only affecting. Awfully strong opinions for someone not actually involved. Opinions that magically become fact.
