+ Reply to Thread
Results 1 to 9 of 9

Thread: Ping yeah!

  1. #1
    Junior Member jincho_pez is on a distinguished road
    Join Date
    Aug 2010
    Posts
    7

    Ping yeah!

    Hello, I'm just curious, it looks that 6 months (approx.) I get a nice 50-60 ping in Dallas, TX servers, and the other half of the year it goes up to 90. It has happened all the time since I've been here, which might be a little more than 2 years.

    So, it's my ISP that changes locations of something? Or it's QL's rout... some... thing? Pingtest says I should be getting 53 ms.

    I live in Mexico by the way, and yes, I love tacos.

  2. #2
    Senior Member pikaluva13 will become famous soon enough pikaluva13's Avatar
    Join Date
    Aug 2010
    Location
    East Lansing, MI
    Posts
    6,206
    Pingtest isn't accurate at all when it comes to determining routing in QL.

    It could either be ISP-related or it could be the overall servers, but since 100% of the people don't have the same issue, it's more likely to be on your end. It could even be in your router. I'd suggest looking at a command prompt and trying "/tracert 69.174.243.26" (A TX CTF server)

    Let me know what the results are.

  3. #3
    Junior Member jincho_pez is on a distinguished road
    Join Date
    Aug 2010
    Posts
    7
    Traza a 69.174.243.26 sobre caminos de 30 saltos como máximo.

    1 10 ms 11 ms 9 ms 10.45.0.1
    2 11 ms 10 ms 31 ms 10.0.92.62
    3 11 ms 9 ms 9 ms 10.2.92.195
    4 9 ms 10 ms 11 ms pe-puebla.megared.net.mx [189.199.117.81]
    5 31 ms 33 ms 32 ms 10.3.0.165
    6 32 ms 41 ms 35 ms 10.3.0.117
    7 33 ms 35 ms 33 ms 201-174-24-225.transtelco.net [201.174.24.225]
    8 43 ms 57 ms 49 ms 201-174-0-189.transtelco.net [201.174.0.189]
    9 69 ms 57 ms 57 ms 201-174-0-205.transtelco.net [201.174.0.205]
    10 74 ms 73 ms 77 ms 201-174-0-210.transtelco.net [201.174.0.210]
    11 78 ms 77 ms 79 ms peer1.com.any2ix.coresite.com [206.223.143.79]
    12 76 ms 76 ms 76 ms 10ge.ten1-1.la-600w-cor-2.peer1.net [216.187.88.
    146]
    13 77 ms 77 ms 77 ms 10ge-ten1-2.dal-eqx-cor-1.peer1.net [216.187.124
    .122]
    14 84 ms 83 ms 86 ms 10ge-ten1-2.sat-8500v-cor-1.peer1.net [216.187.1
    24.78]
    15 90 ms 92 ms 89 ms 10ge.xe-0-0-1.sat-8500v-sbdis-1.peer1.net [216.1
    87.124.66]
    16 85 ms 85 ms 84 ms 69.174.243.26

    Traza completa.




    I should get a cool signature sometime soon. How's it looking doctor? Are those nasty looking numbers?

  4. #4
    Senior Member pikaluva13 will become famous soon enough pikaluva13's Avatar
    Join Date
    Aug 2010
    Location
    East Lansing, MI
    Posts
    6,206
    There's nothing that stands out as to being "bad" in there (No random 200ms or anything) so it's probably just ISP-related.

    (In case anyone reading this doesn't know, I know very little about routing :P)

  5. #5
    Senior Member Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa's Avatar
    Join Date
    Aug 2010
    Location
    Kepler-22b
    Posts
    8,905
    peer1 has been unstable recently..

  6. #6
    Senior Member SHAKEANDBAKE has a little shameless behaviour in the past
    Join Date
    Aug 2010
    Location
    ontario
    Posts
    307
    There's something better than traceroute. Try pingplotter, its free. it gives you real time ping, over and over and plots it for you.

  7. #7
    Senior Member pikaluva13 will become famous soon enough pikaluva13's Avatar
    Join Date
    Aug 2010
    Location
    East Lansing, MI
    Posts
    6,206
    Quote Originally Posted by SHAKEANDBAKE View Post
    There's something better than traceroute. Try pingplotter, its free. it gives you real time ping, over and over and plots it for you.
    Unless it's changed fairly recently, it never worked well for myself. It tended to give approximates. However, the tracert can show if the increase is due to something from your end, or if it's somewhere else down the line. PigPlotter does the same thing as joining a server and checking your ping

  8. #8
    *Vedmedik
    Guest
    Hmmm, I time out on hops 11 and 12


    Tracing route to 69.174.243.26 over a maximum of 30 hops

    1 1 ms <1 ms <1 ms DREAMERK [192.168.1.1]
    2 32 ms 19 ms 31 ms cpe-70-116-128-1.tx.res.rr.com [70.116.128.1]
    3 9 ms 12 ms 9 ms 70.125.216.77
    4 23 ms 21 ms 15 ms tge4-3.dllatx40-tr01.texas.rr.com [24.175.38.74]

    5 14 ms 15 ms 15 ms be26.dllatx1k-cr01.texas.rr.com [24.175.36.208]

    6 21 ms 17 ms 23 ms agg21.dllatxl3-cr01.texas.rr.com [24.175.49.0]
    7 20 ms 19 ms 15 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
    8 16 ms 17 ms 30 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
    9 16 ms 15 ms 18 ms te-0-15-0-1-pe01.1950stemmons.tx.ibone.comcast.n
    et [173.167.57.117]
    10 20 ms 18 ms 17 ms 173.167.58.14
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 32 ms 30 ms 34 ms 69.174.243.26

  9. #9
    Senior Member Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa's Avatar
    Join Date
    Aug 2010
    Location
    Kepler-22b
    Posts
    8,905
    If it always times out on those, it may mean that they have a firewall that refuses tracert packets, which is becoming more and more common these days.

    Ping plotter might be able to get around this, I don't know I've never used it :-/

+ Reply to Thread

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts