Counter-Strike throws a "cannot connect" or queue stalls and the first question is always the same: is it me or is it them? Here is how to tell in under a minute, and what to do about regional weirdness that is neither.
The quick checks
Steam status first. steamstat.us tracks Steam and CS2 services — matchmaking, inventory, community, the session servers. If the whole board is red, close the game and do something else, it is not your setup.
Downdetector for the crowd signal. A spike of thousands of reports in ten minutes means a real outage. A flat line means the problem is closer to home.
Your own region. CS2 matchmaking runs through regional relays. Middle East players specifically hit this constantly: the nearest official relays can be far away, routing through whatever the ISP's transit decides that evening. Steam status can be green while your region's relays are degraded. ping and tracert to the relay addresses, or check community Discords for your region — if everyone in ME is lagging at once, it is the relay path, not your PC.
When it is you
If global status is green and the crowd is quiet: verify game files, check your firewall did not eat the Steam client after an update, restart the router if your NAT type went strict. Packet loss to the relay matters more than raw ping — 40 ms with 5% loss plays worse than 90 ms clean.
If you run the server instead of playing on it
Community server owners have the inverse problem: you need to know before the players do that your server died, map vote crashed, or the game port stopped responding. Players do not file tickets, they just leave. A game-server monitor checks the actual query port the way the server browser does, from outside your network, and pages you the minute it stops answering — which beats finding out from an empty server list an hour later.