Between 2:56 and 3:13 PM CET, approximately half of Memsource Editor for Web users were affected by a failure of one ElasticSearch node. This was caused by faulty operating memory which prevented the creation of a new index. This node was removed from the cluster for memory replacement and the issue was resolved.