Issue Description (Required):
I am experiencing recurring backend connectivity failures in Warhammer 40,000: Darktide. The game frequently fails to connect to backend services or disconnects during matchmaking or mission loading, resulting in error codes 3001, 3013, and occasionally 2014.
According to console.log, the issue is caused by backend connection and resolving timeouts when attempting to connect via gRPC to bsp-im-prod.atoma.cloud:443. The logs consistently show resolving and handshake timeouts rather than client-side crashes or authentication failures.
The issue occurs intermittently but frequently enough to prevent stable gameplay.
Recurring backend connection timeouts (Error codes 3001 / 3013 / 2014) – gRPC resolving timeout to atoma.cloud
Description
I am experiencing recurring and persistent connection failures in Warhammer 40,000: Darktide.
The game frequently fails to connect to backend services or disconnects during matchmaking or mission loading, resulting in error codes 3001, 3013, and occasionally 2014.
The issue occurs intermittently but has become frequent enough to prevent normal gameplay.
Error Codes Observed
- 3001
- 3013
- 2014
Log Evidence
From console.log:
[Backend] Resolving timed out after 5003 milliseconds
Code: 1000
Description: Resolving timed out after 5003 milliseconds
[GRPCManager] Connecting to grpc address bsp-im-prod.atoma.cloud:443
Additional backend-related errors observed:
failed_handshake_timeoutpong_timeoutfailed_found_no_lobbynonexisting_channel
These indicate backend connectivity and handshake failures rather than client-side crashes.
Environment
- OS: Windows 11
- Platform: Steam
- Network: Home broadband (Wi-Fi router)
- Region: Russia
Troubleshooting Already Attempted
The following steps were tested extensively and did not resolve the issue:
- Changing DNS providers (multiple public DNS)
- Flushing DNS cache and resetting network stack
- Using VPNs with different servers and protocols (including encrypted tunnels)
- Disabling VPN entirely
- Restarting router and PC
- Reinstalling the game
- Switching between Wi-Fi and Ethernet (when available)
The problem persists across all of the above scenarios.
Additional Notes
- The timeout occurs specifically during backend resolution / connection to atoma.cloud infrastructure via gRPC over port 443.
- This strongly suggests a network routing, DPI, or regional connectivity issue rather than a local configuration problem.
- Similar reports are being posted by other players, particularly from Russia, but not limited exclusively to this region.
Attachments
console.logdarktide_launcher.log
Request
Please investigate potential backend routing, gRPC connectivity, or regional network compatibility issues affecting connections to atoma.cloud, particularly for players in Russia.
If additional diagnostics or traces are required, I am willing to provide them.
Thank you for your time and support.
Attempted Solutions (Optional):
Changed DNS providers (multiple public DNS services)
Flushed DNS cache and reset Windows network stack
Restarted PC and router
Tested with VPN enabled and disabled (multiple servers and protocols)
Switched between different VPN providers and encryption methods
Reinstalled the game
Tested different network configurations (Wi-Fi / Ethernet when available)
None of the above resolved the issue.
Platform (Required):
PC - Steam
[PC] PC Specifications (Optional):
Operating System: Windows 11
Network: Home broadband connection via Wi-Fi router
Platform: Steam
Upload Supporting Evidence (Optional):
console-2025-12-13-17.23.08-cd05b291-c462-4679-81e1-3c359f9fbfa2.log (331 KB)