Just had a search server fail, moving a set of indexes to a new server starting now.

Amazon is reporting network issues in our datacenter, although we aren't seeing any errors yet, just a heads up - status.aws.amazon.com/

All indexes should be fully functional, please let us know if you have any issues. Apologies again. The root cause: serverfault.com/questions/40…

The linux leap-year issue appears to have hit our servers - we're rebooting the servers & reloading indexes one by one now

All indexes should be up and recovering or fully available now - contact us if you are still having problems. We apologize for the outage

We're trying to launch workers in another AZ to move indexes over...

Our host provider (Amazon EC2) has acknowledged connectivity issues, status here: status.aws.amazon.com/

We're seeing several indexes down, looking into the problem now.

We had a blip of 502 errors for some indexes - pretty sure we found & fixed the cause.

We had several minutes of downtime at about 4pm CT, things are up again.

Looks like there was about a minute of connectivity issues at AWS us-east datacenter that affected @getsearchify, we're monitoring it now

We had 46 failed API add document requests at about 2:15pm Pacific time due to a backup causing too much disk I/O. Everything's good now.

All systems go!