Dead by Daylight has no official status page. That is the reason this search exists, and the reason every answer you find is really a pile of user reports. So this page does the job differently: what happened on the latest outage, which source can actually prove a problem, and what Behaviour's own support articles say each error means.
Quick answer (2 November 2026, 10:30 UTC): DBD is not showing a live outage right now. Players did report a short disruption this morning. Launch failures clustered from about 06:56 UTC, and two trackers logged an incident of 23 to 45 minutes, cleared by 07:41 UTC. The same tracker logged PlayStation Network, Helldivers 2 and Overwatch in the same hour, which points beyond DBD, but Behaviour has not published a cause. 35,748 Steam clients had the game open at 10:30 UTC. Live build: Patch 10.2.2a.
Written for: Patch 10.2.2a. Last checked: 2 November 2026, 10:30 UTC.
Is DBD down right now?
As of the check above, no tracker we read shows an active DBD problem. Down For Everyone Or Just Me reads "we are not detecting any problems", and Steam's own API returned 35,748 clients with the game open. That fits a working game, but it counts anyone sitting on the title screen too, so it is a hint and not proof.
That is a snapshot, not a live feed. An article cannot be a heartbeat monitor, and any page claiming otherwise is showing you a cached guess. If you need the state of the game this minute, use the checks in the section below. They take about two minutes.
The other live signal is new posts on r/deadbydaylight. When the game breaks, posts appear within minutes. This morning's first thread went up at 07:16 UTC.
What happened on 2 November 2026?
Here is the sequence, with the source for each step, so you can judge it yourself.
- 1 November: PlayStation Network had trouble first. Outage tracking quoted by The Sunday Guardian put the report spike at about five hours, ending in the early hours of 2 November.
- 06:48 to 07:42 UTC: Down For Everyone Or Just Me opened incidents on four services in the same hour: Helldivers 2 (06:48 to 07:40), Overwatch (06:54 to 07:27), DBD (06:56 to 07:41) and PlayStation Network (07:06 to 07:42).
- 06:56 to 07:18 UTC: DBD reports bunched together on the Down For Everyone Or Just Me feed: 13 in that window, 11 about launching the game and 2 about login, from the United States, Canada, Australia, Japan and Germany.
- 07:07 UTC: StatusGator detected "Sign in and initialization errors affecting service access", lasting 23 minutes.
- 07:16 UTC: A r/deadbydaylight thread reported: "I received an initialization error on PS5. Down Detector has a huge spike of reports."
- By 07:33 UTC: A press snapshot of Downdetector showed 75% of complaints about game launch, 13% about server connection and 6% about login.
- 07:41 UTC: Down For Everyone Or Just Me marked the problem resolved, with 45 minutes of total downtime.
- 10:30 UTC: No tracker we read showed an active problem. Outage.Report had logged nothing at all for the morning.
What this does and does not prove. DBD almost certainly was not alone. Four services dropping and recovering within the same hour on one tracker suggests a shared cause, and PlayStation Network is the obvious suspect, helped by the PS5 report and a reply calling it "a playstation issue". But DBD's incident opened ten minutes before PSN's, the same tracker shows nothing for Steam since 27 October or Xbox since September, and we have no platform breakdown of the reports. So the honest reading is likely shared, likely console-side, unconfirmed.
Behaviour's Steam news feed had no outage post at the time of writing, and StatusGator lists the incident as "Never acknowledged". Our scrape of @DeadbyDaylight only returned posts up to 30 October, so that account is a gap rather than a confirmed silence. A later Behaviour statement would replace this reading.
This is routine. StatusGator lists nine short DBD incidents between 6 October and 2 November, from 7 to 45 minutes long, and marks every one "Never acknowledged". Two began within two hours of a Steam patch post: 14 October at 15:29 UTC and 20 October at 16:48 UTC. Most blips clear before anyone from Behaviour would comment.
How do you check DBD server status on your platform?
Status sites such as Downdetector and StatusGator count complaints. They are useful, but they measure people clicking a button, not servers. Treat both as evidence of a pattern, and look for two sources agreeing before you stop troubleshooting.
We tested the two addresses a Behaviour status page would normally use, status.bhvr.com and status.deadbydaylight.com. Neither exists. So the first-party route is the platform holder, and Behaviour's Error Code 107 article lists exactly where to look:
| Platform | Where Behaviour sends you | What to look for |
|---|---|---|
| PlayStation | status.playstation.com | Any alert on gaming and social |
| Xbox and Windows | Xbox status | Multiplayer and sign-in alerts |
| Steam | Steam charts page | Slow load or time-out means a Steam-wide issue |
| Epic Games Store and EAC | status.epicgames.com | Epic Online Services and Easy Anti-Cheat |
| Nintendo Switch | Nintendo network status | Maintenance windows |
| GeForce NOW | status.geforcenow.com | Region alerts |
A quick test beats all of these: open another online game. If that works and DBD does not, the fault is probably on the DBD side. If both fail, look at your platform or your connection. The board above puts the error text first because it often settles the question early.
What do DBD error codes mean?
These are Behaviour's definitions, from its support site, checked on 2 November 2026.
| Message | What Behaviour says it means | What to do |
|---|---|---|
| Error 130 | Heavy load from many players launching at once | Wait 15 to 30 minutes. Contact Support if it lasts past 24 hours |
| Error 107 | A network disconnection and reconnection, or platform services down | Check platform status, run the network steps, allow DBD through Windows Firewall |
| RTM Error | Possibly wrong system date and time, or NAT type | Fix date and time. Use Open or Type 1 NAT, or Type A or B on Switch |
| Version Mismatch | You and your friends are on different builds | Everyone updates to the latest version |
| EAC Error 4 | Can be faulty hardware, specifically RAM | Verify game files, run sfc /scannow as admin, then test your hardware |
| EAC Error 3 | Behaviour does not explain it | Contact Support with your Steam profile URL or ID64 |
| EAC Launch Error | A security update flagged outdated software or a driver | Update the software named in the message |
The one to memorise is Error 130, because it is the only code here that Behaviour directly ties to its own servers. In its words: "Error 130 signifies that there is currently a large load on our servers due to many people trying to launch Dead by Daylight at once." So on a big launch day, 130 is a reason to wait, not a reason to reinstall.
For anything else that crashes on PC, Behaviour keeps a master fix guide, updated 28 October 2026, that ends with a reinstall. Treat that as the last step, not the first.
Why does DBD say "Initialization Error"?
At least one PS5 player reported this message this morning, and StatusGator logged the same wording. Older player reports give the full text: "The game has initialized incorrectly and may not save your game properly. Restarting your game may resolve the problem."
We searched Behaviour's support site and found no article for this error, so there is no official meaning to quote. Player bug reports on the old official forum go back to at least 2024, mostly on PlayStation, and some players report it alongside a follow-up "connection error". That points to the game failing to reach its online services at startup, but that is our reading, not Behaviour's.
In order of effort, try this:
- Check the status first. If trackers and Reddit are lit up, stop troubleshooting. A restart loop will not beat an outage.
- Restart the game fully. This is what the message itself asks for.
- Restart the console and router. Behaviour's Network Troubleshooting article covers the router reset: unplug, wait at least 15 seconds, then power the modem first.
- Treat a reinstall as a long shot. In the old forum threads we read, one Xbox player said it worked and three PlayStation players said it did not. It is also a large download.
Skip paid "game booster" pitches for this error. Behaviour's support articles do not recommend them.
Will you get a penalty if the servers drop you?
Probably yes, if you were in a match. Behaviour's Disconnection Penalty article, updated 1 November 2026, says anything that takes you out of a match counts as a disconnect, and it names "an internet outage or Steam maintenance" as things that are not your fault but can still trigger it.
Its reassurance is limited: penalties "start off small enough that the occasional outage should not be noticeable." Behaviour also states flatly that it does not accept appeals, and it publishes no timer ladder, so any exact penalty table online is guesswork. For the rules on leaving a match properly, see our guide to abandon, surrender and End Trial.
There is a second cost this week. The Haunted by Daylight log-in reward renews at 15:00 UTC and the event ends on 3 November, and a player on r/deadbydaylight says each reward disappears if you miss it before the next one. By our count on the Bloodpoint codes page, 2 November opens the last claim window.
When is the next planned DBD downtime?
Behaviour publishes no fixed maintenance calendar that we could find, so the best guide is the patch schedule. All four of October's live updates landed in the same window, per Steam:
| Update | Steam post time (UTC) |
|---|---|
| 10.2.0 Mid-Chapter | 6 October, 14:33 |
| 10.2.1 Bugfix | 14 October, 15:01 |
| 10.2.2 Bugfix | 20 October, 15:01 |
| 10.2.2a Backend Bugfix | 29 October, 15:06 |
Those times track Eastern Time, and the clocks went back on 1 November. Last winter's patch posts landed between about 15:30 and 16:00 UTC, so expect that window now, and check the Steam news feed if trouble starts around it. Small backend patches can need only a game restart: Behaviour's Japanese account said of 10.2.2a that no download was required, but anyone already in-game had to restart.
The next big date is 10.3.0, the Terrifier Chapter. Steam lists 24 November 2026 at 17:00 UTC, which would be later than a normal patch, and Behaviour's Japanese account says the 25 November update, which fits the same release given the time difference. Expect a version mismatch window and, given Behaviour's own Error 130 description, a real chance of launch queues that day. Friends on different platforms should also check our crossplay guide if the party will not form after the update.
Where can you report a DBD problem now?
Not on the forums. Behaviour announced on 21 September 2026 that it would close them, with the site banner giving 1 November 2026, and said community support moves to the official Discord, Steam Discussions and r/deadbydaylight. For a personal issue, use the support site: Behaviour asks for as much detail as possible and a screenshot of the error.
Stuck in the lobby anyway? Use the time on something that needs no servers. Our Dead by Daylight guides cover the current meta and every working code:
FAQ
Is DBD down right now? As of 2 November 2026 at 10:30 UTC, no tracker we read showed an active outage. A short disruption hit earlier that morning and cleared by 07:41 UTC.
Does Dead by Daylight have an official server status page? No. Status.bhvr.com and status.deadbydaylight.com do not exist. Behaviour's support site points players to each platform's own status page.
Why won't DBD load on PS5? The likeliest causes are PlayStation Network trouble, DBD's online services, or the Initialization Error covered above. Check status.playstation.com first, then restart the game and console.
What does Error 130 mean in DBD? Behaviour says it means a large load on its servers from many players launching at once. Wait 15 to 30 minutes and retry. Contact Support if it continues after 24 hours.
Do you get a penalty if DBD crashes mid-match? Behaviour says anything that takes you out of a match counts as a disconnect, including outages out of your control, and it does not accept appeals. It says the first penalties are small.
Do DBD servers go down for patches? Behaviour publishes no maintenance calendar we could find. October's four live updates posted between 14:33 and 15:06 UTC, and winter posts ran about an hour later, so check the Steam news feed first if trouble starts around then.
