This incident has been resolved.
May 21, 16:31 UTC
The data migration is complete. We are monitoring the situation now to verify that it has been resolved.
May 21, 15:43 UTC
The node has been dropped from rotation and the remaining nodes are recovering. We are planning to migrate affected users off of this hardware, so there will be a brief period (up to 5 minutes) of read-only mode during the migration.
May 21, 15:35 UTC
The operations team has identified the underlying issue and is working on a fix.
May 21, 15:10 UTC
We have been paged in response to an issue affecting an Elasticsearch 5.3.2 node in the US-East region.
May 21, 14:36 UTC