Hey. The issue is on Blizzard’s end - and the problem has been known since February. This entire half-year they’ve refused to admit there’s an issue, take any action to fix it, or even reply to a single of dozens threads reporting this. S-tier company as usual.
The actual issue (faulty node on Blizzard’s end) is visible on the screenshot here:
And you can see the issue being “a thing” on Feb 17 already (same root of the issue):