Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
disable any vpn
start -> run/search -> cmd
tracert google.com
post results
first hop or two are router or modem combo, should be 0
next hop isp host, a few ms if on cable/fiber
next are in the isp network, to internet backbone and to google.com servers
the problem is where the numbers start getting bigger
tracert pings each node along the route, will show you where the lag is coming from
router is not always 192.168.1.1 many isp router use 10.0.0.1 or 192.168.random.1
ipconfig will show it, but its not needed it you use tracert
setting the router to use google and cloudfare is the best option, many times faster than isp dns repeaters
8.8.8.8 and 8.8.4.4 and 1.1.1.1
Ping is the as known as the latency or distance between you and the host. I'm assuming your router has enough bandwidth for all your devices. You can check it with a speed test, and a good speed would be a minimum of 1MBps down and 500KBps up. Assuming you have enough bandwidth and your ping-in on the speed, i.e. https://www.speedtest.net/ is still really high, check your physical location to where the hosts are located, i.e. you live in NY, but you are trying to connect to LA servers. Then, unfortunately, you are going to have high ping regardless of what you do because of the physical distance between you and the server, i.e. you live in NY, but you are trying to connect to LA servers, which is 2,789.0 mi. To counteract this, you won't have to connect to the server that is closer, i.e. one that is ideally located with 100mil of you, but whatever is closest.
1.1.1.1 and 1.0.0.1 is Cloudflare, and recommended
I use Cloudflare on my smartphones, laptops, PCs, Router, and even additionally in Firefox settings..
mobile or portable devices its a good idea to just change it on them
You're assuming those devices are configured to get their DNS from a DHCP server.
Concurred on the 1^4 recommendation. Also if you're using IPv6 as well those DNS resolvers are at
Primary: 2606:4700:4700::1111
Secondary: 2606:4700:4700::1001
Also, just because "ping" to some server on the internet is high doesn't mean there is a problem.
Depending on your OS/version; ping will be using ICMP echo messages to determine the latency. Many things including routers, DNS servers, etc. will not prioritize ICMP messages; and in fact will rate limit ICMP messages. The same goes for traceroutes; as ICMP is on the control plane which pretty much any properly configured router along the path will prioritize the data plane so where there is congestion along the path it is not uncommon to have routers ignore the ICMP echo and simply forward the traffic to the next router in the path.
On linux you can tell the ping and traceroute utilities to use UDP instead of ICMP; and you can also use mtr.
Doing a speedtest via Ookla (speedtest.net) will give you 3 bits of info
Initial latency
Jitter
and the download/upload throughput.
Jitter is the range / variance of latency measurements; which is showing the consistency of the latency (e.g. the stability/instability of the connection to their server during the test).
Without more details from the OP there really isn't any way to point them further along troubleshooting their issue, if there is one; beyond what has already been noted.
Looks like, yes. Now install latest Firmware update for your access point/router