This is the last report on this post for now. After the update this week, CABBAGE and LETTUCE seem to have completely stopped on my end so far. This still leaves me very skeptical about the updates. And last week was Iron Banner and I usually see errors become more of a problem during that event too. I'm also not noticing any other errors either when the servers warmed up after the emergency maintenance. I do hear that some other players are still getting these errors, but I haven't seen anything on me or any of my friends' ends so far. We're all good right now. EDIT: Scratch that, I just got KALE in the Crucible a moment ago. I don't normally see that one. EDIT 2: This comment was made a couple of weeks ago and not long after I said this, CABBAGE returned but not LETTUCE.

I have another update on this subject again. I don't really have a reason to make another post because I'm not actually experiencing that many problems right now, so I figured I'd say this here. I'm not sure what all happened during the last maintenance, but CABBAGE and LETTUCE have seemingly stopped on my end again. I have not touched or changed anything involving my internet since I last posted about this. All of the information I've provided is still the same. I still use Spectrum. I've checked the forums and other players are still reporting these errors, some of them also using Spectrum. I've seen an odd in-game effect though. Normally with these errors when they're about to happen, enemies/objects/entities do not fully load into an area. Well right now, I've seen that happen a couple of times for a few seconds but then everything actually successfully loaded in, no errors. After this happens, the instance seems to become pretty laggy like it's just a general connection issue with the servers (still only tied to this one game). In PvE, enemies sometimes don't notice me right away and if I kill them, over half the time they just reappear with partial damage. In PvP, some matches have somewhat-late damage registration, like general latency. All of this seems to only happen when other players are in the same instance and it is still a random occurrence. Considering the rate that this in-game issue happens and when it does, that is what leaves me to believe that this is happening in place of the error codes right now. The only odd things are that other players have to be around for it to happen and it still looks like the errors are about to happen when they don't. The game is a lot more playable right now though, so I'm not too bothered by it. This is the first time I saw these errors change in behavior after just a maintenance rather than a patch. Needless to say, I'm still very confused and skeptical. I have recorded a video of the in-game effects and after looking at it and thinking about the maintenance, now I'm thinking it's just a server issue, not an in-game loading issue. I don't have the video uploaded anywhere yet, but let me know if you'd like a link to it.

Well I've already been messing around with the router's settings. I'm no expert on them and looking around in there was a nightmare. But from what I saw, if there's anything close to a firewall on it, the closest thing would be the network password, which I don't know a single person personally who doesn't use a password, even some other people who play the game with the same ISP. And even if that is some firewall issue, there's not really much I can do about it, especially in my area. I'd rather not get hacked or something else depressing. Like I've been saying, it's only this one game. Other online games like fighting games, Halo, Minecraft, etc work fine. So it's kind of a shame if the servers are just getting that strict as of late. I do understand if maybe some changes had to be made when Cross-Save and free-to-play started to come out (I wouldn't know what changes exactly), but if that's the case, it's impacted many others negatively, even to the point of not being able to play the game at all. You don't even see some of those users on the forums anymore. Well, tomorrow is an update, right? Usually I see the errors change in behavior in some way after an update (not a maintenance), so some point later in the week if it gets better, I'll post back here about it just in case.

I have a friend that also has Spectrum and he went and got his own router to use too. Unfortunately for him, he also gets these errors anyways. I doubt what we have is a router issue. I talked to him about some of the information that was passed around in this post a couple of hours ago. Still can't come up with anything consistent that could be a cause for these errors and I still have some more things to look into.