Our workers are currently not processing data and we are investigating why.
**Edit 13:30** Everything has caught up and fixed itself now. The problem was related to adding a new node to our Elasticsearch cluster in combination with a restart of one of the nodes during a period of shard synchronization.
**Edit 13:40** As we plan to rotate more Elasticsearch nodes today, this issue will be kept open as a reference should further processing problems occur.