TBG servers REALLY need a hardware upgrade

H

HideOut

Registered User
Joined
Apr 17, 2014
Messages
7
Age
51
Or internet or something, Sure is the hardware though. Tonight by 1045PM EST they were lagged out beyond playable already. No other servers i play on have that issue regularly. Just TBG's.

Dont know who's hardware it is, but if you are renting time someone needs to have a discussion with the owners.

BF4 BTW, all servers
 
E3 1270v3 in both boxes. Pretty standard fair for this and way more than enough for what we have on them. CPU usage never even reaches 50%. NFO is the host.

The cabinet has dual redundant 10 Gbps uplinks of course shared by all customers. Hosted in an Internap data center.
 
Last edited:
wow rain put that nicely thought he might go all stewie on him
 
BlitZ003 said:
wow rain put that nicely thought he might go all stewie on him
Click to expand...
Its not my servers its not like I give a shit lol. I always blame battlefield 4 but I have no clue why its so hard to keep these particular ones running well.
 
HideOut said:
Dont know who's hardware it is, but if you are renting time someone needs to have a discussion with the owners.

BF4 BTW, all servers
Click to expand...
BlitZ003 said:
wow rain put that nicely thought he might go all stewie on him
Click to expand...

Actually screw it want me to go stewie? ALL battlefield 4 servers are rented from somewhere. You can't run your own :p, Thanks EA. Now to go stewie I have to throw like a "you moron" on there somewhere right?
 
RainMotorsports said:
Actually screw it want me to go stewie? ALL battlefield 4 servers are rented from somewhere. You can't run your own :p, Thanks EA. Now to go stewie I have to throw like a "you moron" on there somewhere right?
Click to expand...
you also need to get a "victory is/will be mine" in there too
 
We have the best hardware available for gaming servers and the network is top of line.

Could be a couple possibilites

Your routing connection to our IPs may be garbage. You will have to call your ISP for this.
Type "tracert OUR IP" in cmd screen to check.
And I think I have already explained to you. If we are getting hit with ddos it will lag the servers. We nor anyone can do anything about this so remember that. Rush was attacked last night at 11pm eastern if that's the server you were on.
 
Some of the TBG servers that I have been on have at times been lagging. But it is most likely the Internet, or possibly the server host getting to much traffic.



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

C:\Users\sofbsmd0>tracert 74.91.125.103

Tracing route to c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74
.91.125.103]
over a maximum of 30 hops:

1 <1 ms * <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms * 5 ms L100.PHLAPA-VFTTP-89.verizon-gni.net [96.245.182.1]
3 8 ms * 7 ms G101-0-0-13.PHLAPA-LCR-21.verizon-gni.net [100.41.207.15]
4 * * * Request timed out.
5 73 ms * 56 ms 0.ae1.XL3.CHI13.ALTER.NET [140.222.225.179]
6 28 ms * 29 ms TenGigE0-4-0-0.GW2.CHI13.ALTER.NET [152.63.66.106]
7 27 ms * 28 ms internap-gw.customer.alter.net [63.84.96.162]
8 26 ms * 27 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
9 27 ms * 27 ms c-74-91-125-103.managed-ded.internap-chicago.nfo
servers.com [74.91.125.103]

Trace complete.

C:\Users\sofbsmd0>
 
Last edited:
Iguanidon said:
I can't tell if somethings lagging.... 491 ping to Boston. YAY TWC
Click to expand...

cmd prompt and run tracert 74.91.125.103 and look at response. Could be a bad switch etc.

C:\Windows\system32>tracert 74.91.125.103

Tracing route to c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74.91.125.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms JWRNET [192.x.x.X]
2 ****************************
3 **********************************************************
4 11 ms 10 ms 13 ms be-50-ar01.chartford.ct.hartford.comcast.net [68.87.182.238]
5 14 ms 15 ms 16 ms he-1-12-0-0-ar01.needham.ma.boston.comcast.net [162.151.53.145]
6 40 ms 44 ms 43 ms be-7015-cr01.newyork.ny.ibone.comcast.net [68.86.90.217]
7 41 ms 40 ms 40 ms he-0-11-0-1-pe02.111eighthave.ny.ibone.comcast.net [68.86.87.226]
8 41 ms 42 ms 40 ms 50.242.151.70
9 40 ms 39 ms 53 ms ae-1.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.68]
10 52 ms 55 ms 50 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.40]
11 45 ms 42 ms 42 ms ae-1.r05.chcgil09.us.bb.gin.ntt.net [129.250.2.25]
12 46 ms 43 ms 42 ms ae-0.internap.chcgil09.us.bb.gin.ntt.net [129.250.203.178]
13 49 ms 48 ms 46 ms border10.po1-bbnet1.chg.pnap.net [64.94.32.22]
14 45 ms 48 ms 44 ms c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74.91.125.103]

