Does Dead by Daylight have dedicated servers?
Yes. In a 2019 status update on its official forum, Behaviour described converting Dead by Daylight "from the existing peer to peer system" to dedicated servers, so that players connect to a server rather than directly to each other. The release had slipped from summer and was then targeted at all platforms in fall 2019, after live tests on Steam. The launch locations Behaviour named were Singapore, Tokyo, Sydney, Frankfurt, London, Sao Paulo, North Virginia and Oregon, with more regions to be switched on from time to time to test match quality.
The same update made two promises that matter for this error. Dedicated servers would let Behaviour better identify disconnections, and so act more strictly against players who disconnect too often. And a proper disconnection handling system, along with expanded hit authority (who has the final say on a hit when connections are poor), would come after release, with no date at the time.
What "Dedicated server is not responding" means
The full message players quote is "Dedicated server is not responding; disconnecting". Behaviour has not published a technical definition, but the wording is plain: your game expected regular updates from the match server, stopped getting them, and left the trial. A server that froze or crashed, a broken route between you and the server's region, or a drop on your own connection all end the same way. That is why the message alone cannot tell you whose fault it was, and why the context around it matters more than the text.
In the threads we read, players hit it:
- while loading into a trial, sometimes after the loading screen hangs for around ten minutes;
- mid-match, on actions such as hooking, picking up a survivor or vaulting a window;
- right after a long queue, especially as killer, where a single disconnect can cost the whole wait;
- on PC and on Xbox Series S, so it is not tied to one platform.
What players hit in September and October 2026
These are reports from r/deadbydaylight threads over the last six weeks. They are player accounts, not Behaviour data, but they show the shape of the problem.
| Date | Where | What the player reported |
|---|---|---|
| September 13 | Killer queue | Two waits of about 40 minutes each ended in the error, and the queue spot was lost both times. |
| September 25 | Playing with friends | About once per session, mostly while loading in, with a 15-minute ban each time despite a stable connection and a firewall exemption. A reply described the same thing in 2v8 as killer, after waits of up to two hours. |
| October 14 | "The new game mode", in the poster's words | The error every few attempts to queue, then no way into a match at all. |
| October 17 | Every match that day | Random disconnects with the error, then a 30-minute matchmaking ban. |
| October 18 | Xbox Series S, mostly killer matches | Every day for about three weeks. |
| October 21 | Killer, on the latest patch | Three disconnects in three matches, while hooking, grabbing a survivor and vaulting, then a matchmaking ban. A reply described matches alternating between loading fine and kicking players out. |
Two patterns stand out. The killer side complains loudest, because a killer queue can be long and the disconnect throws it away. And the reports cluster around content drops: the 2v8 update in early September and the Haunted by Daylight event in mid-October, both of which change how many people queue and for what.
What Behaviour's patches since September say
Behaviour's own announcements on Steam give the timeline the error sits in:
- September 2 to 15: an anti-cheat trial ran Denuvo Anti-Cheat in the Steam version only. On September 15 an update ended the trial and removed it. Behaviour said cross-play would not be affected.
- September 8, patch 10.1.2: the 2v8 mode got The Xenomorph and the Nostromo Wreckage map. The same patch fixed the matchmaking button not resetting when a ban timer reached zero.
- October 6, patch 10.2.0 (Mid-Chapter): adjustments to more than 50 perks.
- October 13: the Haunted by Daylight event started at 11:00 Eastern, with Void Portals and Void Haunts in every trial.
- October 14, patch 10.2.1: fixed a crash in trials with The Wraith, and an issue where latency could leave killers stuck in a third-person view.
- October 20, patch 10.2.2: fixed crashes during loading on some platforms and during map generation, and a matchmaking queue timer that started early and kept running after queueing stopped.
- November 5 to 12: the Lights Out: Stranger Things Edition event is next.
None of these notes names "Dedicated server is not responding". Two of the 10.2.2 fixes deal with crashes while loading and while generating the map, which is when many players say the error hits, but Behaviour has not connected them. Treat that as a possibility, not a diagnosis.
The matchmaking ban problem
Behaviour said in 2019 that dedicated servers would help it spot disconnections and act against players who disconnect too often. Seven years later, the complaint in the threads runs the other way: players say they get matchmaking bans of 15 or 30 minutes for disconnects they did not cause, and lose the match's progress on top. The 10.1.2 fix to the ban timer confirms the ban system is part of the current game. We found no 2026 statement from Behaviour saying that disconnects caused by a server failure are exempt.
The useful thing to do with a ban you think you did not earn is to report it. Behaviour's support portal takes tickets; include the time the disconnect happened in UTC, your platform, your role and game mode, the exact message, and whether other players in your party were dropped at the same moment. A party that all drops together is the clearest evidence that the server, not your connection, went away.
Is it you or the servers?
- Look for others at the same moment. Check the newest posts in r/deadbydaylight, Behaviour's official accounts and the BHVR forums. If many players report the error within minutes of each other, stop requeueing: nothing on your side will help, and players report a new ban for each disconnect.
- Install pending updates. Behaviour shipped bug fix patches on October 14 and October 20, and players in the threads asked each other first whether they had downloaded the latest one.
- Test your own connection while it happens. If another online game drops at the same time, the problem is local. A wired connection and a router restart rule out the most common home causes.
- On Steam, verify the game files from the game's Properties, Installed Files tab, to rule out a damaged install.
- Note when it happens. Only on load-in, only as killer, only in one mode: those details are what a support ticket needs, and they separate a server pattern from a local fault.
If your connection is stable, the error comes during loading, and players across platforms report it on the same day, the fault is not yours, and a firewall exemption or a reinstall will not fix it. The September 25 poster had already done the firewall exemption and still hit it once a session.
Can you run your own Dead by Daylight server?
No. Dead by Daylight matches run only on Behaviour's servers, and there is no server software for players to host or rent, which is the main difference from survival games like Rust, ARK or Valheim, where communities run their own. Private matches with friends go through the game's Custom Game mode. For the games where you can run the server yourself, see our list of multiplayer games with dedicated servers; for the same "is it them or me" problem in another publisher-run game, see our ARC Raiders server status guide. Our piece on the Jason chapter and asymmetric horror covers why the game keeps its audience despite all this.
Behaviour's patch notes and announcements are on the Dead by Daylight news page on Steam.
FAQ
- Does Dead by Daylight have dedicated servers?
- Yes. Behaviour moved Dead by Daylight from peer-to-peer to dedicated servers, a switch it announced in 2019 for all platforms, so players connect to a match server rather than directly to each other. There is no server software for players to host their own.
- What does "Dedicated server is not responding; disconnecting" mean?
- Your game stopped receiving updates from the match server and left the trial. The message does not say whose side failed: a frozen or crashed server, a routing problem or your own connection can all end the same way.
- Is "dedicated server not responding" my fault?
- Not necessarily. If many players report it at the same moment, or your whole party drops together, it is on Behaviour's side and only waiting helps. If only you are affected, test your connection, install pending updates and verify the game files on Steam.
- Do you get a matchmaking ban for "dedicated server not responding"?
- Players in September and October 2026 report 15 and 30 minute matchmaking bans after these disconnects. We found no 2026 statement from Behaviour that disconnects caused by a server failure are exempt, so report each case to Behaviour support with the time, platform and mode.
- Can you play Dead by Daylight on your own server?
- No. Matches run only on Behaviour's servers and there is no server software to host or rent. Private matches with friends use the in-game Custom Game mode.
Community reading note: Player reports in this piece come from r/deadbydaylight threads titled "You should get your killer queue spot back when the dedicated server crashes." (September 13, 2026), one titled with the error message itself (September 25, 2026), "Is it me or is the new game mode really difficult to actually get games on?" (October 14, 2026), "Is anybody else having serious connection issues?" (October 17, 2026), "Dedicated server not responding on Xbox series s" (October 18, 2026) and "Disconnection on last update ?" (October 21, 2026). They are player reports, not Behaviour policy.