So, I've posted before about connection issues. They eventually resolved themselves, and the game has been running pretty flawlessly, until the weekly reset this week (1/9). It started with bee, then after awhile, straight out to the title screen with weasel. I would keep getting bee every 5 minutes or so before booting me all the way out. Same thing last night (1/10), with a mix of Baboon thrown in for good measure. Tonight (1/11) it has been anteater and weasel (no bee or baboon). First question, do the error codes actually matter, or is it just a way to get us running around in the "troubleshooting guide" chasing after different error codes that are all caused by the same type of error? Second question, I received the Alexa ghost speaker as a Christmas gift. Again, working flawlessly until the reset. Whenever I get an error code in game, the lights on my ghost turn on, and stay on. Even if I exit the game, so I end up having to unplug and replug him in. Then he's fine, until the next drop from the game. He doesn't say anything, and it doesn't affect any other Alexa functionally. It's just weird that it happens at the exact same time that I get an error code and am booted from the game. Could the 2 be related? I get errors in game without my ghost bugging out, but it seems to only bug out when I get error codes. Yes, I've gone through the troubleshooting guide. My husband (a networking and software engineer) did a network capture last night and didn't see an increase in lag or lattency and no sudden packet loss before the Bungie servers dropped me. Good up and down speeds as well. Any additional help beyond a link to the troubleshooting guide, and "its not Bungie, it's you" is appreciated. I'm not blaming Bungie. It could very well be an issue with a peering partner or transit provider. But from what we could tell from the capture last night, it looks like my connection is stable.