Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://steamcommunity.com/sharedfiles/filedetails/?id=143962136
The reason is because you don't actually connect to the official servers, you connect to a "steam datagram relay" node. Then valve forward it within their own network to the server. This was apparently to cut down on DDoS (if no-one knows the server IP, or the player IP, or which relay cluster a player is connected to, it makes the DDoS process pretty much a lot harder).
So, how to find out the relay cluster node IP? That's quite easy. When you exit a game a load of text will be dumped to the console. One of those lines will be like this:
Primary router: xxx#nn (1.2.3.4:270xx) Ping = 1+2=3 (front+back=total)
xxx will be the relay cluster (they are mostly identified by airport IATA codes). #nn is presumably the node within the cluster (no idea if it is or not, it's my guess). What you want is the number in the brackets, which I made 1.2.3.4. There will be a number here, and that will be the datagram node you're connected to.
EDIT:
You can also yell at your ISP and say you are losing packets, it will make them check what's wrong on their end :>
If it's an ongoing problem, then roll with that relay IP you got and send them the trace results. And of course, good luck.