Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Servers are lagging real bad
#1
Also, many laggers are being welcomed, I'm not the only one complaining about it. Snipers/ MG/ and pop maps are the worst servers with lag right now. Also

Matt, post: 79684, member: 178 Wrote:Like always, just saying "MY PING HAS RISEN HALP!!!" is very unhelpful. Tracert Tracert Tracert.

Double post

I decided to do some traceroutes from the server.

DK yours seems fine.
Code:
1 142-4-63-225.static.webnx.com (142.4.63.225) 0.270 ms 0.335 ms 0.390 ms 2 100-42-223-193.static.webnx.com (100.42.223.193) 0.498 ms 0.604 ms 0.760 ms 3 100-42-223-141.static.webnx.com (100.42.223.141) 0.532 ms 0.692 ms 0.789 ms 4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.779 ms 0.938 ms 1.007 ms 5 te0-4-0-7.mpd21.lax01.atlas.cogentco.com (154.54.84.109) 0.771 ms te0-2-0-7.mpd21.lax01.atlas.cogentco.com (154.54.24.61) 0.836 ms te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.733 ms 6 te8-2.ccr01.lax05.atlas.cogentco.com (154.54.0.218) 0.734 ms te7-8.ccr01.lax05.atlas.cogentco.com (154.54.30.190) 0.555 ms te9-1.ccr01.lax05.atlas.cogentco.com (154.54.44.138) 0.677 ms 7 te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.471 ms te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 18.451 ms te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.474 ms 8 pos-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.57) 3.963 ms 19.377 ms 3.955 ms 9 68.86.86.118 (68.86.86.118) 34.795 ms 58.905 ms 34.681 ms 10 pos-1-6-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.85.154) 54.464 ms 70.459 ms 70.447 ms 11 he-0-2-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.89.145) 87.229 ms 87.272 ms 86.576 ms 12 so-1-1-0-0-ar03.audubon.nj.panjde.comcast.net (68.86.92.162) 72.144 ms 87.750 ms 87.606 ms 13 xe-0-1-2-0-ar03.absecon.nj.panjde.comcast.net (68.86.152.114) 74.183 ms ae-1-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.63.178) 74.183 ms so-3-0-0-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.62.214) 73.904 ms 14 xe-11-0-0-0-sur01.eatontown.nj.panjde.comcast.net (68.85.62.78) 77.961 ms 77.525 ms 94.490 ms 15 te-17-10-cdn07.eatontown.nj.panjde.comcast.net (68.87.214.130) 82.989 ms 85.277 ms 90.150 ms


Double post

My latency used to be 70-85 (scoreboard) and with net_graph 1 90-100. Now, it's 127-160 (scoreboard) and with net_graph 1 140-170. I reset my modem/router, and still the same. Also, I'm not the only one.
[Image: 1UH9a8H.png]



[Image: 5pfuEDP.gif]
#2
Just to chime in a little, latency usually idles around the mid 80's, sometimes dips to the 70's and today it was a constant 100-115. Made sure all of my network-based processes were terminated, so I assume the issue is server side.

EDIT:
Code:
C:\Users\User>tracert 173.231.20.20 Tracing route to 173-231-20-20.hosted.static.webnx.com [173.231.20.20] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.0.1.1 2 28 ms 20 ms 20 ms 71.63.124.1 3 11 ms 10 ms 11 ms te-9-4-ur01.shadygrove.va.richmond.comcast.net [68.86.126.213] 4 8 ms 8 ms 8 ms te-9-1-ur01.ashland.va.richmond.comcast.net [68.86.172.6] 5 9 ms 9 ms 9 ms te-1-4-ar01.staplesmllrd.va.richmond.comcast.net[68.86.172.85] 6 19 ms 19 ms 19 ms pos-0-7-0-0-cr01.charlotte.nc.ibone.comcast.net[68.86.91.153] 7 24 ms 23 ms 23 ms pos-3-10-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.86.221] 8 37 ms 39 ms 35 ms pos-0-10-0-0-cr01.miami.fl.ibone.comcast.net [68.86.85.6] 9 63 ms 67 ms 63 ms pos-3-13-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.87.213] 10 107 ms 95 ms 95 ms 68.86.87.37 11 95 ms 95 ms 95 ms pos-0-5-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.88.194] 12 96 ms 97 ms 95 ms 173.167.57.138 13 94 ms 133 ms 94 ms ae0-90g.cr1.lax1.us.nlayer.net [69.31.127.141] 14 101 ms 98 ms 95 ms ae1-50g.ar1.lax2.us.nlayer.net [69.31.127.130] 15 113 ms 113 ms 113 ms as18450.xe-1-0-5.ar1.lax2.us.nlayer.net [69.31.127.54] 16 115 ms 109 ms 110 ms 100-42-223-138.static.webnx.com [100.42.223.138] 17 95 ms 96 ms 97 ms 100-42-223-178.static.webnx.com [100.42.223.178] 18 96 ms 98 ms 95 ms 173-231-20-20.hosted.static.webnx.com [173.231.20.20] Trace complete.
[Image: sigix.png]
#3
Might be a congestion problem with Comcast and our providers transit, seems to have cleared up now.

--- 68.87.214.130 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49109ms
rtt min/avg/max/mdev = 76.071/76.153/76.260/0.211 ms

