EnterraHost
Where the jump happens
Read down the times. A hop that is a few milliseconds slower than the one before it is normal. A hop that adds 150 ms in one step is the link worth asking about.
Find out where the time actually goes. A ping says the trip takes 190 ms. A traceroute shows you which network added it.
Reading a trace
Read down the times. A hop that is a few milliseconds slower than the one before it is normal. A hop that adds 150 ms in one step is the link worth asking about.
The three probes per hop show consistency. Tight numbers mean a stable link. Numbers that swing mean congestion, and congestion is what makes a connection feel unreliable.
Each hop is labeled with the network that announces it. That turns a complaint into a specific question aimed at the right operator rather than at nobody in particular.
Common confusion
Routers routinely refuse to answer probes aimed at themselves while forwarding your traffic without complaint. A blank hop in the middle of an otherwise working trace is not a fault.
If the target is behind a CDN, the trace finishes at the edge nearest you and never reaches the origin. That is the design working correctly, not the trace failing.
Next
If the path looks clean and the delay is still there, the network is not the problem. The next thing to check is the server itself and the certificate it presents.