The Server move made gameplay too painful

Personally I haven't had any issues except perhaps re-adding the server to my favorites (Can't remember if this was in-fact a issue for me..), but I think what would've helped others a bit, or perhaps the most, is a advanced notice.

Correct me if I'm wrong anyone, but having the server move come out of nowhere for those that don't/didn't know what happened (pubs in particular) makes people think the server was dropped or it's under a DDoS attack, resulting in a loss of players, particularly since the IP change messed up a number of peoples' favorites/history listings. Adding on that not everyone checks the forums, but perhaps just having a server announcement and/or Steam Group announcement would help (or do what we did with the Gmod server and rename the server to "Server moved to IP-HERE"

If we do plan on moving the rest of the servers, I'd highly suggest that a advanced notice be given so that we don't lose the players. Without the players, simply put, there isn't a community.

Just my thoughts on the matter (and my apologies if any of it came out rude..was not my intent)

EDIT: Something I might also suggest is posting a announcement on the Steam groups sometime soon with the new IPs we have so far for reasons mentioned above - might help get some players back.
 
Last edited:
This is what I posted in TF2 division. This brought up as well by them.

Hello Everyone,

We were unfortunately under a time crunch to move these servers around. With maul 2 and ddos going on, sometimes we forget about the small things so please for give us. We were working to get our servers moved over to the new hosting company with ddos protection. In the future we will have a better communication when things have changed.

With the IP's not changing over, the way valve has this setup is by using a special syntax used in the startup command. This is sv_setsteamaccount - When this is applied to the startup command, we have a webapi that gives us a token for that syntax. So anytime we change the ip it is matched to that token and everyone's favorites should have updated, but this time the did not for TF2.

Thus the reason about two weeks ago we changed them to the new host and then reverted back to the original host because of this issue. I did more testing and tried to find a solution before the 12th of January but I failed in finding a solution and had to switch the server to the new host. Sometimes things go our way and sometimes they don't.

Just remember we aren't here to hurt any division or any servers intentionally. We are doing our best to provide the best service possible.

-GGVW


For reference:
QuickPlay: https://support.steampowered.com/kb_article.php?ref=2825-AFGJ-3513
sv_setsteamaccount: http://forums.steampowered.com/forums/showthread.php?t=3222737
 
I went into dod at lunch today and was at 70. On Kalt, which was moved to the new server, it was at 110 tonight. Better than 200 last night.
 
I ran traceroute:

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 24 ms 27 ms 24 ms 12.83.78.137
5 83 ms 83 ms 82 ms 12.122.141.229
6 83 ms 83 ms 83 ms 12.249.190.6
7 96 ms 96 ms 131 ms tpa1-ar1-xe-2-0-0-0.us.twtelecom.net [66.192.251.214]
8 97 ms 99 ms 98 ms 66.162.27.46
9 * * * Request timed out.
10 97 ms 97 ms 97 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.
 
here's mine, but i have not even gone to the server yet!


Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 34 ms 21 ms 21 ms 67.166.181.1
3 10 ms 14 ms 10 ms ge-4-7-sr01.hopewell.va.richmond.comcast.net [68
.85.70.97]
4 8 ms 9 ms 9 ms te-2-3-ur01.petersburg.va.richmond.comcast.net [
69.139.206.194]
5 10 ms 10 ms 12 ms 162.151.58.5
6 15 ms 31 ms 16 ms so-7-1-0-0-ar02.charlvilleco.va.richmond.comcast
.net [68.86.172.74]
7 21 ms 19 ms 19 ms he-1-5-0-0-11-cr01.ashburn.va.ibone.comcast.net
[68.86.94.21]
8 33 ms 31 ms 31 ms be-10012-cr01.56marietta.ga.ibone.comcast.net [6
8.86.85.82]
9 28 ms 41 ms 30 ms he-0-10-0-1-pe04.56marietta.ga.ibone.comcast.net
[68.86.83.182]
10 26 ms 28 ms 30 ms as29802-1-c.56marietta.ga.ibone.comcast.net [23.
30.207.178]
11 * * * Request timed out.
12 * * * Request timed out.
13 37 ms 37 ms 39 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Is that good?
 
Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.251
2 * * * Request timed out.
3 2 ms 2 ms 2 ms 77-105-64-81.lpok.fi [77.105.64.81]
4 10 ms 7 ms 65 ms 87.236.154.12
5 3 ms 2 ms 3 ms 212.73.248.53
6 180 ms 180 ms 180 ms ae-0-11.bar1.Tampa1.Level3.net [4.69.137.109]
7 161 ms 160 ms 162 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
8 * * * Request timed out.
9 165 ms 166 ms 166 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.251
2 6 ms 2 ms 2 ms 77-105-107-2.lpok.fi [77.105.107.2]
3 1 ms 1 ms 1 ms 77-105-64-81.lpok.fi [77.105.64.81]
4 41 ms 6 ms 3 ms 87.236.154.12
5 2 ms 3 ms 2 ms 212.73.248.53
6 179 ms 179 ms 179 ms ae-0-11.bar1.Tampa1.Level3.net [4.69.137.109]
7 161 ms 167 ms 160 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
8 * * * Request timed out.
9 166 ms 165 ms 166 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Here is one connecting from Finland.
 
Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms BTHUB3 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 18 ms 18 ms 17 ms 31.55.185.228
5 23 ms 23 ms 22 ms 195.99.127.60
6 19 ms 20 ms 19 ms peer3-te0-1-0-5.telehouse.ukcore.bt.net [109.159
.254.249]
7 19 ms 18 ms 19 ms 166-49-211-246.eu.bt.net [166.49.211.246]
8 19 ms 19 ms 19 ms 82.112.101.73
9 33 ms 19 ms 19 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.5
4]
10 26 ms 28 ms 26 ms ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.1
98]
11 27 ms 26 ms 25 ms ae-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.4.1
26]
12 115 ms 115 ms 115 ms ae-6.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.1
76]
13 145 ms 145 ms 145 ms ae-1.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.8
7]
14 147 ms 147 ms 148 ms ae-1.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.1
11]
15 134 ms 134 ms 134 ms xe-0-1-0-14.r04.miamfl02.us.ce.gin.ntt.net [129.
250.202.242]
16 * * * Request timed out.
17 * * * Request timed out.
18 134 ms 133 ms 133 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

