Seasons & Expansions

Season 15's Launch Went Badly: 5.5 Hours Locked Out and an Early Rebirth

Launch day brought five and a half hours of failed logins and an early Rebirth exploit. SSF stayed off until HOTFIX 3 on 18 September 2026.

9/16/2026 Diablo IV Wiki Editorial Team Last updated: 9/19/2026
Season 15's Launch Went Badly: 5.5 Hours Locked Out and an Early Rebirth video
Official Season of Hell's Legacy screenshot: a Waking Nightmare scene

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

TimeWhat happened
LaunchLarge numbers of players clicked in and were refused. No queue, no game
About 10–15 minutes inBlizzard confirmed a server problem and said it was investigating
About 1.5 hours inBlizzard updated: still broken
About 4 hours inBlizzard announced the season was delayed, without a recovery time
About 5.5 hours inLogins 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 the materials stash.
  • His comparison: starting a new season at level 20 with a fully unlocked passive tree and the entire materials stash for free.

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. Blizzard never explained it.

The four days after launch

Fixing logins did not end it.

DateStatus
15 September 2026Season live; about 5.5 hours of failed logins; a few early players carried last season’s progress through Rebirth
16 September 2026Blizzard announced Solo Self-Found was disabled because old seasonal progress had not reset correctly
18 September 2026HOTFIX 3 (3.2.1): Tree of Whispers caches claimable again, SSF re-enabled, trade window item display fixed

HOTFIX 3 confirmed two things: Tree of Whispers reward caches were fixed, and Solo Self-Found was restored. Before that, Tree of Whispers caches could not be claimed for roughly two days, which was the most-discussed problem in the community.

Players also reported a new issue in the same hotfix thread: after an item was taken back out, the trade window still showed it, so both sides believed the trade had completed. Blizzard did not mention this in the HOTFIX 3 notes.

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 a 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

  • Mathilification, “D4 Latest Season Launch Goes Hilariously Bad”: source
  • Polygon on the delay and recovery: source
  • Official HOTFIX 3 notes (Tree of Whispers and SSF fixes, 18 September 2026): source
  • Official SSF update announcement (16 September 2026): source
  • Official season 15 notes (Rebirth mechanics): source
Advertisement
video season-15 launch
Advertisement

Related pages