Yeah, it took a while, but we added a second Chicago-based machine providing 8 gameservers in addition to the 8 NFO-Chicago gameservers. Due to tragicservers going away we had to get a bunch of extra capacity in NA on short notice. This has resulted in having too many machines right now (compared to the amount of money coming in from premium), so we're planning to get rid of the Dallas and North Carolina locations as these are the most expensive, and the least popular we think. Let us know here or on Discord if you disagree.

This would leave NA with these locations/servers:
Kansas City 1: 4 gameservers
Kansas City 2: 20 gameservers
Chicago (NFO): 8 gameservers
Chicago 2: 8 gameservers
Los Angeles: 8 gameservers

In EU we had to cope with a price hike for one of the datacenters we use (i3d), but we did that by getting a better deal on the servers in France. So you might've noticed 2 new French DDoS-protected machines (BaguetteBrigade/CroissantBrigade) that are taking the place of the 2 machines we had before.
We're also looking to retire the aging FakkelBrigade machine (hosting EU serveme.tf and some gameservers) after almost 8 years of service and replacing it with a modern 6-core machine.

Assuming it's a linux server, install 'gdb' and start the server with -debug. Let it crash, check the debug.log for clues.

Because it's an all-volunteer site on a $0 budget while being under constant DDoS attacks. And now the EU pugchamp anti-DDoS system is refusing connections from my DDoS protected EU servers.

This is why we can't have nice things.

We're still waiting for our tragicservers to come back, so in the meantime we're adding some new servers and locations to na.serveme.tf to have some more options and capacity. Also, one of our machines from our Kansas location is having more and more issues, so we're looking to phase that one out soon.

First of all, 8 new gameservers in Chicago (NFOservers), these are live right now. We'll also be adding 8 more Chicago servers from a different company/datacenter soon. That server is paid for, but out of stock at the moment.

Also live now from a different datacenter/company in Kansas City, 16 gameservers running on a 12-core machine, a bit like Kroket/BolusBrigade in EU.

Because a rapist might just reset your stream key during a LAN if you don't fully control the channel.

Edit: My lawyers inform me I should stick to "alleged rapist and known stream saboteur"

Two things, first, for EU players, please use the anti-DDoS servers for official/casted matches and TF2Center games.

Second, for NA players, our long term sponsor Tragicservers (<3) is changing their infrastructure, so while that's happening we're down on capacity in NA. Once the move is completed I'll have to try and integrate their new gameserver control panel with na.serveme.tf.

This might prove to be difficult, even though I have used their new control panel software succesfully before (TCAdmin at Simrai), that was thanks to the exceptional access granted to me by SimRai, because TCAdmin at the time didn't allow you to restart servers (through an API) without extensive administrator privileges.
So bear with us while we wait for this move to be finished.

We all moved to Brink.

https://youtu.be/UVoloVvsupM

Your routing to the server is bad. I have access to a server in the same 139.99.xxx.xxx range and when I run a trace from that server in Singapore to your ISP it goes through France before going to Malaysia.

Tonight's TF2 update came right at the time a lot of people launch their EU matches (21:00 CEST), the update was large and the steam servers for server downloads slow or at least varying wildly in performance. This caused the update to take anywhere between 2 and 20 minutes. These long update times were experienced on servers from all the geographical regions we provide. They're still slow now, timing out while servers try to get the latest version info.

Since people are used to <5 second server boot times, many people ended their reservations within a few minutes (while the update was still running), and made new ones. This didn't help the situation as this had a chance of triggering a bug in Valve's steam server update tool causing the update process to freeze while trying to shut down, this left a handful of servers in this frozen state.

Luckily it seems everyone managed to get a working server within 15 minutes or so, but I'm not yet sure how to improve this situation. If an update drops close to match times, is big, and steam is slow, we're going to have a bad time.

Because they're Taiwanese, so Blizzard has to show the Chinese they're serious about protecting their interests.

I didn't sneeze, but something did forcibly leave my nose while reading this excellent post.

It's on all serveme.tf servers, but it's the "official" one by F2. That's because the sigafoo one points to F2's auto-update URL for this plugin, so it automatically downgrades itself xD

I'll fix that later. Thanks for letting me know alba, check your private messages for a little gift.

Update: Fixed, running the sigafoo version with the uber-pause-fix, but modified (source) so it won't commit sudoku

Some more updates:

- Greatly increased the average server launch speed. The system will now try to do a fast start of the server (takes between 1 and 5 seconds). If there's a TF2 update or the server is unreachable, the system does the old, slow start (35 seconds). The on-demand cloud servers are still fast at about 20 seconds.
- Added auto-updater for plugins and configs. Stole that idea from RGL, cheers
- Fixed the double response when you had plugins enabled and typed !rcon commands in chat
- Added a little ping refresh button on the reservation form, don't spam it, the TF2 server will ban you
- If you're from NA and end up on EU serveme.tf, we'll now suggest you try na.serveme.tf. With RGLs season in full swing there are lots of new faces visiting from NA and we did a poor job of directing them to the right region.

Cool idea, I've uploaded the current maps to serveme.tf and have given you serveme premium so you can upload updated or new maps.