UK
 
here's mine, but i have not even gone to the server yet!


Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 34 ms 21 ms 21 ms 67.166.181.1
3 10 ms 14 ms 10 ms ge-4-7-sr01.hopewell.va.richmond.comcast.net [68
.85.70.97]
4 8 ms 9 ms 9 ms te-2-3-ur01.petersburg.va.richmond.comcast.net [
69.139.206.194]
5 10 ms 10 ms 12 ms 162.151.58.5
6 15 ms 31 ms 16 ms so-7-1-0-0-ar02.charlvilleco.va.richmond.comcast
.net [68.86.172.74]
7 21 ms 19 ms 19 ms he-1-5-0-0-11-cr01.ashburn.va.ibone.comcast.net
[68.86.94.21]
8 33 ms 31 ms 31 ms be-10012-cr01.56marietta.ga.ibone.comcast.net [6
8.86.85.82]
9 28 ms 41 ms 30 ms he-0-10-0-1-pe04.56marietta.ga.ibone.comcast.net
[68.86.83.182]
10 26 ms 28 ms 30 ms as29802-1-c.56marietta.ga.ibone.comcast.net [23.
30.207.178]
11 * * * Request timed out.
12 * * * Request timed out.
13 37 ms 37 ms 39 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Is that good?

Yes that is good.

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.251
2 * * * Request timed out.
3 2 ms 2 ms 2 ms 77-105-64-81.lpok.fi [77.105.64.81]
4 10 ms 7 ms 65 ms 87.236.154.12
5 3 ms 2 ms 3 ms 212.73.248.53
6 180 ms 180 ms 180 ms ae-0-11.bar1.Tampa1.Level3.net [4.69.137.109]
7 161 ms 160 ms 162 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
8 * * * Request timed out.
9 165 ms 166 ms 166 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.251
2 6 ms 2 ms 2 ms 77-105-107-2.lpok.fi [77.105.107.2]
3 1 ms 1 ms 1 ms 77-105-64-81.lpok.fi [77.105.64.81]
4 41 ms 6 ms 3 ms 87.236.154.12
5 2 ms 3 ms 2 ms 212.73.248.53
6 179 ms 179 ms 179 ms ae-0-11.bar1.Tampa1.Level3.net [4.69.137.109]
7 161 ms 167 ms 160 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
8 * * * Request timed out.
9 166 ms 165 ms 166 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

Here is one connecting from Finland.

Is this better than the dallas servers?

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms BTHUB3 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 18 ms 18 ms 17 ms 31.55.185.228
5 23 ms 23 ms 22 ms 195.99.127.60
6 19 ms 20 ms 19 ms peer3-te0-1-0-5.telehouse.ukcore.bt.net [109.159
.254.249]
7 19 ms 18 ms 19 ms 166-49-211-246.eu.bt.net [166.49.211.246]
8 19 ms 19 ms 19 ms 82.112.101.73
9 33 ms 19 ms 19 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.5
4]
10 26 ms 28 ms 26 ms ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.1
98]
11 27 ms 26 ms 25 ms ae-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.4.1
26]
12 115 ms 115 ms 115 ms ae-6.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.1
76]
13 145 ms 145 ms 145 ms ae-1.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.8
7]
14 147 ms 147 ms 148 ms ae-1.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.1
11]
15 134 ms 134 ms 134 ms xe-0-1-0-14.r04.miamfl02.us.ce.gin.ntt.net [129.
250.202.242]
16 * * * Request timed out.
17 * * * Request timed out.
18 134 ms 133 ms 133 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.

