10:20pm EST - Most servers (including ours) have had a lot of trouble today. I've gotten our server back up on new IP/Port combinations more than 10 times only to have them go down again within a matter of minutes. I'm working on finding a new place to host which is better at mitigating DDoS attacks. Given the scale of the attacks today, my question is: Are they directed at individual servers or a central source at Facepunch? I do not know, either way, I look forward to servers running smooth again soon!

6:45pm EST - This is a frustrating weekend for Rust. Our server continues to be attacked. I am going to take a little break from all this, make myself a drink and a cheeseburger. I'll check back in a bit.

6:00pm EST - After going down 5 times in a row, it is clear this is not simply an issue with trees. It appears we (and most other servers) are experiencing some form of attack. I'm exploring advanced DDoS protection options but as of yet they are too cost prohibitive ($200+ a month). If you have any suggestions or want to offer any support, please contact me at rustafied(at)gmail(dot)com or via steam. As always, I'll keep you up to date with updates as I have them.

5:10pm EST - After mass server outages starting Friday night, an update came out yesterday afternoon which has restored peoples ability to join servers. Unfortunately, it introduced some new issues into the mix. Most crippling being: Tree's are spawning out of control.

All servers are suffering from this. Most official servers are down or not join-able. Our server lasted about 24 hours until the 200,000 tree mark struck and my box died. I rebooted and updated today's server update (v51), came back up and we crashed in 5 minutes. I reverted to yesterdays server version (v47) and started again. It has just crashed again.

I will note: Given a fresh wipe server has crashed on me twice now, it leads me to think this is not related to the tree issue entirely. I don't know if there is some sort of attack or system wide error happening.

I'll post updates on twitter as I have them.