US1 Server Back

Post by **aem** » Mon Oct 13, 2014 4:04 am

I just set up US1 again. Same host, but could be on a different physical server. So we still need to make sure it performs at the same level it did in the past. If it does not work I would probably have to go back to US3. I will be shutting off US3 tomorrow. If for some reason we have any issues with US1 I will have US3 back up before Sunday.

I will try to check in tomorrow night to make sure things are going fine but helpful if you post here after you play real games on it.

Post by **Dome** » Mon Oct 13, 2014 4:49 am

Thanks AEM!

Post by **Papsmear** » Mon Oct 13, 2014 12:17 pm

Yes thanks AEM

Aeropagitica · Post by **Aeropagitica** » Sat Oct 18, 2014 4:48 am

Probably just me, but twice this week I have experienced 600+ ping and 99% ploss on us1. I have never experienced these symptoms on us 2 or 3

ledfist · Post by **ledfist** » Sat Oct 18, 2014 7:04 am

Aeropagitica wrote:QUOTE (Aeropagitica @ Oct 18 2014, 05:48 AM) Probably just me, but twice this week I have experienced 600+ ping and 99% ploss on us1. I have never experienced these symptoms on us 2 or 3

I have had similar issues, pretty much unplayable

blake420 · Post by **blake420** » Sun Oct 19, 2014 4:21 am

why can't we ever have nice things?

time to go server shopping again?

thank you AEM for your continued efforts!

Post by **aem** » Sun Oct 19, 2014 6:35 pm

Every time I have logged into check people are saying the server is working well. There is always a very small portion or players who will be affected negatively by a server change because they unfortunately get stuck with a bad "route" to the new server. Generally the increase in latency won't be enough to make it unplayable, but I have been increases of up to +200ms in the worst cases (average increase for bad route closer to like 40ms) .

600+ping and 99% ploss is far more extreme. Are you sure it is not something on your end? Also make sure you let the ping data settle down a bit after you join the server. For some reason it will report very high ping and packet loss right after you join a server. Check CSS when you are having extreme lag or packet loss and make sure you aren't getting it there.

As of right now the server options are:

US1: $18 per month
US3: $29 per month
Chicago: $25 per month (a bit to the west of US1-US3 server locations, increased latency for EU but should still be acceptable)

If US2 ($25) ever gets fixed we can try that again.

Other options up to $30 have been tested and were not good. Anything else is a significant price increase over these options.

edit: I should point out again that US1 and US3 are in the same datacenter and pings should be the same to both for most players. All it can take is a different IP for your ISP to put you on a worse route to the server though. So it is still possible a small number of players could have significantly different pings to US1 compared US3. As some players pings probably got a little worse to US1, others likely improved vs US3.

Aeropagitica · Post by **Aeropagitica** » Mon Oct 20, 2014 1:42 am

I cannot discount that the issue may be a local problem for me. But the symptoms are not consistent. It tends to happen well after 20 minutes into a game...I will get 3-4 minutes of warping and an inability to traverse alephs or dock, or rip. It is not merely a statistic being reported as soon as I join. typical #s for me are 60ms, 0%ploss for US3, 38ms, 0%ploss on US2, and 55ms, 0% ploss on US1. I am in North Carolina.

raumvogel · Post by **raumvogel** » Mon Oct 20, 2014 2:13 am

There are programs out there that allow you to change you're DNS server. That effectively changes the route to the game server.

HJ_KG · Post by **HJ_KG** » Mon Oct 20, 2014 3:25 am

no

Edit: More specifically, DNS DOMAIN NAME SYSTEM works like this;
You type example.com in a web browser.
Your computer looks up hosts file on its harddrive, if listed return value, if not next;
then it looks for a local network dns response, if listed return value, if not next;
then it will check isp, etc. till a value is returned.

At this point, your computer will now know that example.com is numerical value 93.184.216.119
So now your computer 'knows' the address of another computer.

Knowing the address location is not the same as getting there, while we as humans
can decide which roads to take to get to a destination, your computer cannot choose the route to another computer on the network.
There are many factors that result in the path that is given to connect your computer and the destination computer, none of these are under your control.

www.tldp.org/HOWTO/Unix-and-Internet-Fundamentals-HOWTO/internet.html