Very little jitter at all, that IP was the last hop on DK's trace route.

This is dr gkovr

--- 71.63.124.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49105ms
rtt min/avg/max/mdev = 66.061/66.155/66.385/0.254 ms

traceroute to 71.63.124.1 (71.63.124.1), 30 hops max, 60 byte packets
1 142-4-45-177.static.webnx.com (142.4.45.177) 0.283 ms 0.371 ms 0.429 ms
2 100-42-223-177.static.webnx.com (100.42.223.177) 0.508 ms 0.807 ms 0.899 ms
3 100-42-223-137.static.webnx.com (100.42.223.137) 0.515 ms 0.716 ms 0.775 ms
4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.851 ms 1.071 ms 1.126 ms
5 te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.717 ms te0-4-0-7.mpd21.lax01.atlas.cogentco.com (154.54.84.109) 0.657 ms te0-2-0-7.mpd21.lax01.atlas.cogentco.com (154.54.24.61) 0.697 ms
6 te9-1.ccr01.lax05.atlas.cogentco.com (154.54.44.138) 0.784 ms 0.833 ms te4-5.ccr01.lax05.atlas.cogentco.com (154.54.82.158) 0.598 ms
7 te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 1.783 ms 1.774 ms te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 1.713 ms
8 pos-2-4-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.88.189) 3.123 ms 3.122 ms 3.116 ms
9 68.86.85.146 (68.86.85.146) 39.322 ms 39.427 ms 39.365 ms
10 pos-1-8-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.85.158) 56.263 ms 56.260 ms 56.248 ms
11 pos-1-14-0-0-cr01.charlotte.nc.ibone.comcast.net (68.86.89.18) 59.253 ms 59.298 ms 59.237 ms
12 so-1-0-0-0-ar02.staplesmllrd.va.richmond.comcast.net (68.86.91.150) 65.428 ms 65.322 ms 65.208 ms
13 te-1-1-ur01.ashland.va.richmond.comcast.net (68.86.172.86) 65.867 ms 65.915 ms 65.777 ms
14 te-1-1-ur01.shadygrove.va.richmond.comcast.net (68.86.172.5) 66.381 ms 66.250 ms 66.134 ms

traceroute to 71.63.124.1 (71.63.124.1), 30 hops max, 60 byte packets
1 142-4-45-177.static.webnx.com (142.4.45.177) 0.546 ms 0.608 ms 0.653 ms
2 100-42-223-177.static.webnx.com (100.42.223.177) 0.589 ms 0.750 ms 0.842 ms
3 100-42-223-137.static.webnx.com (100.42.223.137) 0.421 ms 0.621 ms 0.725 ms
4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.773 ms 1.006 ms 1.057 ms
5 te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.750 ms te0-4-0-7.mpd21.lax01.atlas.cogentco.com (154.54.84.109) 0.691 ms te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.737 ms
6 te9-1.ccr01.lax05.atlas.cogentco.com (154.54.44.138) 0.968 ms te7-8.ccr01.lax05.atlas.cogentco.com (154.54.30.190) 0.582 ms te4-5.ccr01.lax05.atlas.cogentco.com (154.54.82.158) 0.622 ms
7 te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 1.783 ms te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 1.756 ms te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 1.754 ms
8 pos-2-4-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.88.189) 5.941 ms 5.923 ms 5.900 ms
9 68.86.85.146 (68.86.85.146) 40.121 ms 40.031 ms 40.083 ms
10 pos-1-8-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.85.158) 54.192 ms 54.203 ms 54.195 ms
11 pos-1-14-0-0-cr01.charlotte.nc.ibone.comcast.net (68.86.89.18) 58.157 ms 58.141 ms 58.118 ms
12 so-1-0-0-0-ar02.staplesmllrd.va.richmond.comcast.net (68.86.91.150) 91.018 ms 65.177 ms 65.392 ms
13 te-1-1-ur01.ashland.va.richmond.comcast.net (68.86.172.86) 65.975 ms 65.871 ms 66.091 ms
14 te-1-1-ur01.shadygrove.va.richmond.comcast.net (68.86.172.5) 95.629 ms 95.826 ms 95.927 ms

Looks like a Comcast problem to me.
#4
Again, server are lagging..
[Image: 1UH9a8H.png]



[Image: 5pfuEDP.gif]
#5
Probably an attack, I can't check right now.
#6
And some servers are crashing or choking, maybe you need to transfer to another host?
Just Go With IT. √

 Why are you even looking here? scroll down if you can.
#7
We host our own servers.

   

As you can see by the graph there was an attack of roughly 600Mbps.

Most game server hosts will struggle to host a full 48 slot server. Plus moving hosts will cause us to loose the server IP's which is never a good thing when hosting game servers.
#8
Getting around 150 ping (about 70+ what I use to get). Please take a look at these again.
[Image: 1UH9a8H.png]



[Image: 5pfuEDP.gif]
#9
Minigames crashed today for about like 5 minutes.
[Image: 519966_101.png]
[Image: 541034_101.png]
#10
DK, post: 82282, member: 3039 Wrote:Getting around 150 ping (about 70+ what I use to get). Please take a look at these again.

Tracert it. The graphs are showing nothing out of the ordinary.

Users browsing this thread: 1 Guest(s)