Tracert for UK Server ?

Can You give an IP for UK Serv to check it by tracert like before ? I'm living in Ireland and my ping is like 150 (!). I want to fix that and shows that to my ISP provider. Cause Im sure this is their fault.

Comments

  • where rae u from and why need tracert ? u have lag ?
  • Cris7712 wrote: »
    Can You give an IP for UK Serv to check it by tracert like before ? I'm living in Ireland and my ping is like 150 (!). I want to fix that and shows that to my ISP provider. Cause Im sure this is their fault.

    my ping keeps spiking too

    what ISP are you with?
    theres the IP anyway

    149.7.36.237
  • Thank You Giggletron. ISP - Eircom (...)
    And I can tell that they are worst ISP that I've ever faced.

    Here are results for ping and tracert:

    C:\>ping -n 20 149.7.36.237

    Pinging 49.7.36.237 with 32 bytes of data:
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=157ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=155ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=156ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=154ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118
    Reply from 149.7.36.237: bytes=32 time=153ms TTL=118

    Ping statistic for 149.7.36.237:
    Pakcets: Sent = 20, Received = 20, Lost = 0
    (0% loss),
    Approximate:
    Minimum = 153 ms, Maximum = 157 ms, Average = 153 ms

    C:\>tracert 149.7.36.237

    Tracing route to 149.7.36.237 over a maximum of 30 hops.

    1 2 ms 1 ms 2 ms 192.168.1.254
    2 24 ms * 10 ms b-ras1.lmk.limerick.eircom.net [159.134.155.24]

    3 9 ms 8 ms 8 ms 86.43.244.253
    4 84 ms 80 ms 81 ms 83.71.115.146
    5 82 ms 83 ms 84 ms te2-4.ccr01.jfk07.atlas.cogentco.com [38.104.67.5]
    6 79 ms 79 ms 80 ms te0-3-0-1.mpd21.jfk02.atlas.cogentco.com [154.54.1.133]
    7 153 ms 151 ms 151 ms te2-4.mpd02.lon01.atlas.cogentco.com [130.117.1.106]
    8 155 ms 155 ms 155 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2.17]
    9 155 ms 156 ms 156 ms 149.6.184.130
    10 154 ms 153 ms 154 ms 149.7.36.237

    Trace complete.
  • Giggletron wrote: »
    my ping keeps spiking too

    what ISP are you with?
    theres the IP anyway

    149.7.36.237
    No .
  • Tracert

    I have this same problem cuz i live in ireland then when i play c.s.s europe my ping is 40 or less it's because our routers are taking the wrong route to the uk servers but i don't know how to fix it
  • Giggletron wrote: »
    my ping keeps spiking too
    what ISP are you with?
    theres the IP anyway
    149.7.36.237

    Thanks for posting IP, i have to do something with that too... Ping increasing very often from 42 - 138, way too much :-S
  • Cris7712 wrote: »
    C:\>tracert 149.7.36.237

    Tracing route to 149.7.36.237 over a maximum of 30 hops.

    1 2 ms 1 ms 2 ms 192.168.1.254
    2 24 ms * 10 ms b-ras1.lmk.limerick.eircom.net [159.134.155.24]

    3 9 ms 8 ms 8 ms 86.43.244.253
    4 84 ms 80 ms 81 ms 83.71.115.146
    5 82 ms 83 ms 84 ms te2-4.ccr01.jfk07.atlas.cogentco.com [38.104.67.5]
    6 79 ms 79 ms 80 ms te0-3-0-1.mpd21.jfk02.atlas.cogentco.com [154.54.1.133]
    7 153 ms 151 ms 151 ms te2-4.mpd02.lon01.atlas.cogentco.com [130.117.1.106]
    8 155 ms 155 ms 155 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2.17]
    9 155 ms 156 ms 156 ms 149.6.184.130
    10 154 ms 153 ms 154 ms 149.7.36.237

    Trace complete.

    Obviously the problem starts to worsen around hop number 7, where it spikes from 80 to 151. That would indicate that there is a problem with the router or computer at te2-4.mpd02.lon01.atlas.cogentco.com. This is simply a case of poor internet routing, and there isn't a whole lot you can do except try to contact your ISP about it.