Servers.

**Hocus Pocus** · 04-29-13, 03:25 PM

Originally Posted by Alundil

I see. Ok. But stating a preference for one != skip (kill) the other unless I'm missing something and for what it's worth, "representing the group" is tough to do if there's not been a noticeable outcry from the group (again unless I'm missing something).

Yeah that's why I leave the floor open for them. Its something that has been brought up frequently in game as of late so I'm just starting the thread.

Sent from my Desire HD using Tapatalk 2

**¤[BlitzKrieg]¤** · 04-30-13, 06:24 PM

I just know I am definitely useless on the East server. I am about 1 second behind everyone else. I can no longer play on the East server so it kind of sucks.

**Alundil** · 04-30-13, 06:56 PM

Originally Posted by ¤[BlitzKrieg]¤

I just know I am definitely useless on the East server. I am about 1 second behind everyone else. I can no longer play on the East server so it kind of sucks.

Were you getting good ping on easy at one point in it'd short life and if so when did that change? Or are you just saying that you don't get as good of ping to East as you do to Central? And where, geographically are you, if you don't mind my asking?

Sent from my Nexus 7 using Tapatalk HD

**~BigTymer~** · 04-30-13, 09:10 PM

I don't have any trouble with either server BUT I live in North East Alabama about 2:45 from the Atlanta server and I get the same ping as the Central server. BUT....When I play CS:GO on East I have a great ping and not so great on Central.

**¤[BlitzKrieg]¤** · 04-30-13, 09:29 PM

Welp, I just recently started playing again and every time we get on the East server my ping skyrockets. Not sure when the East server was implemented but since I came back I have always had trouble on it. I am in Colorado.

**Alundil** · 04-30-13, 09:58 PM

East/ATL server is since the beginning of March. There wasn't one before then.

Post up some pings and tracert results and lets some folks try and help diagnose. Though being in Colorado it would stand reason that Dallas would be a little better at the very least.

**Mr_Blonde_OPS** · 04-30-13, 11:08 PM

Originally Posted by Alundil

East/ATL server is since the beginning of March. There wasn't one before then.

Post up some pings and tracert results and lets some folks try and help diagnose. Though being in Colorado it would stand reason that Dallas would be a little better at the very least.

Ira lives farther West then Blitz and gets better ping. I notice Ira gets around 90s and Blitz had like 130 the other night.

I'm near Chicago and both servers are fine for me.

**Alundil** · 04-30-13, 11:48 PM

Right - kinda why (

) my sneaky self requested pings/tracert

I am reasonably sure that there might be a routing issue that one of our fine members can help troubleshoot.

**¤[BlitzKrieg]¤** · 05-01-13, 07:09 AM

Not sure if I did it right or not... but here is some info I got from using what I thought was the tracert in cmd. I think this was the correct server to tracert but not 100%

Tracing route to host.colocrossing.com [206.217.143.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 27 ms 25 ms 25 ms hlrn-dsl-gw06.hlrn.qwest.net [207.225.112.6]
3 24 ms 24 ms 27 ms hlrn-agw1.inet.qwest.net [71.217.188.41]
4 58 ms 58 ms 58 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 59 ms 59 ms 59 ms 63.146.26.154
6 66 ms 84 ms 59 ms ae-8.r20.lsanca03.us.bb.gin.ntt.net [129.250.5.1]
7 69 ms 72 ms 72 ms ae-4.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.169]
8 69 ms 70 ms 72 ms ae-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.59]
9 85 ms 85 ms 85 ms ae-4.r03.atlnga05.us.bb.gin.ntt.net [129.250.3.90]
10 91 ms 83 ms 88 ms ae9.ar1.atl1.us.nlayer.net [69.31.135.172]
11 90 ms 90 ms 85 ms ae0-50g.cr1.atl1.us.nlayer.net [69.31.135.129]
12 90 ms 90 ms 87 ms ae1-40g.cr2.atl1.us.nlayer.net [69.31.135.138]
13 96 ms 99 ms 99 ms as36352.ae6-107.cr2.atl1.us.nlayer.net [69.31.135.94]
14 102 ms 102 ms 103 ms host.colocrossing.com [206.217.143.135]

**Kanati** · 05-01-13, 08:47 AM

You hit high 50s before you ever leave your ISP (qwest) and mid 80s before you leave ntt. Definitely not a server issue. I'd be interested to see your dallas tracert as well. I'm betting it can't be a lot less than mid 70s since your ntt route bounces through dallas anyway.