Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
#1
Can you guys help me to find the source of the high latency in my css? Since the nonsteam update my latency lowered from a unusual 150 to my regular 77. After 2 weeks it started to get high until today i find that my latency reached the amazing 200. I was trying to find if it's my internet but apparently it isn't. The rates are exactly the same as it was when my latency was on 77, but any other config could be helpful.
[Image: 1qs5g7.png]
#2
This happened to me too, not the tomix cares, he just thinks im a kid.
Anyone wanna tell me every time when im on the popular maps 2 my latency will spike for no reason, and so does mostly everyones on the server?
"Ignorance is Bliss"- Sima Yi from DW6
#3
Say that in the correct section.
[Image: 1qs5g7.png]
#4
Apparently the only thing he focuses on is a side comment i made, and not the fact that im agreeing with him.
"Ignorance is Bliss"- Sima Yi from DW6
#5
Tracert it please. Usually when everyones ping rises the server is getting attacked.
#6
Umm which one?

Tracing route to war-lords.net [65.19.166.194]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    9 ms    29 ms    39 ms  10.48.40.21
  4    10 ms    12 ms    47 ms  201-218-92-197.cpe-statics.cableonda.net [201.21
8.92.197]
  5  105 ms  102 ms  167 ms  64.210.12.185
  6  102 ms  121 ms  130 ms  64.209.105.42
  7  124 ms  123 ms  146 ms  10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
  8  139 ms  130 ms  120 ms  10gigabitethernet1-4.core1.fmt2.he.net [72.52.92
.66]
  9  126 ms  122 ms  124 ms  v100.br2.fmt2.he.net [72.52.96.66]
10  124 ms  124 ms  123 ms  ph01.purgehosting.com [65.19.166.194]

Trace complete.

Or

Pinging war-lords.net [65.19.166.194] with 32 bytes of data:
Reply from 65.19.166.194: bytes=32 time=121ms TTL=53
Reply from 65.19.166.194: bytes=32 time=172ms TTL=53
Reply from 65.19.166.194: bytes=32 time=122ms TTL=53
Reply from 65.19.166.194: bytes=32 time=129ms TTL=53

Ping statistics for 65.19.166.194:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 121ms, Maximum = 172ms, Average = 136ms
[Image: 1qs5g7.png]
#7
One of the game servers. 173.231.20.18
#8
Pinging 173.231.20.18 with 32 bytes of data:
Reply from 173.231.20.18: bytes=32 time=154ms TTL=50
Reply from 173.231.20.18: bytes=32 time=117ms TTL=50
Reply from 173.231.20.18: bytes=32 time=117ms TTL=50
Reply from 173.231.20.18: bytes=32 time=123ms TTL=50

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


Tracing route to 173-231-20-18.hosted.static.webnx.com [173.231.20.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    30 ms    11 ms    24 ms  10.48.40.21
  4    11 ms    25 ms    12 ms  201-218-92-205.cpe-statics.cableonda.net [201.21
8.92.205]
  5  103 ms  119 ms  103 ms  64.215.185.73
  6  102 ms  102 ms  106 ms  xe3-3-0-10G.scr2.PTY2.gblx.net [67.16.132.157]
  7  106 ms  105 ms  107 ms  ae0-70G.scr3.LAX1.gblx.net [67.16.141.18]
  8  122 ms  113 ms  127 ms  e5-1-40G.ar6.LAX1.gblx.net [67.17.111.65]
  9  107 ms  108 ms  108 ms  PACKETEXCHANGE-LTD.Ethernet6-4.ar6.LAX1.gblx.net
[67.17.134.110]
10  115 ms  131 ms  119 ms  67.199.135.234
11  118 ms  130 ms  117 ms  100-42-223-150.static.webnx.com [100.42.223.150]

12  190 ms  253 ms  343 ms  100-42-223-194.static.webnx.com [100.42.223.194]

13  686 ms  446 ms  121 ms  173-231-20-18.hosted.static.webnx.com [173.231.2
0.18]

Trace complete.
[Image: 1qs5g7.png]
#9
Tomix <3 ♥Madelaine♥' Wrote:  4    11 ms    25 ms    12 ms  201-218-92-205.cpe-statics.cableonda.net [201.21
8.92.205]
  5  103 ms  119 ms  103 ms  64.215.185.73

You're getting higher than 77ms before it even hit's our network.

I am curious about this tho

Quote: 12  190 ms  253 ms  343 ms  100-42-223-194.static.webnx.com [100.42.223.194]

