Our uptime in February 2013 was a whopping 100%. We’re pretty pleased with this figure, as it included a number of improvements deployed to most of the components in our system, including an update to Elasticsearch itself.
There were two minor hiccups in the service not accounted for in our uptime reports.
On the 21st, we had a few hours during which index creation requests were failing due to a regression deployed with our multi-index syntax support.
Another was on Monday the 25th, when an Elasticsearch node was restarted abruptly to recover from unusual load and memory usage, without having been removed from our load balancers. During that time, a fraction of requests routed to that node would have failed until our load balancer noticed and removed it from the rotation.
