Season 15's Launch Went Badly: 5.5 Hours Locked Out and an Early Rebirth
A creator's record of launch day: five and a half hours of failed logins, sparse communication, and a few players using Rebirth early.
The short version: this was not queueing, it was roughly five and a half hours of failed logins.
Mathilification’s 16 September 2026 recording documents the day and explains why it was worse than a typical season launch.
The timeline
| Time | What happened |
|---|---|
| Launch | Large numbers of players clicked in and were refused. No queue, no game |
| About 10–15 minutes in | Blizzard confirmed a server problem and said it was investigating |
| About 1.5 hours in | Blizzard updated: still broken |
| About 4 hours in | Blizzard announced the season was delayed, without a recovery time |
| About 5.5 hours in | Logins worked again |
The creator describes it as five and a half hours of click, refuse, click. No queue screen ever appeared. In his view it was worse than Diablo III’s worst launch.
The bigger problem: Rebirth was used early
The real issue was not the lockout. It was that some people got in.
- A small number of players logged in during the failure and used season 15’s new Rebirth to bring old characters into the season.
- Rebirth preserves account-level progress. According to the video, those players carried over last season’s Paragon points, gold and materials.
- His comparison: starting a new season at level 20 with a fully unlocked passive tree and the entire materials stash.
That is widely understood to be why Blizzard chose to delay the season rather than let more players in. The creator also concedes that if this was the reason, taking the servers down to fix it makes sense, even though Blizzard never explained it.
What Blizzard and the press said
Polygon’s 16 September update records that Blizzard announced a delay caused by login problems and said that evening the issue was resolved. The company has not published a root cause or compensation plan.
Player reaction
The top comments on the video are largely self-deprecating:
- “D5 bad”, “they wanted to recreate the D3 launch experience”, and “Error 37 nostalgia is real” were the most liked.
- A sharper one: “this is only the 15th time they did this, they’ll get it right next time.”
Those are comment-section views, not official positions. If you still cannot log in, use the code 34202 fix order; for the season itself, see the season 15 page.
Sources
Related pages
guide
Why Long-Time Players Stop Playing Diablo IV
A creator with thousands of hours explains why he stopped logging in daily, and why the seasonal loop wears motivation down.
guide
Season 15 Gem Farming: The Efficient Route
With the old farm nerfed, run the World Stone Keep dungeon south of Kyovashad for royal gems, charms and runes.
guide
Season 15 Runewords: How Good Are the New Ones?
wudijo tests all 17 season 15 runewords: how to craft them, whether runes come back, the free Stealth, and the Ber rune recipe.