Normally with my group of friends that I play with on Destiny 2, it tends to be an inside joke when I get hit by error codes like CABBAGE or LETTUCE. No one else in this particular group tends to get hounded by as many error codes as I do. CURRANT happens here and there for all of us, mainly me but sometimes them too.
Throughout this week though, it's gotten bad. Now my friends who are normally not affected by some of these errors are getting them a lot, just like me. Reports have also gone up yet again. I think something about the event is still taking its toll on the servers and I'm worried about Iron Banner coming along as well next week. I think it's going to get bad.
The error codes that seem to be happening a lot with my group of friends include CURRANT, RABBIT and QUAIL. Normally for me, these errors are more rare than CABBAGE or LETTUCE, but I've seen them multiple times this week myself and my friends have been booted by them as well when they normally never see them.
The error codes that I'm surprised to see happening to a couple of other friends are CABBAGE and LETTUCE, because I've only met random players in the past that experienced these besides me.
The signs are pointing toward the servers. I know they use different ISPs and we're all experiencing similar things right now. And be ready for it to get worse because it will.
-
Same. Been getting currant and baboon errors. I've never had any issues with Destiny until this week, and everything else works fine on our home network. It started just having issues loading into the tower, but then I was kicked out of Sundial yesterday. Luckily, it put me back in.