Thank you for the fresh reports of this error impacting many public bounties & Rifts. It seems this error has resurfaced following the server hiccups last night and we’re investigating the cause. We’ll continue to share updates in this thread as they are available, and I am sorry for the disruption this causes in the meantime.
problems like this when everyone came back to diablo after years off because d4 is coming makes blizzard look really bad. huge lack of devs but some e mails should be going out for help from other areas of blizzard
If you think this is making Blizzard look bad, Just do a google search and take a look at the fecal storm that has been this company for the last year or so.
Awesome. Yeah, just came back today to check to see if I could get some bounties done but no go. Couldn’t yesterday. Bottlenecked at veiled crystals! But low on the others too.
You guys are testing hardware for D4, aren’t you? I mean that’s cool. Ish.
Hey there. I have been receiving 24004 also. I can start game solo, but when I try to join for rifts, bounties, etc… I get 24004. It started 06 Mar 23 approx 20:00
Thanks
this is supposed to be a fresh start… I dont really understand why the company doesnt go oh crap our game which is building hype atm is on fire we need to have people stop what they are doing for a few hours and fix it
I play in the Americas server and now I am unable to join public bouties, rift or greater rifts. From Torment 6 to 16. I have tried 3 different characters same result