Service Interruption Warning

Amazon is doing some maintenance this weekend/early next week to address the Shellshock security issue.  We don’t know when this will affect our servers, but it will cause an interruption in service.  We will bring everything back up as quickly as we can, and I will update this status as we have more information.

W3C Validation test

If you are using cutting edge HTML5 in your sites, you may find that the W3C validator results are incorrect.

Sitebeam puts so many requests through the validator that we have to keep a local copy on a scaling group of servers.  On occasion, the W3C will update their validator, and it takes time for us to get a copy functioning on our servers.  Updating the validator isn’t an automatable task, and can take anywhere from 2-10 hours. This unknown period of time needs to be scheduled in around regular development activities, and thus it can take a week or two when we become aware of a change to be able to implement a new copy on our servers.

We are working on the validator today, and will update this post when it has been resolved.

[UPDATE] We have pulled the latest available copy from the W3C, however this does not seem to have resolved the issues with RDFa.  It may be the W3C has not made the latest version available yet.

Incoming Links issues

Moz’s API is currently down, which means that reports may come through without incoming links data, or may fail completely.  We are aware of the issue and are awaiting more information from Moz to get this resolved.

Sitebeam unavailable for some installs

We are aware of an issue that has started a few minutes ago that is preventing some of our users from accessing Sitebeam.  We are working on it now and will update this page as soon as we have more information.

This issue has now been resolved.  Downtime for the installs involved was roughly 14 minutes.

Delays in report running

We are aware of an issue that started about 40 minutes ago involving reports sitting in the queue for over 20 minutes before they started to run.  We have identified the issue and the reports are running now, we expect the queue to be cleared within the hour.