Cody R.

Correct - this has been disabled as we do not allow our shared services to be used for proxies.

Unfortunately at this time we don't have plans on offering VPS services in Amsterdam.

This maintenance window has been completed.

The machine is online and booting services at this time. Please allow 10-15 minutes for everything to be restored to normal speeds.

The machine is currently rebooting from the maintenance.

This is about 90% complete at this time.

This is about 70% complete at this time.

This is about 30% complete at this time.

Maintenance will be starting in a few minutes.

Hehe, glad to hear it was handled promptly. Ideally the response time will be lower however sometimes there are more pressing tickets that will take precedence. We usually operate in a FIFO style - we'll do tickets in the order they come in and will get escalated if the issue is critical / something outside the scope of "normal" support. Please keep us posted on your experience with our support department - we really have tried to maintain the same level of support since our smaller days. Luckily in the past few months we've made huge logistical changes to our company (policy, tools) to help ensure things truck along smoothly. Cheers!

On Wednesday December 28th starting at 12am CST we will be taking the Hornet server down to run a file system check on one of the partitions the operating system is reporting to have issues. This is necessary maintenance as otherwise the problem could result in an unplanned outage and potential data loss if it's a file system check is not done within a reasonable time frame. We've set aside a window of 2 hours meaning the window ends at 2am CST. We estimate the actual file system check will take less than an hour to be completed so the estimated downtime will be around 1 hour. Date: 12/28/2011 Start time (CST): 12:00am End time (CST): 2:00am Duration: 2 hours Estimated Down Time: 60 minutes

It looks like you figured out the proxy - I'd suggest trying to use a mail client with SSL/TLS to see if those ports are open as it's generally a good idea to access your mail via an encrypted channel .

The FSCK and the machine is online. We'll be investigating what caused the initial crash and will schedule maintenance if it's necessary.

This is 70% completed at this time.

We're about 30% done with the FSCK at this time.

We're currently running a FSCK on the machine so we can get the machine online / investigate what exactly failed.

This machine crashed with a kernel panic due to what we believe is a hardware issue. We're currently having data center technicians investigate however at this time we believe some memory may have gone bad. We'll post more information once we have it.

Everything is now online. We'll be monitoring the server closely for the next 24 hours to ensure there are no further issues. To wrap up the delay / what happened this morning: * The machine crashed unexpectedly earlier on the 15th. We were able to get online and schedule a memory replacement of 8GB worth of RAM * The server crashed unexpectedly early in the morning of the 16th * We swapped out all of the memory ahead of the maintenance window due to crashes * After swapping the memory the machine had issues posting until the processors were re-seated. Once booted the machine showed only 12GB of RAM * After replacing the RAM again the machine failed to post a second time. We had the processors swapped and the machine posted / went online without issue Sorry for any trouble this may have caused

After replacing the RAM again the server is having trouble posting. We believe this is caused by bad CPU's so we're having these swapped out.

It appears the CPU wasn't seated correctly in the machine causing issues posting. The machine was booted successfully however half of the RAM (12GB) isn't showing so we're going to be bringing the machine down once more to swap out the RAM.

We're starting the memory replacement maintenance that was slated later for today to now due to instability issues. All further updates will be posted in that thread:

We're performing this replacement now due to instability issues. We'll update this ticket once it has been completed.

The sea005 machine unexpectedly went offline. We're currently having datacenter technicians take a look at what's wrong however it's starting to appear to be related to hardware. We'll post more updates shortly once we receive them.

Unfortunately there is no easy way to do this with the standard analytics software - your best bet is to let the visits / stats average out so the numbers are a bit more accurate. One thing you could look at is unique visitors which shouldn't count the same visitor for each request. I believe with Google Analytics you can filter down unique views for each request (IE: feed.xml) so that may be something you want to look into .

This maintenance window is closed.