Lag: US22 - 2fort+ Chigago

PsychoRealm

PsychoRealm

Australian Skial God
Contributor
Reporting lag on the server around 5:10 - 5.14 pm EST.
This time I took screenshots so it would be clear it was not only my issue. Also have to point out that SourceOP.com 24/7 2fort [INSTANT RESPAWN] server was experiencing the exact same lag within the same time frame.

Screenshots:

7D4AA76E3DA78C7AD395C2E5D822899CC14B503F


1EFB944D9F726A22F17EA5711E232134839D2ADC


01A64569271086D62568AC971BAF3FA8BDB90929
 
Next time do what bottiger tells people to do

1. Take a screenshot of the netgraph at 5
2. take a screenshot with winmtr

otherwise he cannot help.

And its near impossible to have servers run 24/7 without a lagspike every now and then
 
KillerZebra said:
Next time do what bottiger tells people to do

1. Take a screenshot of the netgraph at 5
2. take a screenshot with winmtr
Click to expand...

/sigh
Are you fucking serious? Okay... I'll try to make it as simple as possible.

WPi5Z.jpg


lUC0A.jpg


B2I2R.jpg


6 people typed "laaaaaag" and about 3-4 dudes said it through Voice Chat. /sigh.
 
im not an idiot. You screenshots don't help that much tho. All they show is a few people getting lag.

with what bottiger tells everyone to do during a lag will show any packetdrops, if its server lag or what is actually going on. For all ur screenshot shows is a few people complaining about lag. Which someone always does whenever the server lags or not.

i believe it also shows in and out times. pings and so on. This way bottiger can pinpoint if its ddos, server lag which requires a reboot, or just player lag.

No need to be such an asshole about it when im just letting you know what bottiger ask people to do
 
I can also attest that as usual Chicago is getting intermittent lagspikes - it isn't uncommon tho..for the past year or so it goes on and off.
 
KillerZebra said:
No need to be such an asshole about it when im just letting you know what bottiger ask people to do
Click to expand...
I know what Bottiger asks people to do and I did that when I was reporting the lag to him before. There has been no lag for over a week now and this spike is completely different from what it was before. This spike should be clearly seen on the server.

Also, I'm not asking for help. I'm reporting the lag. As simple as that. Should Bott decide to take it seriously or not - non of my business.

In addition, I'm pretty positive you've edited your initial post while I was uploading another screenshots. In your inital post you said something about my screenshots showing nothing besides my ping - that's why you've got respective attitude in response.
 
Bottiger said:
I don't see anything in our logs and I am still getting pings of up to 2000 ms to you.
Click to expand...
Ok then. Just as a side note: once this lag occurred everybody started leaving and by 5:30 pm there were about 15 players on the server. There are 16 players on the server right now.

Also, I don't know what tools you are using, but here is tracerout results from gateways in Montreal (Bell), Hong Kong (Global Crossing) and Frankfurt (Deutche Telecom):
Router: Montreal
Command: traceroute 76.112.224.161
traceroute to 76.112.224.161 (76.112.224.161), 30 hops max, 38 byte packets
1 206.47.244.66 (206.47.244.66) 0.442 ms 0.238 ms 0.206 ms
2 core4-montreal02_GE5-0-0.net.bell.ca (206.108.107.49) 0.183 ms 0.140 ms 0.128 ms
3 Ncore3-montreal02_POS0-4-1-0_core.net.bell.ca (64.230.168.237) 9.453 ms 8.635 ms 8.338 ms
MPLS Label=16031 CoS=5 TTL=255 S=0
4 newcore1-newyork83_so1-0-0.net.bell.ca (64.230.187.129) 7.603 ms 7.559 ms 7.564 ms
MPLS Label=358976 CoS=5 TTL=1 S=0
5 bx6-newyork83_xe3-0-0.net.bell.ca (64.230.187.158) 7.563 ms 7.587 ms 7.558 ms
6 be-10-808-pe01.111eighthave.ny.ibone.comcast.net (173.167.56.109) 8.378 ms 8.233 ms 8.067 ms
7 pos-1-9-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.86.41) 8.832 ms 10.899 ms 12.249 ms
8 pos-2-2-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.85.9) 16.237 ms 17.606 ms 16.008 ms
9 pos-0-15-0-0-ar01.taylor.mi.michigan.comcast.net (68.86.90.106) 28.401 ms 30.533 ms 28.302 ms
10 te-9-4-ur02.royaloak.mi.michigan.comcast.net (68.85.222.197) 29.914 ms 29.787 ms 29.862 ms
11 te-17-10-cdn10.royaloak.mi.michigan.comcast.net (68.85.49.242) 46.787 ms 43.968 ms 50.419 ms
12 c-76-112-224-161.hsd1.mi.comcast.net (76.112.224.161) 42.432 ms 42.693 ms 43.230 ms
Trying trace from node 'Hong Kong, China' to '76.112.224.161'


1 113.29.32.129 (113.29.32.129) 87.236 ms 0.327 ms
2 po3-40G.ar4.LAX2.gblx.net (67.17.107.82) 158.040 ms 158.036 ms
3 te-0-0-0-7-cr01.losangeles.ca.ibone.comcast.net (66.208.233.201) 167.491 ms 164.330 ms
4 pos-0-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.88.206) 195.312 ms 195.390 ms
5 pos-0-10-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.86.130) 208.268 ms 208.208 ms
6 pos-4-13-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.88.237) 226.758 ms 224.333 ms
7 pos-0-15-0-0-ar01.taylor.mi.michigan.comcast.net (68.86.90.106) 237.815 ms 239.611 ms
8 te-9-1-ur02.royaloak.mi.michigan.comcast.net (68.87.191.6) 238.738 ms 238.990 ms
9 te-17-10-cdn10.royaloak.mi.michigan.comcast.net (68.85.49.242) 257.853 ms 280.495 ms
10 c-76-112-224-161.hsd1.mi.comcast.net (76.112.224.161) 236.743 ms 238.398 ms
traceroute to 76.112.224.161 (76.112.224.161), 15 hops max, 60 byte packets
1 F-EA20.F.DE.net.DTAG.DE (194.25.0.217) 2.343 ms 2.261 ms 2.248 ms
2 was-sb1-i.WAS.US.NET.DTAG.DE (62.154.5.186) 89.475 ms 89.482 ms 89.456 ms
3 194.25.209.42 (194.25.209.42) 88.592 ms 88.599 ms 88.591 ms
4 pos-3-15-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.86.25) 90.275 ms 90.278 ms 90.268 ms
5 pos-0-13-0-0-ar01.taylor.mi.michigan.comcast.net (68.86.90.218) 100.910 ms 100.919 ms 100.910 ms
6 te-9-1-ur02.royaloak.mi.michigan.comcast.net (68.87.191.6) 103.795 ms 103.759 ms 103.743 ms
7 te-17-10-cdn10.royaloak.mi.michigan.comcast.net (68.85.49.242) 114.750 ms 103.506 ms 117.062 ms
8 c-76-112-224-161.hsd1.mi.comcast.net (76.112.224.161) 120.919 ms 117.269 ms 117.254 ms

I see no spikes in response to the node next to my gateway. Sorry.
 
I showed you already last time.

Your ping is spiking from time to time. You cannot hope to catch it with a single traceroute.

Just a few minutes of leaving MTR shows you spiked up to 1257 ms. Sourceop 2Fort is in another datacenter, so if it was lagging at the same time, it doesn't make sense for it to be the server's fault.

Host Loss% Snt Last Avg Best Wrst StDev
1. ip131.50-31-26.static.steadfastdns.net 0.0% 696 0.4 2.7 0.2 168.3 13.9
2. ip77.208-100-32.static.steadfastdns.net 0.3% 695 0.3 1.5 0.1 19.0 3.0
3. ip41.208-100-32.static.steadfastdns.net 35.5% 695 392.7 342.3 191.6 421.9 79.1
4. ae1-133.cr2.ord1.us.nlayer.net 0.0% 695 0.3 1.7 0.2 50.3 6.7
5. ae2-30g.ar1.ord1.us.nlayer.net 2.9% 695 4.2 2.9 1.0 11.1 1.5
6. 173-167-57-125-static.hfc.comcastbusiness.net 0.0% 695 0.9 0.7 0.5 6.7 0.4
7. be-11-cr01.350ecermak.il.ibone.comcast.net 0.0% 695 1.9 3.1 0.9 11.7 1.4
8. pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net 0.0% 695 2.4 3.3 1.0 11.2 1.4
9. pos-0-13-0-0-ar01.pontiac.mi.michigan.comcast.net 0.0% 695 17.5 16.2 14.1 20.1 1.2
10. te-9-4-ur03.royaloak.mi.michigan.comcast.net 0.0% 695 15.2 15.3 14.9 70.2 3.4
11. te-17-10-cdn10.royaloak.mi.michigan.comcast.net 0.0% 695 45.9 46.7 27.9 1257. 58.4
12. ???

