If you are experiencing lag spikes, run an MTR test from your own computer to the server IP while the problem is happening. Enter the IP without the game port, turn off any VPN or proxy, and send the complete result to EnderHost support. A second affected player’s report helps us compare routes.
Timing matters: start the test during the lag spike, not only after the connection has returned to normal. Run it from the affected player’s connection rather than from the hosting server.
Before you start
- Find the server IP in your game panel or connection details.
- Remove the port. For example, if the connection address is 203.0.113.10:25565, enter only 203.0.113.10. This is an example address; use your own server IP.
- Turn off any VPN or proxy for the test so the report reflects the direct route from your connection.
- If possible, ask another affected player to run the same test at the same time.
Run WinMTR on Windows
Open the WinMTR download and setup guide from xneelo and follow its Windows download instructions.
- Download and extract WinMTR, then open the version that matches your Windows system.
- Enter your server IP in the Host field. Do not include a port, https://, or any other URL text.
- Click Start while you are experiencing the lag spike. Leave the test running through the affected period; a few minutes is more useful than a single moment.
- Click Stop after you have captured the issue.
- Copy or export the full output as text, or take a screenshot showing all hops and the result columns.
Send us the results
Reply in your existing support conversation with the screenshot or pasted text. Include the details below so we can match the report to the incident:
- The server IP you tested and which service or game was affected.
- When the spike happened, including your time zone, and whether it is still happening.
- What you experienced: high ping, rubber-banding, disconnects, delayed actions, or another symptom.
- Whether you used Wi-Fi or a wired connection, and confirmation that your VPN/proxy was off.
- The second player’s report, if available. Keep the two reports labeled so we can compare them.
Need to start a support conversation? Join EnderHost on Discord and share the report with our support team.
What happens next?
We use the reports to investigate the connection path and compare affected players. For help interpreting the output, read how to read MTR results. Please send the complete trace rather than only the hop that looks unusual.
MTR investigates the network path. If the issue is slow Minecraft ticks, we may also request a Spark profile. Our latency and lag guide explains the distinction, and the Spark analyzer helps review server performance metrics.
Sources and references
Hosting documentation. Publication and update dates reflect this edition.
Related articles
- How to Read MTR Results Without Mistaking ICMP Loss for an OutageSeparate router reply limits from end-to-end loss and collect a useful network report for a hosting investigation.3 min read
- Diagnosing latency and lagTell a network problem apart from a server performance problem.1 min read
- What Are Minecraft TPS and MSPT?Read tick rate and tick duration together to distinguish sustained server lag, brief stalls and network delay.3 min read
