Scout was inaccessible from 1:50 – 2:28 PM PST (20:50 – 21:28 GMT). During this time, no data was collected from Scout clients and the Scout web interface was not available.

We care deeply about reliability and rely on Scout ourselves to monitor our own servers. While we do not have a Service Level Agreement (SLA), we want to compensate you if were negatively affected by the outage. Please contact us at support@highgroove.com and we’ll take care of it.

We have a load-balanced setup that is designed to handle a failure like this. Obviously, it did not perform. We will update this thread when we determine the cause.

Just to clarify—only one instance of the scout virtualized setup experienced problems and had to be rebooted. Only community plugins were affected by the downtime, which happens to be a majority of the plugins, and thus a majority of clients did not run plugins during this time. Clients were still checking in, thus monitoring still functioned. We are currently working on a solution to make sure this does not happen again.

Just a follow up—we now have a solution in place to ensure that if the server hosting the community plugins becomes unavailable, we can keep on chugging!