Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I like to play the game League of Legends but lately have gotten unacceptable amounts of latency (400+ ping). After finding out the game server's IP ( I tried to traceroute it to see if there are any problems. As it turns out, there are:


Tracing route to over a maximum of 30 hops

  1    <1 ms     1 ms     1 ms []
  2    25 ms    27 ms    25 ms []
  3    34 ms    28 ms    27 ms []
  4    43 ms    26 ms    25 ms []
  5    25 ms    53 ms    30 ms []
  6    31 ms    32 ms    37 ms []
  7    33 ms    32 ms    33 ms []
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.


 30     *        *        *     Request timed out.

Trace complete.

As you can see it never finishes. I have tried everything on my side to improve the connection, but I have ruled out everything (network card drivers, modem firmware, line issues). I have ~50 ping with any other european server, and I used to have around that with this one too. But since two weeks the latency has skyrocketed. And I'm not the only one, many (mostly italian) people report the same issue, with the same traceroute stuck on

Is there anything I can do to bypass this and get my previously good connection back?

share|improve this question
Traceroute does not always finish without timing out as some internet routers do not respond to ICMP messages. It's normal. – paradroid Apr 20 '12 at 1:38
up vote 5 down vote accepted

The only ways to change your routing to a specific destination are to use some kind of proxy or a different ISP. Routing is pretty much determined by peering arrangements between ISPs.

The fact that traceroute never ends just means that the last router or last few routers are not reporting back packet TTL expiry, it doesn't explain the overall latency (your 400ms ping).

share|improve this answer
Yes. That's a perfectly normal traceroute and doesn't indicate any problem. – David Schwartz Apr 20 '12 at 0:56

You can also request that your ISP (or Tinet) reroute your traffic using alternate ISP peers. I have done this once or twice in the past. Above, where Tracert is going to after Tinet is the ISP that is unresponsive. Ping however automatically reroutes and finds an alternate route (if any exist) to the final Destination IP. The fact that ping works means that there is a working connection.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .