HELP! Server lagging badly!!!!

[GUMP61]

Hey guys the WAW server has been really laggy for at least a week now. Also COD 4 is bad too!   Any idea what's going on. Everybody's ping jumps all over the place . Mine is double and sometimes triple of what it usually is.

[deerejon]

5 minutes ago, GUMP61 said:

Hey guys the WAW server has been really laggy for at least a week now. Also COD 4 is bad too!   Any idea what's going on. Everybody's ping jumps all over the place . Mine is double and sometimes triple of what it usually is.

As far as the Ftag server, as I said I only heard about this yesterday? This morning? I forget we're working on it in this post...stay tuned for updates...

 

[Hunter1948]

I think it's on the server side @GUMP61 and I thik they are looking into it.

[J3st3r]

COD4 is lagging like shit to. Seems to happen most in the evenings and early morning. 

 

Hashtag this shit and pass it on lol.

#NukeNFOServers

[djMot]

I have opened a ticket with NFO noting that we've been experiencing server degradation for upwards of two months now, and in particular that last night the servers were becoming unplayable.  Their predictable response was,  "We're not seeing any issues... blah, blah, blah..."

Quote

We're not seeing any issues in NYC or the host machine overall. If you're seeing high pings, could you please provide us with a traceroute taken at the same time you're experiencing the issue so we can take a closer look?

To perform a tracert to provide more information on a continuously-high latency problem, please follow these instructions:

1) Run a tracert from your command line. We have more information on how to do that here: http://forums.nfoservers.com/viewtopic.php?f=25&t=1539 

2) Obtain your IP address (one place to obtain it is http://www.whatismyip.com)

3) Send us the information from steps #1 and #2.

4) Have anyone else seeing the same problem also complete steps #1-#3.

5) Allow us time to review the tracert, run further tests from our end, and work with InterNAP to see if there is a routing problem that we or they can address.

In another thread, I've pinged Rugger to try to see how we could add some bite to the situation.  I don't pay the bills around here, so I have to defer to management on that.  But this business of always pushing problems back at the customer because "it must be them, not us" is the most frustrating aspect of technology technical support I know.

NFO has provided the instructions for obtaining a traceroute from your computer.  I suggest you do as they say and post the information here.  I'll try to keep up and update the ticket I have open with them.

ONLY REPORT situations where your play is clearly affected by server performance degradation.  I will reject any ping report showing "normal" response times.  If you want a better utility than the built-in trace route command (tracert) then use this one instead and from the Edit menu select "Copy as text".  Do not submit screenshots since NFO does not have a way to attach images to their tickets.

[Giggles]

At 8:51 AM 

 

C:\Users\Melody>tracert 162.248.95.178

Tracing route to c-162-248-95-178.managed-ded.inap-nyc.nfoservers.com [162.248.9
5.178]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [192.168.1.1]
  2    15 ms    18 ms    10 ms  173-26-64-1.client.mchsi.com [173.26.64.1]
  3    17 ms    21 ms    16 ms  172.30.9.137
  4    19 ms    17 ms    15 ms  68-66-73-70.client.mchsi.com [68.66.73.70]
  5    15 ms    19 ms    17 ms  po10.chgil001er1.mchsi.com [68.66.73.122]
  6    20 ms    15 ms    17 ms  be-123-pe01.350ecermak.il.ibone.comcast.net [50.
248.118.9]
  7    16 ms    16 ms    18 ms  be-10563-cr02.350ecermak.il.ibone.comcast.net [6
8.86.82.157]
  8    42 ms    37 ms    39 ms  be-10305-cr02.newyork.ny.ibone.comcast.net [68.8
6.85.201]
  9    36 ms    35 ms    37 ms  be-10381-pe02.111eighthave.ny.ibone.comcast.net
[68.86.86.250]
 10    44 ms    42 ms    41 ms  96-87-8-82-static.hfc.comcastbusiness.net [96.87
.8.82]
 11    36 ms    35 ms    35 ms  border2-po2-bbnet2.nyj004.pnap.net [216.52.95.11
0]
 12    37 ms    35 ms    38 ms  inap-b2e4.e9.router.nyc.nfoservers.com [162.248.
95.253]
 13    35 ms    36 ms    36 ms  c-162-248-95-178.managed-ded.inap-nyc.nfoservers
.com [162.248.95.178]

Trace complete.

C:\Users\Melody>

[Giggles]

I will post another tonight when I play cuz 4 me last night was awful

[PainKiller]

It's been hitting CoD2 as well, so it has to be down to the host

[J3st3r]

Fuck that trace route shit the lazy bastards.  They are to LAZY to try and figure out there own damn problems. That's completely unprofessional.  Nothing new from NFOServers.

 

 

Great idea with the PingPlotter.  You can basically record the damn thing while you game.

 

[djMot]

UPDATE:

NFO tells me that our server is overloaded.  It's not problems with the route to the server, their routers, the quality of their service, etc. 

I noticed during an event earlier today that my PingPlotter graph showed absolutely NO lag in the route.  Nevertheless, multiple servers were going Timeout.  NFO reports that we are over capacity on our server and we are swamping it's CPUs.   It's just that we're so darn popular!

Don't bother recording TRACERT or PingPlotter times.  They don't matter at this point.

[J3st3r]

Overloaded the P4 3.06ghz CPU eh?  Time to upgrade to a Core 2 Duo.

 

[Giggles]

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

C:\Users\Melody>tracert 162.248.95.178

Tracing route to c-162-248-95-178.managed-ded.inap-nyc.nfoservers.com [162.248.9
5.178]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [192.168.1.1]
  2    21 ms    15 ms    13 ms  173-26-64-1.client.mchsi.com [173.26.64.1]
  3    20 ms    18 ms    15 ms  172.30.9.137
  4    16 ms    19 ms    15 ms  68-66-73-70.client.mchsi.com [68.66.73.70]
  5    18 ms    17 ms    14 ms  po10.chgil001er1.mchsi.com [68.66.73.122]
  6    20 ms    14 ms    20 ms  be-123-pe01.350ecermak.il.ibone.comcast.net [50.
248.118.9]
  7    17 ms    22 ms    16 ms  be-10563-cr02.350ecermak.il.ibone.comcast.net [6
8.86.82.157]
  8    44 ms    40 ms    39 ms  be-10305-cr02.newyork.ny.ibone.comcast.net [68.8
6.85.201]
  9    36 ms    35 ms    40 ms  be-10381-pe02.111eighthave.ny.ibone.comcast.net
[68.86.86.250]
 10    47 ms    44 ms    44 ms  96-87-8-82-static.hfc.comcastbusiness.net [96.87
.8.82]
 11    31 ms    37 ms    46 ms  border2-po2-bbnet2.nyj004.pnap.net [216.52.95.11
0]
 12    35 ms    37 ms    37 ms  inap-b2e4.e9.router.nyc.nfoservers.com [162.248.
95.253]
 13    30 ms    34 ms    36 ms  c-162-248-95-178.managed-ded.inap-nyc.nfoservers
.com [162.248.95.178]

Trace complete.

C:\Users\Melody>

 

 

 

This was at 4:15 ...While playing

 

[djMot]

@Giggles - those pings are fine.  It's not any sort of traffic bottleneck.  It's the server hardware itself.  No need to collect tracert data.  It's not the route.

[J3st3r]

The Minecraft server isn't on the same box is it?  If it is there's most of the problem.

Sandbox type games like that use huge amounts of resources unless the maps are whipped regularly. I used to run a BF2 Sandbox mod server on the same box that our BF2 and BF 1942 DC mod servers was on. When the sandbox mod server had been running for 10-12 hours and people had built up huge structures the other servers would lag horribly. Some times it would crash the whole box. We had to restart/reset the sandbox mod atleast every 4-6 hours to keep our other servers from lagging like hell.     

[snaFU73]

How can we be overloading the server when the lag is also happening, early in the morning (U.S. side) when the Freezetag server is half full and no other servers have a single player?  This seems like trying to get customer service a Best Buy.

[J3st3r]

Wait until we get DDOSed into oblivion.

That's what the fucking cocks as NFOServers NY did to my old clan. I'm dead serious. It started out as a "Bad Firmware update" then our CPU was overheating and crashing our servers so they switched boxes. Then shortly afterwards the 3 month long unrelenting DDOS attacks started that they supposedly could not do anything about it.  Rite in the middle of the CAL tournament season which is now CPL ( Cyberathlete Professional League). We were going for our 4th year straight as undefeated 2v2 4v4 and 8v8 BF2 champions.