All depends on curator settings.
If You run clustered setup, check where Your curator instance is running:
Once You identify the active machine, check when curator was last run
systemctl status curator-forcemerge
Check the logs
journalctl -u curator-forcemerge
The output should be like :
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index logstash-cf-acmefoto_access-2019.16
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index logstash-cf-waf-2019.16
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-json_appmon-2019.16
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-kubernetes-microservices-prod-2019.16
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-acme-portal-2019.17
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-oneclick-2019.17
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index logstash-cf-other_access-2019.17
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-portal-secure-2019.17
Jul 24 04:00:02 energylogserver01 curator[432105]: 2019-07-24 04:00:02,871 INFO ---deleting index filebeat-json_appmon-2019.17