Host Loss% Snt Last Avg Best Wrst StDev
1. 161-255-144-216.static.reverse.lstn.net 0.0% 751 0.7 1.2 0.5 30.9 2.4
2. vl13.cr02-55.core2.dllstx3.dallas-idc.com 0.0% 751 1.0 1.3 0.3 65.3 4.1
3. te3-4.core2.bdr2.dllstx3.dallas-idc.com 0.0% 751 155.0 6.2 0.3 206.3 25.4
4. xe-2-1-0.mpr1.dfw1.us.above.net 0.0% 751 0.5 3.4 0.3 80.4 11.3
5. xe-2-3-0.cr1.dfw2.us.above.net 0.0% 751 0.7 4.8 0.5 68.1 11.0
6. xe-8-2-0.er1.dfw2.us.above.net 0.5% 751 0.7 2.0 0.4 62.0 6.6
7. above-comcast.dfw2.us.above.net 0.0% 751 1.9 3.4 1.1 38.5 2.5
8. pos-2-3-0-0-cr01.dallas.tx.ibone.comcast.net 0.0% 751 3.4 4.2 1.3 40.9 2.8
9. pos-0-12-0-0-cr01.atlanta.ga.ibone.comcast.net 0.0% 751 22.3 22.8 21.8 71.9 2.9
10. pos-4-5-0-0-cr01.ashburn.va.ibone.comcast.net 0.0% 751 37.3 38.3 35.7 79.2 2.6
11. 68.86.95.254 0.0% 751 50.1 50.9 48.4 94.9 2.9
12. te-9-4-ur02.royaloak.mi.michigan.comcast.net 0.0% 751 51.6 52.2 51.3 141.7 5.4
13. te-17-10-cdn10.royaloak.mi.michigan.comcast.net 0.0% 751 62.4 71.9 52.2 1276. 62.6


For comparison here is an MTR report for someone with normal ping.

Host Loss% Snt Last Avg Best Wrst StDev
1. ip131.50-31-26.static.steadfastdns.net 0.0% 239 0.3 1.8 0.2 88.6 7.2
2. ip77.208-100-32.static.steadfastdns.net 1.3% 239 0.5 2.2 0.1 12.4 3.5
3. ip41.208-100-32.static.steadfastdns.net 23.1% 239 390.9 339.6 192.3 417.8 81.4
4. ae1-133.cr2.ord1.us.nlayer.net 0.4% 239 0.5 2.8 0.2 64.9 8.9
5. ae2-30g.ar1.ord1.us.nlayer.net 2.9% 238 4.0 2.9 1.3 7.3 1.3
6. 173-167-57-125-static.hfc.comcastbusiness.net 0.0% 238 0.8 0.6 0.5 1.9 0.2
7. be-12-cr01.350ecermak.il.ibone.comcast.net 0.0% 238 2.7 3.1 0.7 10.4 1.4
8. pos-2-13-0-0-ar01.area4.il.chicago.comcast.net 0.0% 238 6.0 4.1 1.6 23.4 2.1
9. pos-1-13-0-0-ar01.indianapolis.in.indiana.comcast.net 0.0% 238 6.7 6.9 6.4 20.2 0.9
10. te-3-1-ur01.champaign.il.chicago.comcast.net 0.0% 238 14.4 15.1 14.3 109.2 6.4
11. te-17-10-cdn07.champaign.il.chicago.comcast.net 0.0% 238 35.7 28.8 14.9 37.1 4.4
 
Lord Killington said:
n00b question, I'm probably reading it wrong, but from your screenshots, you always have <40 ping?
Click to expand...
Ping isn't the issue. Unfortunately since he didn't have net_graph 5 it's not showing the whole picture. On a 32 person server you're going to hit some choke no matter what with a lot of people. So if a whole ton of stuff is going on the server is going to most likely lag behind a bit and you'll see your choke go up and you'll get lag. I don't believe servers are technically designed for 32 players so if it's busy then it's more of a valve server issue. Granted I have experienced some major lag on the comp server with only 18 people, but lobby doesn't some weird stuff to servers so it could just be that.
 
You must log in or register to reply here.
Top Bottom
Back