We acknowledge that there was an issue 5 hours ago (relative to the time of writing) with our site. We have already implemented fixes to mitigate that specific issue and we will be analyzing logs in the future to see if this issue arises again.

We have taken the site offline for a bit for some maintenance. We’ll be back soon.

We looked at the server statistics again after a few hours and realized that we were getting the same performance degradation issue again.

Because we recently switched to NginX, we’re still working on a few kinks with the configuration. Please bare with us.

Although this is based on a preliminary analysis of server stats, we can announce that our site is now back at full speed.

Kudos to the Russian developers at NginX.

We understand our members are still receiving timeouts. We are working on fixing this.

We’re stopping all maintenance on the servers until we can figure out what is wrong and why our new kernel can’t be used.

We’re going to take the site down for about 10minutes for a reboot at about 2:20AM GMT.

We seem to have experienced a road block in our upgrade. We’re working on getting around this problem to finish the upgrade. The site will be up and down for the next few hours.

Everything is up and running again.

However, we identified a new bug yesterday that causes network performance to degrade over a period of time. To fix this, we need to upgrade our kernel to the latest version. This will mean that we will experience a scheduled downtime of up to 3 hours to rectify this and to make sure everything will be churning away as normal.

We will also take this opportunity to upgrade our MySQL version to the latest.

We will pull the servers offline at 3:30AM (GMT) today.

We’re down because of some network issue we didn’t see coming. This will be fixed in the next few hours.