Posted below are the traceroute results:
Tracing route to domain.com [2401:7400:8000:0:4:0:80c7:de5f]
over a maximum of 30 hops:
1 10 ms 2 ms 8 ms 2401:7400:6002:47f9:100c:6fd8:d267:ba1c
2 * * * Request timed out.
3 34 ms 42 ms 39 ms 2401:7400:200:3::3
4 65 ms 104 ms 108 ms 2401:7400:8888:2::6
5 71 ms 72 ms 59 ms 2401:7400:8888:21::6
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 49 ms 28 ms 24 ms 2401:7400:8000:0:4:0:80c7:de5f
I have no idea what to do next, please do advise. Currently routing through Cloudflare.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hi there,
The traceroute results you provided show the path that a packet of data takes from your computer to the destination server (in this case, domain.com). Each line of the traceroute represents a “hop” or step along that path. When you see a line with “* * * Request timed out”, it means that a particular step didn’t respond in a timely manner.
In your case, it looks like the packet successfully made its way to the destination server (last hop), despite the time outs in hops 6 to 10. These timed out hops might belong to networks that either have ICMP blocked or have firewall rules that are dropping the ICMP echo requests, which are needed for traceroute. This is a common security measure and doesn’t necessarily indicate a problem.
If you’re not experiencing any issues (slow connections, intermittent connectivity, etc.), then there’s likely nothing to worry about.
However, if you’re experiencing issues with reaching the domain or the domain’s services:
A few timeouts in a traceroute do not necessarily indicate a problem, especially if you can still reach the destination server successfully.
Best,
Bobby