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
Discussions Rules and Guidelines
Report this post
It’ll clear up.
Most modem/routers have some minimum level of "directed denial of service" attacks. They will refuse pings, refuse random connection attempts, refuse requests, etc..
Most commercial providers will attempt to squelch attacks if heuristics identifies them as such or they come from known vectors or have certain hallmark signatures.
"Attacks" of all sorts are endemic... At any one time at all you can likely pull up logs for your router only to see a list of suspicious connection attempts that target known vulnerabilities and certain software known to have vulnerabilities but, nonetheless, opens ports to listen for communications. It's everywhere, always - The bots are ruthless and mostly... ineffective.
It is unlikely that you were specifically signaled out by a conventional ddos attempt. Though, you would also have to know a bit about the operating environment for that game and for its connection and matchmaking schemes. I do not.
It's likely you ran afoul of general network issues involving your connection. I can't discount there wasn't some sort of attempted attack, in general, though - I do not know the environment you're experiencing. (There could be all sorts of hacking tools that exploit vulnerabilities in online game networks as those hosting them aren't focused a lot on security... You need to know about what common problems your community encounters in order to assess the likelihood an exploit/vulnerability was used. Doubtful... but it's possible.)
Typical issues are packet loss and dropped connections or connection interruptions.
(Note: A general reset of everything could clear up issues. So, reboot your modem, network, and PC. Also, it's not unusual for locally connected equipment, like your Mom's smartphone, to suddenly eat up so much bandwidth that you get your gameplay disconnected. :) Some ISP provided equipment, like a "cable TV box" can also end up eating up bandwidth even though it's not supposed to do that... (Television/media should be on a separate frequency, but a box can also end up updating its own firmware using conventional frequencies. :/))
The first thing to do is to check your connection from your PC to your router and to the modem. If you're running on wifi, I'd say that's likely the biggest failure point and the most common. If you're hardwired all the way, you need to check that pipe to be sure there's not a problem. Wires, splitters, subnets, etc.. can all cause issues even before your connection gets out into the wild.
You should check your connection from your PC through your local network and then out into the wild all the way to the service connection you're using. To do that, you'd use something like "traceroute" to check your connection to your home router, first, knowing that local IP assigned address (ie: 192.168.xxx.xxx) Then, you would need the IP of the service you're connecting to, which would be the server hosting your connection to the game. That may or may not be published, but a route to that server's base network should be discernible. You can run the game and then check for a list of open connections using "netstat." This will show a list of open connection from your PC to a list of IPs. Some of those may be "logical" IPs, but you can check the host process that called for those connections and then check those IPs to see which are owned by the game's services. You may only get a base level IP address that represents the first hop in that game hosts internal network - That is normal, to prevent exactly what you think may be happening to you. :)
By initiating a traceroute to that end-point IP, you can see the overall "health" of your connection to that game's servers. Each "hop" will return information about connectivity to that specific IP your route passes through to your game's host. Note that some IPs may not report such information. That's normal, too. However, some IPs may fail to report and the difference between those types can be difficult to discern.
You will see your connection passing through IPs belonging to your provider, then out to larger main trunks, through to your game's hosts.
What you're looking for here are unusually long response times that do not appear to be typical request refusals. If you see an unusually long response time that appears to be within your internet provider's network, that's most likely the problem. (Most of the time) Sometimes, it's another source and, if so, you may be able to look up that IP to see if there's a major internet outtage issues. (internet health reports, etc)
Note: Terms in "quotes" are there for you to look up, yourself, to learn how to use these commands. :)
PS: You can get a decently reliable assessment of your general internet connection by using your favorite "console" and using it's own network diagnostics for a one-button-checkup at the very least. It will only return a report for the connection that console is on within your network to its services host, though. If you're on a different port, it won't apply to your home network for your PC. But, it could be a quick way for you to check for common issues, like packet-loss.
https://youtu.be/u3EwUok729Y