ersan

Yeah, battling DDoS attacks and trying to get DayZ 1.7.7 pushed out isn't fun. The attacks are actually delaying DayZCommander's release of 1.7.7 I think we got it up on DayZCommander for most CDN nodes now, we are trying to patch up the security holes that are allowing the DDoS attacks to be effective so we can get our servers back working again.

Very large DDoS attack today against at least 20 servers, 10+gbps - working on getting it mitigated.

We maintain compatibility with DayZCommander. We have requested the DayZCommander developer add the new version of Epoch, it should be added shortly and we will update the servers to the new version once this is done. EDIT: It looks like Josh added them either last night or this morning (I hadn't checked) - CK should be working on getting the arma patch and epoch updates provisioned today.

FWIW we are having a promo where it is $15 for the first month - https://dayz.st

DayZ has not issued official instance ID's in several months, the the only way to host an official server is to find a host that still has leftover ID's from when they were still being issued (we don't have any, I think Vilayer and H FB are the only ones with leftovers). The official recommendation has been to use private hives.

We're doing a promotion - $15 (50% off) for the first month for all server locations. Order normally at http://www.dayz.st and the discount is applied at checkout. Also you can cancel at any time (see http://dayz.st/w/Main_Page#Cancel_Server]here for info). Subject to availability.

Gray server names are 100% the fault of DayZCommander - we've asked Josh to fix it but he's been pretty busy lately.

Like I said, we are in talks with a datacenter in Chicago but that is a couple months out at best.

gamersdream servers have actually been the reason our servers are getting attacked, all of the machines on which they have servers are being repeatedly targetted. We have (or will soon be) given you the option to move to Los Angeles where your servers are protected from such attacks. We cannot continue hosting you at your current location if you continue to be a DDoS magnet. We have had many #1 and #2 servers on gametracker and they are usually ddos'ed off the face of the planet until they are downranked. We have had to sever relationships with several of the "top-ranked" servers because they are DDoS magnets and they affect all of our other customers. The DDoS protection offered in our Los Angeles location would cost hundreds or thousands of dollars, but we have a special agreement with Black Lotus that lets us offer it to you at the same price as our other non-protected datacenters. We suggest everyone take full advantage of the opportunity. Otherwise you are going to have a difficult time finding someone capable of hosting your servers stablely. Additionally, we have made no claims that the locations on which you chose to host your servers would be protected from DDoS - Los Angeles is the only location where we offer DDoS protection. Every other location has a "best-effort" policy. We are working on establishing a presence at a DDoS-protected datacenter in Chicago, but that likely won't be for 2 months. There are no overseas datacenters that offer decent ddos protection.

Servers updated to Namalsk 0.741 and ArmA2 Beta 103419 - Namalsk also now supports messaging, custom inventories, and buildings. I believe the EU hive node is now operational as well which should reduce lag for servers in Amsterdam, London, and Singapore.

We maintain our own branch of bliss/reality now. We intend to open source it at some point once we clean up the code.

99.9% of the time it seems to be servers with lines like 2 "" or 1 "" in any of the battleye filters - my recommendation is to remove any of those lines that log or writeout all events for any particular filter. If that doesn't fix it I took a look through all of the servers and found 3 at higher than normal loads and adjusted their max slots to compensate (but this takes some time as people need to move off or cancel), ams02 (159.253.131.97), lon01 (5.63.147.44) and wdc20 (50.97.53.250) were the ones I changed - they seem to have slipped past the automated load balancer. If you were on those lag might actually be our fault.

When one of our servers breaks you are always capable of switching to a different one - moving to a different location and back to Amsterdam will give you a new server and new IP - we usually try to remove the broken server from the pool. Hardware problems happen. Amsterdam is not protected from DDoS attacks, Los Angeles is. There are no DDoS protected transit providers outside of the US from what I have been able to research. I'm sorry your server has been down but we give you tools to get it running again. We have a lot more servers so we have a lot more aggregate problems than anyone else, other providers have the same issues just in smaller scale. Also feel free to contact admin@dayz.st about the downtime. We have a very liberal refund policy.

Or there could already be 5 people logged into RCon. 5 is the limit.

I apologize, I'm personally in Atlanta visiting my grandmother who's on her third round of chemo and cellkill is in charge of support. He just got back home from LA and should be working on the tier 3 e-mails now. We got some pretty devastating news from PayPal yesterday. They said that we were growing too quickly and we pose a high risk to them, so they are going to be putting a hold on all of our payments received until further notice, and once they have held an undisclosed amount they'll be holding 15% of everything we receive for 6 months. This severely limits us and depending on how much they hold initially it could be disastrous. We are getting ready to switch to credit cards only if comes to that. We were working on using a payment system that allows people to pay directly by credit card, reactivate cancelled accounts, change payment methods for an active subscription, and e-mail notices related to payment and invoicing, among other things. This is going to be priority one until we learn the fate of our PayPal account. I cannot stress enough how much people should NOT rely on PayPal for your business, I ignored all of the horror stories thinking they valued customers that had higher volumes, turns out it is exactly the opposite. For now we are still accepting PayPal and will be until they have more information for us (the risk management department does not respond to phone calls or e-mails), we will honor all PayPal subscriptions regardless of their decision and if we are forced to move away from PayPal we will try to work with all of our customers to make sure there is no lapse in services.

Yeah, it was a synflood attack on the main db/web server. It's back up now and should be harder to bring down that way. It was down for 39 minutes.

Didn't get any other reports of this as far as I know.

This happens when you or a program you are using changes your MySQL password. E-mail admin@dayz.st and someone will fix it when they are available.

Not that I know of, no. After it is on DayZCommander.

I apologize for the extended delay in support responses - I've become somewhat detached from DayZ.ST other than some high-level stuff (I am flying out to Los Angeles to oversee the two new cabinets and server installs on Wednesday) while I'm working on another project - I left my business partner in charge and there seems to be some confusion over what his responsibilities were and how the support system works. I think everything is straightened out now and e-mails will get answered in a more timely manner. There were only 3 or 4 e-mails in the inbox older than 3 days that I saw, yours was probably one of them, it should be answered shortly. Basically any questions that first and secondline support couldn't answer were just sitting there unanswered because they failed to flag them for the next level. I've instructed the last line of support to answer any e-mails older than 3 days regardless of whether or not they are flagged.

Unlikely, they are charging hosts commission to host the mod and last they talked to us our databases were not compatible with their map.

We usually host 20 servers per machine, some machines actually have dual xeon 2660's instead of 2620's which gives them 4 more cores, those can have up to 26 servers. I've posted before but our metrics are available here: http://ersan.us/src/munin/ - we monitor CPU usage pretty closely and if we see any problems we will adjust a machine's maximum allowed servers accordingly. Every instance is basically guaranteed a full CPU core, and since arma2oaserver is essentially single threaded if you are somehow using too many resources (if you see a core on the CPU history that is above 90%) that means you are actually maxing out an entire CPU core, which means there is nothing we can do about it. You'll have to find a way to reduce your CPU usage - be it through less vehicles, less players, less battleye filters, removing custom anticheats, etc. etc. Hardly ever is lag the fault of our hardware, it is almost always a server misconfiguration which the client is responsible for. I don't know who you are or what server you are on but if you want to check the statistics on your machine feel free to do so at the above link. It says very clearly on the contact page that IRC is for community support and for official support to e-mail us. Going in there to complain that your e-mails aren't getting answered fast enough isn't going to get you anywhere, sorry. I would take down the channel completely but a lot of people use it for its intended purpose, which is a knowledgebase and tool to collaborate on server customization with other people who run servers. I told toker and xir not to be rude to customers but if they feel like someone is causing a problem they are authorized to ban people.

Alright, here is the info for the Salt Lake City and Seattle server moves: Seattle 01 (50.23.131.224) -> Los Angeles 07 (192.31.185.206) Seattle 02 (173.192.170.117) -> Los Angeles 08 (192.31.185.207) Seattle 03 (50.23.131.226) -> Los Angeles 09 (192.31.185.208) Seattle 04 (173.192.170.85) -> Los Angeles 10 (192.31.185.209) Seattle 05 (173.192.170.98) -> Los Angeles 11 (192.31.185.210) Seattle 06 (50.23.131.230) -> Los Angeles 12 (192.31.185.211) Seattle 07 (50.23.131.238) -> Los Angeles 13 (192.31.185.212) Seattle 08 (173.192.170.97) -> Los Angeles 14 (192.31.185.213) Salt Lake City 01 (199.195.198.140) -> Los Angeles 15 (192.31.185.214) Salt Lake City 02 (198.105.218.156) -> Los Angeles 16 (192.31.185.215) Salt Lake City 03 (198.105.220.164) -> Los Angeles 17 (192.31.185.216) Salt Lake City 04 (50.115.124.92) -> Los Angeles 18 (192.31.185.217) Salt Lake City 05 (206.190.129.92) -> Los Angeles 19 (192.31.185.218) Salt Lake City 06 (206.190.134.36) -> Los Angeles 20 (192.31.185.219) Salt Lake City 07 (206.190.131.108) -> Los Angeles 21 (192.31.185.220) Salt Lake City 08 (206.190.132.84) -> Los Angeles 22 (192.31.185.221) Salt Lake City 09 (206.190.136.76) -> Los Angeles 23 (192.31.185.222) Salt Lake City 10 (206.190.132.4) -> Los Angeles 24 (192.31.185.223) Salt Lake City 11 (206.190.131.140) -> Los Angeles 25 (192.31.185.224) We will definitely be making the move before March 26th - if everything goes smoothly we should be making the move on March 20th. We will stop new orders for Salt Lake City and Seattle servers on March 15th and there will be warnings after you login to your control panel that the move is impending starting tomorrow. Here are some latency comparisons between the three datacenters: https://dl.dropbox.com/u/1956377/LAX.xlsx - TLDR: Los Angeles has a better network than the other locations, especially in Australia and Asia, and is very similar to Salt Lake in the US. Our LA datacenter will also be adding a new carrier soon so the pings should be even lower after that. We are making the move because we have started purchasing our own hardware and Salt Lake and Seattle are the two datacenters (besides Singapore) that have no DDoS protection whatsoever, whereas LA has amazing protection. They are also the two that are geographically closest to Los Angeles and we have less servers at those two locations combined than any other location (besides singapore). We are also looking at expanding into Chicago because we have access to a DDoS protected network there as well, this wouldn't be until at least next month though.

IRC is not an official support channel. Nobody there is required to answer any of your questions and nobody is paid to be there, they are all volunteers. Also we have a lot more than one customer asking for support at any given time. Our servers are not laggy at 50 players using default settings. Custom scripts, hundreds of vehicles, objects and buildings, and most importantly excessive battleye filters doing logging can cause your instance to lag. Well, it isn't, sorry. If you feel that is unacceptable then nobody is making you stay with us, some of our competitors make more lofty tech support claims but ours are pretty clearly outlined. We have roughly 3000 servers and 10 paid support representatives. It was very easy having a live 24/7 support system when we were smaller and receiving very few requests. Tech support does not scale linearly like the rest of the company. Our claim is 24 hours, which we do generally maintain, and are proud of given the nature of hosting DayZ. Again, IRC is not an official support channel, I don't know how much more clear I can make that. And this is not the real world it is the Internet where people have no issue cursing, spamming, hacking or ddos attacking us and our employees when they don't get their way. If you want a polite, considerate response from actual staff you need to e-mail us. I don't answer e-mails generally, but I don't see anything particularly old in the inbox. Feel free to PM me your question directly on these forums and I will try to answer it.

Yep, toker and xir don't work for dayz.st, they are IRCops on the IRC network who were volunteering their time to help moderate the channel. - IRC isn't official support it is community support as it says very clearly in the topic and on the contact us page (http://dayz.st/contact). For official support your only option is to e-mail admin@dayz.st as I've said repeatedly. It stopped being official support when most of our support team refused to moderate it because people were too rude, underinformed, demanding and unwilling to do any research. Plus it is incredibly time consuming. Now it is a place where other dayz.st customers can talk to each other about server customization, complaining about bugs and problems in there isn't going to get you anything but banned by whatever moderators are on at the time.