Bug: Post-October 2025 AWS Outage: Dedicated Server Unresponsiveness on Stable Connections
Bug #2824
Post-October 2025 AWS Outage: Dedicated Server Unresponsiveness on Stable Connections
| Status: | Under Investigation |
| Priority: |
High |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
The game abruptly disconnects and issues a matchmaking penalty, even though the external internet connection (Twitch stream) remains fully active without any buffering or interruption.
|
| Expected Result: |
The game should maintain a stable handshake with the dedicated servers on a standard connection without requiring a VPN, matching the stability observed prior to the AWS outage.
|
| Severity: |
Major
|
| Reproducibility: |
Always
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
This is a controlled experiment recorded via OBS. Since Twitch is highly sensitive to network drops, the fact that the stream remained unaffected while the game failed proves that the issue is not with my ISP or hardware. The server-side changes made after the AWS outage have likely created a routing failure for certain IP ranges. I have the video evidence ready if your technical team requires it for analysis.
|
Steps to Reproduce
- Launch the game without a VPN on a standard internet connection.
- Simultaneously run a high-bandwidth service (e.g., a Twitch live stream) and record both windows using OBS.
- Enter a match and play normally.
- Observe the game client disconnecting with the "Dedicated server not responding" error while the Twitch stream continues to play flawlessly.
Explanation
"Dedicated server not responding" errors occur on stable connections, resulting in unfair player penalties.
These stability issues began immediately following the October 20, 2025, global AWS outage. Previously, my connection was perfectly stable. Now, playing without a VPN results in a disconnection rate of nearly 50%. However, using a VPN consistently guarantees a smooth and stable connection, which strongly suggests a server-side routing conflict.To verify the root cause, I conducted the following controlled test
Watchers
Duplicates (2)
Bug Occurrence
Screenshots
Video Clips
None
Log Files
None