This was Eriena's reply to a similar thread: [quote]Bungie are aware of users getting Error code Beaver and are investigating. Stand by for updates. [url=https://twitter.com/bungiehelp/status/758019356055867392]@Bungiehelp[/url] [quote]We continue to investigate issues causing an increase in BEAVER errors. To potentially reduce this issue, please see https://www.bungie.net/en/Forums/Post/209806134[/quote] [url=https://twitter.com/bungiehelp/status/758087949464371202]@Bungiehelp[/url] For further information you can also view Cozmos reply [url=https://www.bungie.net/en/Forum/Post/209860825/0/0/1]Here[/url] [quote]It's us. Sorry if it wasn't made clear, but the issue with Beaver error codes was introduced in 2.3.1 and is definitely on our end. We offered up some advice on NAT tweaks as a way of possibly alleviating the issue while we work on a fix, but please don't interpret that as us passing the blame. Sorry for inconvenience, as soon as we have more info for you we will update this thread.[/quote][/quote] TL;DR: Bungie saw the problem and it's their fault from the patch. They're trying to fix it There you have it, the only definitive answer we have so far.