are you kidding me? no announcement or anything… i play hc im glad i was standing in town when i got disconnected. fix your servers … when i die season is over for me. crap company
1 Like
i play also hc and it was rip for me 
Only started GR to be suspended, luckily there wasn’t any monsters near entrance… Also playing in HC.
I can get in play D3 campaign for about 10 mins before I get server maintenance message and get kicked out of the game. I can restart blizzard app and repeat play for about 10 minutes and the same thing happens.
On a personal note, stuff like this always happens when I try to play Act 5 campaign Marshlands area. Since I’m always looking under every nook and cranny, never ever have I succeeded to pass that area in 1 go. Always some type of disconnect for one reason or another.
I hope we’ll be informed on this thread, when the situation will be fixed.
1 Like
Look on the hopeful side. Maybe blizz got around to fixing the many operating problems in d3
RIP for me. I was in whimsyshire when I got the popup about the server outage…and I can still see the monster moving in the background. Hey Blizzard, please pause or kill the monsters too in case of a server outage. This is a programming fail.
They had a short-term issue with the authentication servers…
" Profile Unavailable
This profile could not be displayed, possibly for one of the following reasons:
- This account has been inactive for an extended period of time, and cannot be displayed. To be displayed again, the inactive account must first log in to Diablo III.
- A profile for this account does not exist in this region."
Webpage on our heroes. Does this happend on just me?
Mine too. My profile is disable but I was logged in 2 days ago. Also I got kicked out of the server in the middle of the rift for no reason when I was playing solo. Something is unstable. That’s why I don’t play D3 anymore. Only occasional farming if I see my mate online but 99% of the time they are not around. They all moved on to other games. So I just stick with SC2 for now.
They’re doing something odd with FQDNs (Fully Qualified Domain Names) on the profile / armoury site again.
I have this as a saved favourite for my Meteorblade hero…
https://eu.diablo3.com/en-us/profile/Meteorblade-2266/hero/80892263
That’s currently not working, but if I change the URL to…
https://eu.diablo3.blizzard.com/en-us/profile/Meteorblade-2266/hero/80892263
It re-directs to…
https://diablo3.blizzard.com/en-us/profile/Meteorblade-2266/hero/80892263
However, this gives rise to another problem, which is that I have a single hero on the US and Asia server regions so the re-direction means it’s no longer possible to see them, as a region-specific URL is automatically re-directed to the home region, i.e. it’s no longer possible to look at the armoury pages for my US or Asia heroes.
Blizzard did something similar about a month ago, and rolled back the changes. Seems they’re doing odd stuff again. There’s lots of posts about this on the US Technical Support forum too. Awaiting Blizzard response.
1 Like
I know I’ll get again ‘ban/freeze’ but still - those codemonkeys in Blizz - “Let’s use that code we have and make something on that…” and what we have is same shit on new package.
Same here Hc rip. my new barb. Thanks blizz! 