Servers are lagging real bad - Printable Version +- (wL) Forums (https://war-lords.net/forum) +-- Forum: Community (https://war-lords.net/forum/forum-4.html) +--- Forum: Suggestions or Issues (https://war-lords.net/forum/forum-16.html) +--- Thread: Servers are lagging real bad (/thread-9146.html) |
Servers are lagging real bad - i cri everytiem - Nov 12 2012 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 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. RE: Servers are lagging real bad - Dr. gkovr - Nov 12 2012 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 RE: Servers are lagging real bad - Matt - Nov 12 2012 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. RE: Servers are lagging real bad - i cri everytiem - Dec 17 2012 Again, server are lagging.. RE: Servers are lagging real bad - Matt - Dec 18 2012 Probably an attack, I can't check right now. RE: Servers are lagging real bad - Sibrox - Dec 18 2012 And some servers are crashing or choking, maybe you need to transfer to another host? RE: Servers are lagging real bad - Matt - Dec 18 2012 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. RE: Servers are lagging real bad - i cri everytiem - Dec 19 2012 Getting around 150 ping (about 70+ what I use to get). Please take a look at these again. RE: Servers are lagging real bad - s p a c e - Dec 19 2012 Minigames crashed today for about like 5 minutes. RE: Servers are lagging real bad - Matt - Dec 19 2012 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. |