This is another example of blaming the community for their problems. The way I'm perceiving this issue is someone on the prod support team patched a 3rd party framework and didn't have an image to roll back to (or the team continued to make updates reliant on this update) so there isn't a way for them to fix it without putting in a ton of time. I'm seriously disappointed in how terrible communication of this issue has been. It's widespread and they have done little to nothing to address the issue other than half-assed reposting from diligent community members trying to alleviate the pain of hard resetting their consoles or resetting their MAC addresses or turning off NAT accelerating. Your community loves you more than you deserve right now. Show us that you're actually on the issue Bungie. Admit you messed up and share your gameplan for getting this fixed.