13  686 ms  446 ms  121 ms  173-231-20-18.hosted.static.webnx.com [173.231.2
0.18]

Can you provide some more tracerts please?

-------------------------------------------

EDIT:

traceroute to 201.218.92.205 (201.218.92.205), 30 hops max, 40 byte packets
1  108-171-197-41.static.webnx.com (108.171.197.41)  0.383 ms  0.450 ms  0.506 ms
2  100-42-223-193.static.webnx.com (100.42.223.193)  0.497 ms  0.717 ms  0.842 ms
3  100-42-223-141.static.webnx.com (100.42.223.141)  0.590 ms  0.711 ms  0.835 ms
4  te7-3.209.ccr01.lax04.atlas.cogentco.com (38.122.146.25)  0.438 ms  0.484 ms  0.491 ms
5  te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113)  13.680 ms  13.732 ms  13.884 ms
6  te0-0-0-5.ccr22.sjc01.atlas.cogentco.com (154.54.5.181)  13.489 ms  13.542 ms  13.687 ms
7  te0-0-0-2.ccr22.sjc03.atlas.cogentco.com (66.28.4.78)  13.452 ms  13.675 ms  13.771 ms
8  tiscali.sjc03.atlas.cogentco.com (154.54.13.14)  11.303 ms  11.306 ms  11.304 ms
9  ge-2-0-0.mia11.ip4.tinet.net (89.149.182.34)  78.224 ms  78.231 ms  78.320 ms
10  c-w-panama-gw.ip4.tinet.net (173.241.131.90)  131.905 ms  131.927 ms  131.981 ms
11  201.224.250.150 (201.224.250.150)  106.188 ms  106.153 ms  106.130 ms
12  201-218-92-198.cpe-statics.cableonda.net (201.218.92.198)  107.247 ms  108.057 ms  108.053 ms
13  201-218-92-205.cpe-statics.cableonda.net (201.218.92.205)  106.229 ms  106.817 ms  106.802 ms

traceroute to 201.218.92.205 (201.218.92.205), 30 hops max, 40 byte packets
1  108-171-197-41.static.webnx.com (108.171.197.41)  0.336 ms  0.400 ms  0.451 ms
2  100-42-223-193.static.webnx.com (100.42.223.193)  0.497 ms  0.641 ms  0.767 ms
3  100-42-223-141.static.webnx.com (100.42.223.141)  0.538 ms  0.684 ms  0.762 ms
4  te7-3.209.ccr01.lax04.atlas.cogentco.com (38.122.146.25)  0.432 ms  0.478 ms  0.528 ms
5  te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113)  13.733 ms  13.734 ms  14.000 ms
6  te0-0-0-5.ccr22.sjc01.atlas.cogentco.com (154.54.5.181)  13.648 ms  13.531 ms  13.771 ms
7  te0-0-0-2.ccr22.sjc03.atlas.cogentco.com (66.28.4.78)  13.516 ms  13.760 ms  13.859 ms
8  tiscali.sjc03.atlas.cogentco.com (154.54.13.14)  11.277 ms  11.273 ms  11.270 ms
9  ge-2-0-0.mia11.ip4.tinet.net (89.149.182.34)  78.162 ms  78.230 ms  78.164 ms
10  c-w-panama-gw.ip4.tinet.net (173.241.131.90)  131.833 ms  131.971 ms  132.021 ms
11  201.224.250.150 (201.224.250.150)  106.217 ms  106.171 ms  106.097 ms
12  201-218-92-198.cpe-statics.cableonda.net (201.218.92.198)  107.453 ms  108.003 ms  108.061 ms
13  201-218-92-205.cpe-statics.cableonda.net (201.218.92.205)  106.296 ms  106.295 ms  106.257 ms