UK

Is this better than the dallas servers?
 
The pings are higher on the florida servers.
Everybody seems to get about +15-20 ms on there pings.

Tracing route to 67.228.175.243-static.reverse.softlayer.com [67.228.175.243]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.251
2 2 ms 2 ms 3 ms 77-105-107-2.lpok.fi [77.105.107.2]
3 1 ms 1 ms 1 ms 77-105-64-81.lpok.fi [77.105.64.81]
4 3 ms 3 ms 2 ms 87.236.154.12
5 3 ms 3 ms 2 ms 87.236.158.5
6 7 ms 10 ms 6 ms te4-2.cr9.mt.ax.as3238.net [194.112.2.174]
7 9 ms 9 ms 10 ms te3-4.cr1.kn7.sth.se.as3238.net [194.112.2.208]

8 * * * Request timed out.
9 38 ms 36 ms 36 ms ae7.bbr01.eq01.ams02.networklayer.com [50.97.18.
212]
10 112 ms 113 ms 113 ms ae1.bbr02.eq01.wdc02.networklayer.com [50.97.18.
214]
11 112 ms 114 ms 112 ms ae7.bbr01.eq01.wdc02.networklayer.com [173.192.1
8.194]
12 125 ms * 124 ms ae0.bbr01.tl01.atl01.networklayer.com [173.192.1
8.153]
13 144 ms 145 ms 145 ms ae13.bbr02.eq01.dal03.networklayer.com [173.192.
18.134]
14 145 ms 145 ms 145 ms ae1.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
15 145 ms 145 ms 145 ms po2.fcr04.sr05.dal01.networklayer.com [66.228.11
8.218]
16 145 ms 145 ms 145 ms 67.228.175.243-static.reverse.softlayer.com [67.
228.175.243]

Trace complete.
 
Last edited:
here's mine

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

C:\Windows\system32>
C:\Windows\system32>tracert 74.50.111.253

Tracing route to 74-50-111-253.static.hvvc.us [74.50.111.253]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.1.1
2 3 ms 3 ms 3 ms 100.103.23.177
3 656 ms 618 ms 649 ms host977300251.direcway.com [97.73.51.2]
4 621 ms 606 ms 659 ms host9773001752.direcway.com [97.73.52.17]
5 751 ms 764 ms 709 ms vlan122.car1.SaltLakeCity1.Level3.net [4.53.42.1
33]
6 798 ms 763 ms 683 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
7 * * * Request timed out.
8 700 ms 669 ms 679 ms 74-50-111-253.static.hvvc.us [74.50.111.253]

Trace complete.
 
To be rather frank, honest and blatantly obvious-

They moved the servers due to the lack of protection on the servers and as a result of the numerous DDOS attacks and server downtime (both TS and other division servers).

In a sense, the move and relocation of servers was to cover the rear-end of eGO from the rather humiliating downtime many servers had. And to justify the embarrassment of having to admit that server-security was not as it should be- and was left vulnerable.

So now they've moved the servers, upgraded to a decent, new and modern 'security' package/method- which has now been hammered into the community as costing more and needing more donations to eGO.

I wouldn't be surprised at some point if eGO decides to push forward a voluntary/mandatory (You know what I mean) donation from long-standing members.

Anyways, that's my view. I'm probably way off the ball, in another universe and even dimension. So I'll let this stew here for a bit, and come back when the meat had tenderised.

Fiction CAN be fun ladies and gents... You couldnt be more wrong, by the way. I think you are reading WAY too much into it. Please relax while they figure out how to route everything properly. It will get figured out, just be patient
 
I didn't now Donner/Avalanche were on a different box than Kalt/rotation, just seems a little weird...
 
I didn't now Donner/Avalanche were on a different box than Kalt/rotation, just seems a little weird...

Kalt and Rotation are the only ones that were moved so far. If I recall correctly, the other 2 are still being planned on moved.
 
If the move was necessary great! glad we made it for security purposes. Although I wish we could get those pings sometimes down it kills me when I do not see someone just appear out of nowhere after they shoot me. :) <3 I am not going anywhere eGO is to fun:)
 
If the move was necessary great! glad we made it for security purposes. Although I wish we could get those pings sometimes down it kills me when I do not see someone just appear out of nowhere after they shoot me. :) <3 I am not going anywhere eGO is to fun:)

Yeah im here more for the community and just love of the game instead of getting good scores. Where I live I never get below 120 ping :chair:
 

Latest posts

Back
Top