ping for 100 packets and an MTR report (mtr -rwc 100 203.0.113.10 on Linux, WinMTR or pathping on Windows) from your computer to the server, and a second report from the server back to your IP. Loss or a latency jump that starts at one hop and continues to the end shows where the problem is.
Before you start
- Note your server’s public IP. On a VPS it’s on the Network tab of the panel: see find your VPS’s IP address.
- Run the tests while the lag is happening. A report from a quiet moment shows a healthy path.
- Latency is the time a packet takes to reach the server and come back (round-trip time), measured in milliseconds (ms). Packet loss is the share of packets that never come back. Jitter is how much latency varies.
Is it the network or the server?
A busy server feels like a slow network. Before you test the path, log in and check CPU, memory and disk load withhtop or uptime (see load average), or the VPS Panel resource graphs. If CPU is at 100% or the server is swapping, fix that first.
Also compare with another destination. If every site is slow from your computer, the problem is probably your own connection or Wi-Fi.
How to measure latency with ping
ping sends small test packets and shows the round-trip time of each.
- Linux / macOS
- Windows
Some servers don’t answer ping because the firewall blocks ICMP (the protocol ping uses). On Windows Server you may need to allow it first: see how to enable ICMP on Windows. No reply doesn’t always mean the server is down.
How to run an MTR report
MTR combines ping and traceroute: it sends packets to every router (hop) on the path and shows loss and latency for each. Run at least 100 cycles so the numbers mean something.- Ubuntu / Debian
- AlmaLinux / Rocky
- Windows
-r prints a report instead of the live screen, -w keeps long hostnames, and -c 100 sends 100 cycles. Add -n to skip name lookups, or -T -P 443 to test with TCP to port 443 when ICMP is filtered somewhere on the path.
How to test the other direction
The route back from the server to you is often different. Log in to the server (SSH or Remote Desktop) and run the same test towards your home public IP, for examplemtr -rwc 100 198.51.100.25. Lag that only appears in one direction usually points to that return path.
How to read the results
In the example, hop 3 shows 60% loss but the later hops show 0%. That router is only limiting replies to test packets, which is normal and harmless. Only loss or latency that carries through to the final hop affects your connection.
Where is the problem?
How to send results to support
Open a ticket with both MTR reports (to and from the server) as plain text, the time you ran them with your time zone, and your public IP. Reports taken during the lag are the most useful.Frequently asked questions
What is a good ping to a server?
It depends mostly on the physical distance between you and the server: a server on another continent always has a higher ping than one nearby. For games and remote desktops, steady times with no loss matter more than the lowest number.Why does traceroute show * * * or “Request timed out”?
That hop doesn’t answer test packets or limits how fast it answers. If the later hops and the destination reply, you can ignore it.
Can low bandwidth cause high latency?
Yes. When a link is full, packets queue and latency rises. Test throughput with iperf3 and check bandwidth usage on the server.Related guides
VPS and dedicated server guides
Every guide in this section.
Run MTR and traceroute
All options and output explained.
Test speed with iperf3
Measure throughput between two hosts.
Check if a port is open
Test a service from outside.
Enable BBR
Better TCP throughput on long paths.
Monitor VPS resources
Rule out a busy server.
Checked against the mtr man page and Microsoft Learn (pathping, tracert) on 4 November 2026; Linux commands tested on Ubuntu 24.04 LTS (mtr 0.95). Commands can differ on other distributions or releases.
Need Extra Help?
If you encounter any issues, our support team is ready to assist:- Live Chat: Quick assistance via our website.
- Support Ticket: Open a Ticket
- Discord: Join our Community
- Email: support@freakhosting.com
Last Updated: November 2026