Trace complete.
 
Tracing route to c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74.91.125.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms LINKSYS01657 [192.XXX.X.X]
2 31 ms 22 ms 26 ms cpe-174-099-000-001.nc.res.rr.com [174.99.0.1]
3 113 ms 20 ms 17 ms gig10-0-0-420.rlghnca-rtr2.nc.rr.com [66.26.44.205]
4 11 ms 11 ms 11 ms cpe-024-025-062-150.ec.res.rr.com [24.25.62.150]
5 17 ms 19 ms 18 ms be31.chrcnctr01r.southeast.rr.com [24.93.64.186]
6 23 ms 24 ms 23 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
7 28 ms 21 ms 21 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
8 23 ms 21 ms 21 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
9 23 ms 22 ms 20 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.161]
10 52 ms 53 ms 53 ms be2099.ccr42.ord01.atlas.cogentco.com [154.54.28.73]
11 55 ms 75 ms 53 ms be2003.ccr21.ord03.atlas.cogentco.com [154.54.29.22]
12 46 ms 47 ms 45 ms 38.104.102.102
13 49 ms 46 ms 46 ms border6.po1-bbnet1.chg.pnap.net [64.94.32.11]
14 53 ms 47 ms 47 ms c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74.91.125.103]

Trace complete.
 
C:\Windows\system32>tracert 74.91.125.103

Tracing route to c-74-91-125-103.managed-ded.internap-chicago.nfoservers.com [74
.91.125.103]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 41 ms 28 ms 28 ms bundle1.wrrnme04-10k002.nyroc.rr.com [74.78.160.
1]
3 19 ms 23 ms 17 ms bundle1.spldme47-10k001.nyroc.rr.com [24.31.156.
1]
4 14 ms 19 ms 14 ms agg30.ptldmehx02r.northeast.rr.com [24.58.41.140
]
5 109ms 214 ms 21ms be25.albynyyf01r.northeast.rr.com [24.58.32.64]

6 32 ms 33 ms 30 ms be46.cr0.nyc30.tbone.rr.com [107.14.19.102]
7 70ms 70s 28 ms 107.14.17.216
8 28 ms 32 ms 29 ms 209.220.18.145.ptr.us.xo.net [209.220.18.145]
9 30 ms 29 ms 34 ms 207.88.13.58.ptr.us.xo.net [207.88.13.58]
10 59 ms 58 ms 58 ms 207.88.14.62.ptr.us.xo.net [207.88.14.62]
11 50 ms 49 ms 52 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
12 53 ms 50 ms 52 ms border10.po2-bbnet2.chg.pnap.net [64.94.32.87]
13 50 ms 50 ms 51 ms c-74-91-125-103.managed-ded.internap-chicago.nfo
servers.com [74.91.125.103]

Trace complete.
 
1 <1 ms <1 ms <1 ms GOD DAMN IT [HEY.No.No.No]
2 35 ms 41 ms 27 ms cpe-107-015-064-001.nc.res.rr.com [107.15.64.1]
3 68 ms 26 ms 17 ms 66.26.45.169
4 14 ms 12 ms 12 ms cpe-024-025-062-104.ec.res.rr.com [24.25.62.104]
5 23 ms 15 ms 15 ms be31.drhmncev01r.southeast.rr.com [24.93.64.184]
6 24 ms 22 ms 18 ms 107.14.19.44
7 17 ms 17 ms 17 ms ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
8 19 ms 19 ms 24 ms 209.48.38.225
9 28 ms 29 ms 23 ms 207.88.14.180.ptr.us.xo.net [207.88.14.180]
10 30 ms 24 ms 22 ms 207.88.12.135.ptr.us.xo.net [207.88.12.135]
11 25 ms 25 ms 26 ms 207.88.12.105.ptr.us.xo.net [207.88.12.105]
12 44 ms 48 ms 49 ms 207.88.14.62.ptr.us.xo.net [207.88.14.62]
13 42 ms 41 ms 44 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
14 47 ms 44 ms 47 ms border6.po1-bbnet1.chg.pnap.net [64.94.32.11]
15 40 ms 43 ms 41 ms c-74-91-125-103.managed-ded.internap-chicago.nfo
servers.com [74.91.125.103]
 
I live a couple of hours from Iguanidon in the same state and will have spike issues in the evening. Usually between 6pm and 10pm, totally random when it happens. Annoying as hell. Wednesday night had spikes as high as 500. I hate Time Warner.
 
You must log in or register to reply here.
Back
Top