Bug: Blank Stats Page for Recent Match History on Dead by Daylight
Bug #8252
Blank Stats Page for Recent Match History on Dead by Daylight
| Status: | Open |
| Priority: |
High |
| Added by: | Anonymous on October 27, '26 |
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
The stats website should load correctly for all users when accessed directly, allowing them to view their recent match history without any additional steps.
|
| Expected Result: |
For some users, accessing the stats website directly results in a completely blank white page. However, deliberately triggering a 404 error and navigating to Recent Match History through the navigation bar successfully loads the page.
|
| Severity: |
Major
|
| Reproducibility: |
Always
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
Not set
|
Steps to Reproduce
- Navigate directly to the Dead by Daylight stats website: https://stats.deadbydaylight.com/
- If you're affected, notice that the website displays a blank white page.
- To bypass this issue, deliberately navigate to an invalid URL, such as https://stats.deadbydaylight.com/asdasd/, to trigger the website's 404 error landing page.
- From the 404 page, use the top navigation bar to manually navigate to Recent Match History.
- The recent match history page now loads correctly, allowing you to view your statistics.
Explanation
The official Stats page (Recent Match History) is completely blank white for some users. This is a recurring issue that I've noticed on some of my accounts. The only workaround is to deliberately navigate to an invalid URL path, such as https://stats.deadbydaylight.com/hellobhvrdevs/, to trigger the 404 error landing page, and then from there manually navigate to Recent Match History using the top navigation bar. This allows the page to load correctly.
I previously reported this issue back in April (Support Ticket #2203225), where I also provided the same workaround. The issue resolved itself some days after support contacted me back without any intervention on my end, but it appears to have resurfaced on another account of mine, suggesting that this may be a recurring problem affecting certain users.
Please look into this, thank you!
Watchers
Screenshots
None
Video Clips
None
Log Files
None