+ Reply to Thread
Results 1 to 5 of 5

Thread: Ping problem

  1. #1
    Junior Member spiderbot is on a distinguished road
    Join Date
    Dec 2011
    Posts
    6

    Ping problem

    Before 4 days my ping in Singapore server was 125. Some day before when quake live took 5 minutes for updates regarding maintenance and after that my ping is 330 till today i dint get a server with ping less than 200 !. So please i request quake live to solve this PING PROBLEM @

  2. #2
    Senior Member Ikaruga is on a distinguished road
    Join Date
    Aug 2010
    Posts
    283
    I think you should also write to your ISP about this and explain that things were much better a short time ago, and don't forget to include a traceroute and a ping in the letter, something like this:

    Code:
    C:\Users\ika>tracert 216.12.220.165
    
    Tracing route to 165.220.12.216.hypernia.com [216.12.220.165]
    over a maximum of 30 hops:
    
      1     8 ms    10 ms     8 ms  *
      2     9 ms    10 ms     8 ms  *
      3    38 ms    39 ms    38 ms  *
      4    39 ms    37 ms    38 ms  84.116.132.201
      5    38 ms    37 ms    36 ms  84.116.132.81
      6    38 ms    36 ms    36 ms  84.116.132.238
      7    78 ms   248 ms   257 ms  te13-4.br02.ldn01.pccwbtn.net [195.66.236.167]
      8   307 ms   307 ms   308 ms  63-218-213-174.static.pccwglobal.net [63.218.213.174]
      9   297 ms   296 ms   299 ms  ae6.dar01.sr03.sng01.networklayer.com [50.97.18.201]
     10   303 ms   305 ms   321 ms  po1.fcr01.sr03.sng01.networklayer.com [174.133.118.131]
     11   296 ms   298 ms   298 ms  165.220.12.216.hypernia.com [216.12.220.165]
    
    Trace complete.
    
    C:\Users\ika>ping 216.12.220.165 -n 20
    
    Pinging 216.12.220.165 with 32 bytes of data:
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=299ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=298ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=298ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=298ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=299ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=296ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=297ms TTL=51
    Reply from 216.12.220.165: bytes=32 time=299ms TTL=51
    
    Ping statistics for 216.12.220.165:
        Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 296ms, Maximum = 299ms, Average = 297ms
    
    C:\Users\ika>

  3. #3
    Senior Member megaman3 is on a distinguished road
    Join Date
    Dec 2011
    Posts
    1,204
    net_restart console command is the best thing since bread. It completely solves my routing issues in one second, repeat if it doesn't work.

  4. #4
    Senior Member Ikaruga is on a distinguished road
    Join Date
    Aug 2010
    Posts
    283
    Quote Originally Posted by YMCMB View Post
    net_restart console command is the best thing since bread. It completely solves my routing issues in one second, repeat if it doesn't work.
    I highly doubt that net_restart could fix routing issues, but it does something with QL indeed. For example, I still having this for years now, and nobody can tell me what's causing it. (note: it's a video from 2010, I have no idea why Youtube shows 2012)

  5. #5
    Senior Member megaman3 is on a distinguished road
    Join Date
    Dec 2011
    Posts
    1,204
    Quote Originally Posted by Ikaruga View Post
    I highly doubt that net_restart could fix routing issues, but it does something with QL indeed. For example, I still having this for years now, and nobody can tell me what's causing it. (note: it's a video from 2010, I have no idea why Youtube shows 2012)
    That's exactly what happens. No idea if it is routing, artificial lag or whatever, but the game feels much less lagged out afterwards (80 to 40 in netgraph) so it works.

+ Reply to 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