Still having ping spikes

Anx_iety
Anx_iety
in CrossFire Support
Before and after the latest update I have been getting these odd ping spikes that I have never gotten before. I contacted my ISP and they say there is no problem at all on my end. I'll be in the game with a nice 30 or so ping then all of a sudden during the match it spikes up to 250 and keeps doing it randomly throughout the match.

Most of you will say, hey this is your network problem. Wrong, I actually hooked it straight from the fiber optic wall outlet into my PC and I am still getting the same problems. Would like a response if possible of any kind.
Flag · Disagree Agree Like Vote Up Awesome LOL

Comments

  • iDjSatoMi
    iDjSatoMi
    Just Like Me I Have the Same Problem do you get Crossfire Send Error Report and then u Restart Crossfire and you start spiking yes?
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • [Greycloak]
    [Greycloak]
    Regardless of how well connected your internal network is, once data leaves your computer it will travel through dozens of routers before it reaches it's destination. Unfortunately sometimes packets get routed through congested networks, which can cause higher latency (ping). Try this:

    - Open a command prompt
    - XP: Start menu, run, CMD
    - Vista: Type CMD in the search on your start menu
    - In the command prompt type: IPCONFIG
    - Take note of the value listed next to Default Gateway
    - At the command prompt type: PING x.x.x.x -n 20 (where x.x.x.x is the default gateway)

    This tests the latency between your computer and your router/modem. If you see the response time spike, then it's a problem there. Otherwise it's most likely just a case of bad routing on the internet.
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Giggletron
    Giggletron
    i spike all the time

    and according to what you said grey my routers fine
    ill ping the servers and see what happens

    EDIT: pinged the UK server and got 13ms

    so why am i getting 50-90 o_0
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    [MOD]Greycloak wrote: »
    Regardless of how well connected your internal network is, once data leaves your computer it will travel through dozens of routers before it reaches it's destination. Unfortunately sometimes packets get routed through congested networks, which can cause higher latency (ping). Try this:

    - Open a command prompt
    - XP: Start menu, run, CMD
    - Vista: Type CMD in the search on your start menu
    - In the command prompt type: IPCONFIG
    - Take note of the value listed next to Default Gateway
    - At the command prompt type: PING x.x.x.x -n 20 (where x.x.x.x is the default gateway)

    This tests the latency between your computer and your router/modem. If you see the response time spike, then it's a problem there. Otherwise it's most likely just a case of bad routing on the internet.

    i didnt understand i have the same problem never happened before but i didnt understand what u said i am not from USA , canada or england so can u tell it more specified?
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    what is should say? Microsoft Windows [Έκδοση 6.0.6002]
    Πνευματικά δικαιώματα (c) 2006 Microsoft Corporation. Με επιφύλαξη κάθε νόμιμου
    δικαιώματος.

    C:\Users\Victor>IPCONFIG

    Ρύθμιση παραμέτρων IP των Windows


    Προσαρμογέας ασύρματου δικτύου LAN Σύνδεση ασύρματου δικτύου:

    Επίθημα DNS συγκεκριμένης σύνδεσης:
    Διεύθυνση IPv6 τοπικής σύνδεσης . : fe80::d53c:b9b7:7745:2c76%11
    Διεύθυνση IPv4. . . . . . . . . . : 192.168.0.2
    Μάσκα υποδικτύου. . . . . . . . . : 255.255.255.0
    Προεπιλεγμένη πύλη . . . . . . . : xx.x.x.xx.

    Προσαρμογέας Ethernet Τοπική σύνδεση:

    Κατάσταση μέσου . . . . . . . . . : Έχει αποσυνδεθεί
    Επίθημα DNS συγκεκριμένης σύνδεσης:

    Προσαρμογέας διοχέτευσης Σύνδεση τοπικού δικτύου*:

    Κατάσταση μέσου . . . . . . . . . : Έχει αποσυνδεθεί
    Επίθημα DNS συγκεκριμένης σύνδεσης:

    Προσαρμογέας διοχέτευσης Σύνδεση τοπικού δικτύου* 6:

    Κατάσταση μέσου . . . . . . . . . : Έχει αποσυνδεθεί
    Επίθημα DNS συγκεκριμένης σύνδεσης:

    Προσαρμογέας διοχέτευσης Σύνδεση τοπικού δικτύου* 7:

    Κατάσταση μέσου . . . . . . . . . : Έχει αποσυνδεθεί
    Επίθημα DNS συγκεκριμένης σύνδεσης:

    Προσαρμογέας διοχέτευσης Σύνδεση τοπικού δικτύου* 11:

    Κατάσταση μέσου . . . . . . . . . : Έχει αποσυνδεθεί
    Επίθημα DNS συγκεκριμένης σύνδεσης:

    C:\Users\Victor>PING x.x.x.x.x -n 20

    Εκτελείται η λειτουργία Ping στο x.x.x..x.x με 32 byte δεδομένων:
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=3ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=4ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=3ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=2ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64

    Στατιστικά στοιχεία Ping για 192.168.0.1:
    Πακέτα: Απεσταλμένα = 20, Ληφθέντα = 20, Απολεσθέντα = 0 (απώλεια 0%),
    Πλήθος διαδρομών αποστολής και επιστροφής κατά προσέγγιση σε χιλιοστά του
    δευτερολέπτου:
    Ελάχιστο = 1ms, Μέγιστο = 4ms, Μέσος όρος = 1ms
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    BUMP BUMP BUMP GREY watch that is it fine?
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    GREYGLOACK GREYGLOACKGREYGLOACK GREYGLOACK GREYGLOACK Come here dude LOL!
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Anx_iety
    Anx_iety
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Administrator>ping 192.168.1.1 -n 20

    Pinging 192.168.1.1 with 32 bytes of data:

    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

    Ping statistics for 192.168.1.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    There is my results, nothing wrong specifically on my end and I do understand about how internet goes and that it can be a number of problems.

    Does anyone have the ip address to the login server so I can test that much? Would prefer the IP address of alpha or delta server but I understand if there is no way no one can tell me that.
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • [Greycloak]
    [Greycloak]
    You can find some of that information in your version.ini file.

    The next thing I would recommend trying is to go to whatismyip.com, which will tell you your external IP address. Run that same ping command on that address as well. This will test the connection between your router and modem. The next step after that would be to find the IP address of your ISP and ping them.

    I was helping someone from Brazil once, and the ping to his router was fine and so was the ping to his modem. However, between his modem and ISP there were massive ping spikes. Obviously in cases like that it's out of the user's control and needs to be addressed by the ISP.
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Anx_iety
    Anx_iety
    Ok here is a tracert to server 1 according to the version.ini file. I can see some definite problems in there but I don't even know if it is possible to solve this on my own. I know that I have 2 World of Warcrafts running at the time of this tracert which could make the pings a little higher than normal so keep that in mind. It just wouldn't make the time outs like they are now.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Administrator>tracert 74.200.6.133

    Tracing route to 133.6.200-74.q9.net [74.200.6.133]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms Hidden for privacy.
    2 22 ms 28 ms 20 ms Hidden for privacy.
    3 30 ms 58 ms 78 ms frtc-rt1.mis.net [69.176.32.1]
    4 * 45 ms 39 ms 10.10.100.1
    5 42 ms 78 ms 39 ms lexmain.mis.net [204.68.228.254]
    6 29 ms 58 ms 59 ms 12.88.132.21
    7 42 ms 58 ms 58 ms cr81.mmptn.ip.att.net [12.122.112.30]
    8 60 ms 58 ms 59 ms cr1.sl9mo.ip.att.net [12.122.85.161]
    9 61 ms 57 ms 59 ms cr2.sl9mo.ip.att.net [12.122.2.218]
    10 61 ms 58 ms 59 ms cr2.cgcil.ip.att.net [12.122.2.21]
    11 41 ms 58 ms 58 ms gar3.chail.ip.att.net [12.122.132.101]
    12 * * * Request timed out.
    13 42 ms 58 ms 59 ms newcore1-chicagocp_xe-4-0-0_0.net.bell.ca [64.23
    0.186.105]
    14 62 ms 58 ms 59 ms core3-toronto47_POS0-2-0-0.net.bell.ca [64.230.1
    86.125]
    15 88 ms 62 ms 60 ms agg1-toronto47_xe-5-0-0_core.net.bell.ca [64.230
    .161.122]
    16 72 ms 58 ms 59 ms dis2-malton22_5-0-0.net.bell.ca [64.230.134.106]

    17 73 ms 59 ms 58 ms 67.69.228.202
    18 72 ms 58 ms 58 ms dist1-2.brm2-f1.q9.net [74.200.14.24]
    19 71 ms 58 ms 79 ms dist1-2-g-access1-2.brm2.q9.net [74.200.10.122]

    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    How about we make a server in Kentucky, like a couple miles from me lol.
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    Microsoft Windows [Έκδοση 6.0.6002]
    Πνευματικά δικαιώματα (c) 2006 Microsoft Corporation. Με επιφύλαξη κάθε νόμιμου
    δικαιώματος.

    C:\Users\Victor>ping My ping

    Εκτελείται η λειτουργία Ping στο 79.103.170.95 με 32 byte δεδομένων:
    Απάντηση από: 79.103.170.95: bytes=32 χρόνος=2ms TTL=64
    Απάντηση από: 79.103.170.95: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 79.103.170.95: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 79.103.170.95: bytes=32 χρόνος=1ms TTL=64

    Στατιστικά στοιχεία Ping για x.x.x.xx. (MY IP)
    Πακέτα: Απεσταλμένα = 4, Ληφθέντα = 4, Απολεσθέντα = 0 (απώλεια 0%),
    Πλήθος διαδρομών αποστολής και επιστροφής κατά προσέγγιση σε χιλιοστά του
    δευτερολέπτου:
    Ελάχιστο = 1ms, Μέγιστο = 2ms, Μέσος όρος = 1ms

    C:\Users\Victor>ping ***x.x.x.x ISP IP

    Εκτελείται η λειτουργία Ping στο 192.168.0.1 με 32 byte δεδομένων:
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64
    Απάντηση από: 192.168.0.1: bytes=32 χρόνος=1ms TTL=64

    Στατιστικά στοιχεία Ping για ISP PING
    Πακέτα: Απεσταλμένα = 4, Ληφθέντα = 4, Απολεσθέντα = 0 (απώλεια 0%),
    Πλήθος διαδρομών αποστολής και επιστροφής κατά προσέγγιση σε χιλιοστά του
    δευτερολέπτου:
    Ελάχιστο = 1ms, Μέγιστο = 1ms, Μέσος όρος = 1ms

    C:\Users\Victor>
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Anx_iety
    Anx_iety
    Any mods willing to help please? I posted the tracert.
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Anx_iety
    Anx_iety
    I just did another ping test and I called my ISP.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Administrator>tracert 74.200.6.133

    Tracing route to 133.6.200-74.q9.net [74.200.6.133]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms
    2 21 ms 19 ms 19 ms
    3 39 ms 39 ms 38 ms frtc-rt1.mis.net [69.176.32.1]
    4 * * 36 ms 10.10.100.1
    5 99 ms 82 ms 34 ms lexmain.mis.net [204.68.228.254]
    6 34 ms 39 ms 39 ms 12.88.132.21
    7 61 ms 118 ms 58 ms cr81.mmptn.ip.att.net [12.122.112.30]
    8 64 ms 56 ms 58 ms cr1.sl9mo.ip.att.net [12.122.85.161]
    9 42 ms 58 ms 58 ms cr2.sl9mo.ip.att.net [12.122.2.218]
    10 43 ms 58 ms 59 ms cr2.cgcil.ip.att.net [12.122.2.21]
    11 42 ms 59 ms 58 ms gar3.chail.ip.att.net [12.122.132.101]
    12 * * * Request timed out.
    13 51 ms 58 ms 58 ms newcore1-chicagocp_xe-4-0-0_0.net.bell.ca [64.23
    0.186.105]
    14 57 ms 58 ms 59 ms core3-toronto47_POS0-2-0-0.net.bell.ca [64.230.1
    86.125]
    15 62 ms 58 ms 73 ms agg1-toronto47_xe-5-0-0_core.net.bell.ca [64.230
    .161.122]
    16 95 ms 64 ms 59 ms dis2-malton22_5-0-0.net.bell.ca [64.230.134.106]

    17 62 ms 58 ms 59 ms 67.69.228.202
    18 75 ms 58 ms 59 ms dist1-2.brm2-f1.q9.net [74.200.14.24]
    19 63 ms 58 ms 58 ms dist1-2-g-access1-2.brm2.q9.net [74.200.10.122]

    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    They said it is absolutely not their fault but I think they are full of **** honestly because if you look at the recent tracert it shows it timing out on #4 which is right before it hits the main server for my internet connection. To me this doesn't seem right.

    Lol, is there a possible way for me to make my very own path to the server by choosing the way it goes? Probably not but thought I'd ask to be certain. Seems I have the most trouble with ATT servers than any (I'm not even on ATT).
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    what did u press in the CMD?
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • ]Karl
    ]Karl
    Australian server

    how bout they make an Australian server and then no more lagging for me and others
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    karlthepro1 wrote: »
    how bout they make an Australian server and then no more lagging for me and others
    shut up we are talking about spike lags any mod here plz!
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • Giggletron
    Giggletron
    connection on my router and modem are fine.... running a tracert now...

    EDIT:


    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Tom>ping REMOVED

    Pinging REMOVED: with 32 bytes of data:
    Reply from REMOVED: bytes=32 time<1ms TTL=64
    Reply from REMOVED: bytes=32 time<1ms TTL=64
    Reply from REMOVED: bytes=32 time<1ms TTL=64
    Reply from REMOVED: bytes=32 time<1ms TTL=64

    Ping statistics for REMOVED:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


    These are the results of the modem test... everything seems fine

    C:\Users\Tom>tracert 149.7.36.237

    Tracing route to 149.7.36.237 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 10 ms 24 ms 9 ms 10.69.248.1
    3 7 ms 16 ms 7 ms watf-cam-1a-ge912.network.virginmedia.net [80.3.
    2.41]
    4 8 ms 60 ms 31 ms watf-core-1a-ge-010-0.network.virginmedia.net [1
    95.182.174.9]
    5 10 ms 20 ms 24 ms brnt-bb-1a-ge-320-0.network.virginmedia.net [212
    .43.162.138]
    6 85 ms 48 ms 22 ms brnt-bb-1b-ae0-0.network.virginmedia.net [213.10
    5.174.226]
    7 26 ms 119 ms 114 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.
    185.74]
    8 59 ms 28 ms 103 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15
    .69]
    9 208 ms 149 ms 81 ms te4-3.mpd01.lon01.atlas.cogentco.com [130.117.3.
    189]
    10 33 ms 49 ms 67 ms 149.6.184.130
    11 219 ms 20 ms 68 ms 149.7.36.237

    Trace complete.

    These are the results of tracing the UK server..... seems to spike straight away and gradually getting worse... :/
    Flag · Disagree Agree Like Vote Up Awesome LOL
  • DeathB0dy
    DeathB0dy
    Any mod hereeeeeeeeeeeeeeeeee!!!!?????????
    Flag · Disagree Agree Like Vote Up Awesome LOL

Categories