CS2 Connection Failed: Your connection to matchmaking servers is not reliable
Connection to matchmaking servers not reliable
Verified against Steam Support: CS2 Network Connectivity troubleshooting guide, Valve Developer Community: Steam Datagram Relay (SDR) documentation, r/cs2 connection issues threads and Valve employee responses · Updated June 2026
> quick_fix
Open Command Prompt as Administrator and run ipconfig /flushdns followed by netsh winsock reset. Restart your computer, then restart your router by unplugging it for 30 seconds. Launch Steam and try matchmaking again. This clears stale DNS entries and resets your network stack, which fixes the majority of cases.
ipconfig /flushdns && netsh winsock resetWhat causes this error
This error appears when CS2's client cannot establish or maintain a stable connection to Valve's Steam Datagram Relay (SDR) network, which handles all matchmaking traffic. The SDR system requires persistent UDP connectivity to Valve's Point of Presence (PoP) servers. Common causes include ISP-level UDP throttling, restrictive firewall or router NAT settings blocking the required UDP port range (27015-27050), corrupted Winsock catalog entries from VPN software, stale DNS cache pointing to decommissioned Valve relay IPs, or an actual Valve infrastructure outage in your region.
How to fix it
- 01
step 1
Check Valve server status
Before troubleshooting your own network, check if Valve's servers are down. Visit steamstat.us or check the Steam Status section on the Steam community. If CS2 game coordinator or matchmaking shows red, the problem is on Valve's end and no local fix will help.
- 02
step 2
Flush DNS and reset network stack
Open Command Prompt as Administrator and run both commands. This clears any stale DNS entries pointing to old Valve relay IPs and resets the Winsock catalog, which VPN software often corrupts.
ipconfig /flushdns netsh winsock reset netsh int ip reset - 03
step 3
Restart your router and switch DNS to public servers
Unplug your router for 30 seconds, then plug it back in. While waiting, change your DNS to Google (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1, 1.0.0.1). ISP DNS servers frequently have stale records for Valve's SDR network and return IPs for decommissioned relay nodes.
- 04
step 4
Allow CS2 and Steam through your firewall
Open Windows Defender Firewall → Allow an app through firewall. Ensure both cs2.exe and steam.exe have checkmarks for Private and Public networks. If they are missing, click 'Allow another app' and browse to their locations. Also ensure UDP ports 27015-27050 are not blocked by your router.
netsh advfirewall firewall add rule name="CS2 UDP" dir=in action=allow program="C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64\cs2.exe" protocol=UDP - 05
step 5
Disable or reconfigure VPN and proxy software
VPN clients (NordVPN, ExpressVPN, Windscribe) install TAP/TUN adapters and modify the routing table even when disconnected. Open Network Connections (ncpa.cpl) and disable any TAP-Windows or TUN adapter you see. If you need the VPN, configure split tunneling to exclude Steam and CS2 traffic.
How to verify the fix
- Launch CS2 and successfully queue for and connect to a competitive or casual match
- Open the Steam console (steam://open/console) and run 'connect' to confirm no timeout errors appear
- Play for at least 15 minutes to confirm the connection remains stable without mid-match disconnects
Why CONN happens at the runtime level
CS2 matchmaking routes all traffic through Valve's Steam Datagram Relay (SDR) network rather than direct IP connections. When you queue for a match, the client pings multiple SDR Points of Presence (PoPs) over UDP to determine the lowest-latency relay. If the client cannot complete this ping handshake with any PoP within the timeout window — typically because UDP packets are being dropped by a firewall, NAT is failing to maintain the UDP hole punch, or DNS is resolving Valve relay hostnames to stale IPs — the client surfaces this error and refuses to enter the matchmaking queue.
Common debug mistakes for CONN
- Reinstalling CS2 when the problem is entirely network-side — a 30GB download that changes nothing about DNS, firewall, or routing.
- Only checking Steam status but not the specific SDR relay status for your region — global Steam can be green while your regional PoP is degraded.
- Leaving a VPN's TAP adapter enabled in Network Connections after disconnecting the VPN — the adapter still intercepts and misroutes UDP traffic.
- Adding firewall rules for TCP only and forgetting that CS2 matchmaking uses UDP exclusively for SDR relay communication.
- Blaming their ISP without first testing on a mobile hotspot — a quick 4G/5G hotspot test isolates whether the problem is ISP-specific or local machine configuration.
When CONN signals a deeper problem
When this error persists across DNS flushes, router restarts, and firewall changes, it usually indicates a deeper routing issue between your ISP and Valve's SDR network. Some ISPs, particularly in South Asia and parts of South America, route UDP traffic through congested international transit links that drop packets above a certain threshold. The SDR client interprets sustained packet loss above 5% as an unreliable connection and refuses to queue. Running a traceroute to sdr.steampowered.com from Command Prompt can reveal where packets are dying. If the loss starts at a hop outside your network (beyond your router), the only real fixes are changing ISPs, using a gaming-optimized VPN with a server near a Valve PoP, or waiting for off-peak hours.
Editor's take
This is the error that makes players irrationally blame their internet connection and call their ISP, only to be told everything looks fine — because from the ISP's perspective, it does. HTTP works. YouTube streams. Speed tests show full bandwidth. The ISP is not wrong; they just do not test UDP connectivity to Valve's SDR relay network, which is the only thing that matters for CS2 matchmaking.
The SDR architecture is Valve's solution to DDoS protection and latency optimization. Instead of connecting players directly to game servers (which would expose server IPs), all traffic routes through relay nodes. It works well when it works. When it does not, the error message gives you absolutely no diagnostic information — just 'not reliable,' which could mean anything from a DNS typo to an ISP routing policy.
The single most effective diagnostic step that almost nobody does: open Steam's console (steam://open/console) and type 'net_client_steamdatagram_enable_override 1' followed by trying to connect. The console output will show exactly which SDR PoPs the client is trying to reach and what the ping/loss numbers look like. If every PoP shows 100% loss, your UDP traffic is being blocked wholesale. If only your nearest PoP shows loss, that specific relay is degraded and forcing a different PoP via mm_dedicated_search_maxping can work as a temporary bypass.
The VPN trap is worth calling out specifically. NordVPN, ExpressVPN, and similar clients install a TAP-Windows adapter that persists in your network stack even when the VPN is disconnected. This adapter can intercept UDP traffic meant for the physical adapter and route it nowhere. The fix is not just disconnecting the VPN — it is going into Network Connections (ncpa.cpl) and explicitly disabling the TAP adapter. This single step resolves a surprising number of cases where players swear they are not using a VPN.
By Bikram Nath · Curator · Updated June 2026
Frequently asked questions
Why does this error only happen at certain times of day?
ISPs in congested regions throttle UDP traffic during peak hours (evenings and weekends) to prioritize HTTP/HTTPS. Valve's SDR network uses UDP exclusively for game traffic. Switching to a wired connection and using public DNS reduces but may not eliminate peak-hour throttling. If it persists, contact your ISP about UDP QoS policies.
I reinstalled CS2 and still get the error. Why?
This error has nothing to do with game files. It is a network connectivity issue between your machine and Valve's relay servers. Reinstalling CS2 does not change your DNS, firewall rules, Winsock catalog, or router configuration — which are where the actual problem lives.
Does this error affect my trust factor or matchmaking rank?
The error itself does not affect trust factor. However, if you repeatedly fail to connect after accepting a match, CS2 will issue matchmaking cooldowns. Your rank (CS Rating) is unaffected unless you are disconnecting from matches you already joined, which counts as an abandon.