traceroute to 201.218.92.205 (201.218.92.205), 30 hops max, 40 byte packets
1  108-171-197-41.static.webnx.com (108.171.197.41)  0.275 ms  0.335 ms  0.403 ms
2  100-42-223-193.static.webnx.com (100.42.223.193)  0.505 ms  0.610 ms  0.730 ms
3  100-42-223-141.static.webnx.com (100.42.223.141)  0.499 ms  0.723 ms  0.791 ms
4  te7-3.209.ccr01.lax04.atlas.cogentco.com (38.122.146.25)  0.436 ms  0.484 ms  0.532 ms
5  te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113)  13.655 ms  13.761 ms  13.764 ms
6  te0-0-0-5.ccr22.sjc01.atlas.cogentco.com (154.54.5.181)  13.463 ms  13.639 ms  13.630 ms
7  te0-0-0-2.ccr22.sjc03.atlas.cogentco.com (66.28.4.78)  13.504 ms  13.708 ms  13.778 ms
8  tiscali.sjc03.atlas.cogentco.com (154.54.13.14)  11.237 ms  11.279 ms  11.278 ms
9  ge-2-0-0.mia11.ip4.tinet.net (89.149.182.34)  78.222 ms  78.268 ms  78.183 ms
10  c-w-panama-gw.ip4.tinet.net (173.241.131.90)  131.893 ms  131.973 ms  132.049 ms
11  201.224.250.150 (201.224.250.150)  106.252 ms  106.167 ms  106.120 ms
12  201-218-92-198.cpe-statics.cableonda.net (201.218.92.198)  107.668 ms  107.937 ms  107.996 ms
13  201-218-92-205.cpe-statics.cableonda.net (201.218.92.205)  106.804 ms  106.343 ms  106.334 ms

Here's some tracerts from our end.

9  ge-2-0-0.mia11.ip4.tinet.net (89.149.182.34)  78.222 ms  78.268 ms  78.183 ms
10  c-w-panama-gw.ip4.tinet.net (173.241.131.90)  131.893 ms  131.973 ms  132.049 ms

This is way out of our network when it's higher than 77ms.
#10
I have been having this problem too and it gets really annoying that i cant play my ping usually is 289-299 but sometimes it goes up to 345 i did a traceroute to that server and its like this

Tracing route to 173-231-20-18.hosted.static.webnx.com [173.231.20.18]
over a maximum of 30 hops:

  1    3 ms    1 ms    1 ms  mygateway1.ar7 [192.168.1.1]
  2    *        *        *    Request timed out.
  3    25 ms    24 ms    23 ms  89.148.62.50
  4    24 ms    23 ms    22 ms  89.148.62.25
  5    23 ms    23 ms    23 ms  172.17.2.66
  6    24 ms    23 ms    23 ms  172.17.2.113
  7  224 ms  224 ms  224 ms  if-1-0-2.mcore4.NYY-NewYork.as6453.net [209.58.60.17]
  8  169 ms  171 ms  170 ms  ge-0-2-0.0.pjr02.ldn001.flagtel.com [85.95.25.58]
  9    *      224 ms  232 ms  Vlan25.icore1.NTO-NewYork.as6453.net [216.6.90.62]
10  170 ms  179 ms  170 ms  so-1-0-0.0.cjr02.ldn004.flagtel.com [85.95.25.10]
11  225 ms  226 ms  224 ms  te0-6-0-1.ccr22.jfk05.atlas.cogentco.com [154.54.12.93]
12  226 ms  234 ms  225 ms  10gigabitethernet7-4.core1.nyc4.he.net [72.52.92.241]
13  231 ms  231 ms  232 ms  te0-4-0-2.ccr21.dca01.atlas.cogentco.com [154.54.42.17]
14  290 ms  288 ms  297 ms  10gigabitethernet3-2.core1.den1.he.net [184.105.213.86]
15  256 ms  257 ms  256 ms  te0-2-0-1.ccr21.iah01.atlas.cogentco.com [154.54.29.6]
16  299 ms  299 ms  299 ms  216.218.213.250
17  293 ms  292 ms  293 ms  te0-2-0-0.mpd22.lax01.atlas.cogentco.com [154.54.3.78]
18  299 ms  300 ms  299 ms  100-42-223-194.static.webnx.com [100.42.223.194]

19  294 ms  295 ms  293 ms  38.122.146.26
20  299 ms  300 ms    *    173-231-20-18.hosted.static.webnx.com [173.231.20.18]
21  293 ms  293 ms  294 ms  100-42-223-178.static.webnx.com [100.42.223.178]

22  299 ms  298 ms  299 ms  173-231-20-18.hosted.static.webnx.com [173.231.20.18]

Trace complete.


Pinging 173.231.20.18 with 32 bytes of data:
Reply from 173.231.20.18: bytes=32 time=299ms TTL=44
Reply from 173.231.20.18: bytes=32 time=299ms TTL=44
Reply from 173.231.20.18: bytes=32 time=300ms TTL=44
Reply from 173.231.20.18: bytes=32 time=300ms TTL=44

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


when my ping is 340 in office in snipers its 295, and in some maps in snipers it just goes up to 360, any idea whats going on?

Users browsing this thread: 1 Guest(s)