The report is currently one player's detailed experience, not evidence that Diablo IV's servers are broadly failing or that every player is losing Sigils. The player believes the issue is server-side and provides several reasons for that suspicion, including a 600 Mbps connection, routine network maintenance and other internet-connected devices continuing to work normally. But without Blizzard diagnosing the connection path, there are still plenty of possibilities between the player's PC and Diablo IV's game servers. What we can document is the symptom: the game stops responding, the player disconnects, they cannot immediately reconnect while the character is apparently being saved, and once they return, the active dungeon has reset and the consumed Sigil is gone. Six reported disconnects at almost the same point after logging in makes for an unusually consistent little disaster. (September 9 technical-support report)
Six Disconnects, Roughly Nine to Ten Minutes After Login
The original post already described repeated failures during Nightmare and Escalation content, but the player later added a particularly useful detail: by that point they had experienced six disconnects, each roughly nine to ten minutes after selecting a character. That kind of timing is precisely why the player began looking for something more systematic than ordinary random internet instability. They even asked Blizzard whether there is a server address they could monitor with ping or traceroute and offered to build a simple Python or PowerShell monitoring script to capture network anomalies while playing.
That does not prove Blizzard's infrastructure is responsible. Home networks, ISP routing, packet loss, security software, local client problems and the connection between regional networks can all produce symptoms that look remarkably similar from the player's chair. “Everything else works” is useful evidence, but it is not a full network diagnosis. Still, six sessions apparently failing within the same narrow window deserves investigation, especially when each failure can consume a resource attached to seasonal progression.
The dungeon is supposed to be dangerous. Apparently the connection screen has applied for the position too.
The Player Says 13 Sigils Have Already Been Lost
The material cost is what turns a generic disconnect complaint into a proper Diablo story. According to the player, the failures have consumed 10 Nightmare Sigils and three Escalation Sigils. Ordinary Nightmare Sigils are replaceable, but losing thirteen entry items while testing the same connection problem becomes tedious surprisingly quickly. Escalation Sigils are particularly annoying because they launch Escalating Nightmares, the multi-dungeon chains Blizzard originally introduced with Season 9 and later integrated more deeply into War Plans.
Blizzard describes an Escalating Nightmare as a sequence of three Nightmare Dungeons, where each dungeon carries its affixes forward and makes the next stage more dangerous. Complete the full Torment chain and players eventually face the Exalted version of Astaroth. The activity therefore asks for considerably more commitment than opening one ordinary dungeon, and the Sigil represents permission to start that chain in the first place. (Blizzard's Escalating Nightmares guide)
Lose the connection halfway through and the player does not merely lose nine minutes. They potentially lose the key to the entire sequence.
War Plans Make the Disconnect More Expensive
The current player's frustration is amplified because their War Plan specifically requires Escalation Dungeon completion. War Plans were built to turn Diablo IV's increasingly crowded endgame into something resembling a coherent route: players chain together activities, complete objectives and progress the Command Table rather than wandering between Helltides, Nightmare Dungeons, The Pit and various bosses according to whichever map icon happens to look most threatening.
We have already spent quite a lot of time documenting what happens when that structure stops progressing correctly. Season 14 players have reported War Plans becoming stuck or failing to recognize completed activities, while another investigation found Escalation Dungeons themselves sometimes failing to satisfy the War Plan objective even after players clear all three floors and defeat Astaroth. More recently, some players have reached every visible maximum and still remained stuck at War Plans Rank 9/10. The September 9 case is technically different: according to this player, the War Plan cannot progress because the connection repeatedly ends the activity before the game gets a chance to register completion.
The result feels nearly identical from the player's side. The objective remains unfinished. Another Escalation Sigil is consumed. Another run begins.
Blizzard Has Already Fixed One Disconnect-Related War Plan Bug
There is a relevant precedent in Blizzard's own patch history. Patch 3.0.4 on June 10 fixed an issue where War Plan progression could become blocked if a player disconnected while claiming rewards. That does not describe the current report, which involves disconnecting during the activity itself rather than during reward collection, but it confirms that disconnect handling has previously been capable of leaving War Plan state in a bad place. (official Patch 3.0.4 notes)
Blizzard has also continued expanding the number of Nightmare Escalation options available through War Plans. The current patch notes mention additional Helltide and Nightmare Escalation choices, making reliable completion increasingly important to the system rather than less. War Plans are supposed to remove friction by letting the player create a preferred chain of activities. A repeated disconnect that consumes the activity's entry resource turns that principle inside out.
Instead of “build your ideal endgame playlist,” the affected player gets “restart track three until the network approves.”
War Plans Can Generate Sigils, but Losing Them Still Matters
Blizzard's original Lord of Hatred explanation notes that War Plans can generate an activity Sigil on the fly when the player does not already possess one. That means not every War Plan node necessarily requires farming a separate key beforehand. But Escalation Sigils remain real, consumable endgame items outside that convenience layer, and the September player specifically says they are replacing the lost ones through the Cube before retrying the objective. Blizzard also increased rewards and added additional War Plan quests around Nightmare Dungeon Escalation Sigils in Season 14, reinforcing their place in the current endgame loop. (Lord of Hatred War Plans overview)
The broader issue is not whether another Sigil can eventually be created. Diablo players can replace almost anything if sufficiently motivated. The question is whether an externally interrupted activity should consume the resource permanently when no meaningful gameplay failure occurred. Dying because an Escalating Nightmare became too difficult is part of the game. Losing access because the session vanished nine minutes after login is a very different transaction.
This Is Exactly Why Disconnect Protection Matters
Online-only ARPGs have always had an awkward relationship with consumable content. Once an activity begins, the server needs rules governing what happens if the player disappears. If every disconnect refunded everything automatically, deliberate connection drops could become an exploit whenever a run begins badly. If nothing is ever refunded, legitimate connection failures become expensive. Developers therefore have to distinguish between failures that look nearly identical from the server's perspective while producing very different experiences for the player.
Diablo IV has had this tension since launch, and the cost becomes more visible as Blizzard adds more activities behind keys, Sigils and other access items. Earlier this week, we covered players saying Longtooth can consume a valuable Mythic Tribute without delivering the expected loot. Yesterday, The Resounding Scream was still leaving some players unable to access Echoing Hatred even after obtaining rare Trace of Echoes. The mechanics differ, but the frustration is remarkably similar: obtaining the entry resource is one challenge; convincing the activity to respect that resource is becoming another.
The Player Is Asking for Better Diagnostics, Not Just a Refund
One of the more useful aspects of the report is that the player is not simply demanding thirteen Sigils back. They ask whether Blizzard can provide a server endpoint they could monitor to determine where the connection actually fails. That would allow continuous ping or route monitoring during the session and potentially reveal whether packet loss appears locally, inside the ISP route or closer to Blizzard's infrastructure.
That kind of data would be considerably more useful than the traditional technical-support ritual of restarting the router for the fifth time and hoping the demons notice. The player says they already power-cycle their network regularly, flush DNS, have no large downloads or streams competing for bandwidth and host much of their household content through a NAS. Again, none of that rules out a local problem, but it does demonstrate why more detailed connection diagnostics would help. A failure that appears at almost the same interval across repeated sessions should be measurable somewhere.
This Is Still One Player Report, Not a Server Outage
The most important caveat remains scale. Blizzard's current Technical Support forum does not show a flood of identical September reports describing disconnects precisely nine to ten minutes after login. The September 9 thread has no large collection of confirmations behind it. We therefore should not describe Diablo IV as suffering a widespread server failure based on one detailed case. The player themselves insists the problem “has to be server-side,” but that remains their diagnosis rather than a confirmed Blizzard finding.
What makes the report newsworthy is the very specific cost attached to it: six repeated session failures, approximately the same timing, thirteen lost Sigils and War Plan progression that cannot move forward because the relevant Escalation Dungeon keeps being interrupted. That is enough for a player-report story. It is not enough for “Diablo IV servers are broken.” Sanctuary already contains sufficient exaggeration without our assistance.
Thirteen Sigils Is an Expensive Way to Troubleshoot a Connection
For now, players experiencing similar behaviour should probably stop repeatedly feeding valuable Escalation Sigils into the problem until they have tested the obvious connection variables. Try an ordinary dungeon or open-world session and see whether the disconnect occurs at the same interval. Record the exact time from character login. Check Windows Event Viewer, network adapter behaviour and packet loss. If possible, test another connection temporarily. The goal is not to prove Blizzard guilty or innocent; it is to find whether the nine-to-ten-minute pattern survives outside the expensive content.
And if the same disconnect continues occurring with suspicious precision, document it before using another valuable entry item. Screenshots, timestamps and route data give Blizzard far more to work with than a pile of vanished Sigils and understandable profanity.
Diablo IV's Escalating Nightmares are supposed to become more dangerous as you descend through the chain.
For one player, the most reliable escalation currently happens about ten minutes after logging in.
