We're working (as always) on the lag as the event progresses.

The new server had a "remember" cookie set, so if you got assigned to it, it wouldn't let you get traffic from the other web servers. That's great except then it crashed, and never came back up, and if you ever were on it you couldn't get off :/

Just fixed it!

We're working on it. Making big code changes over the past few weeks to ensure we can switch to a better processing engine means significant improvements, but a little bumpy until we get there. It also means doing it during a time when we have this much traffic is the best way to test one server.

Unfortunately it had a setting that gave all of the people who got put on that server a cookie that stuck them on that server. That settings been turned off and a "health watch" has been enabled on the server so if it goes down it gets removed from the load balancer.