From 22:58 to 23:32 UTC (2017-08-09), an unresponsive node in our search cluster caused a portion of requests to our management API to fail with a 500 response. The unresponsive node was restarted, and we have not seen further errors since then. We will investigate the cause and determine what follow-up actions are required.