I can confirm there is no data I/O burst at that time, CPU/Memory usage was under average. Besides, there are another 2 loki stack with same configuration but even no data ingested, the error above complained as well almost at the same time:
If it happens at a specific time then it’s most likely not because of Loki itself. If it were a configuration issue I’d expect it to manifest much more frequently.
Check your kubernetes cluster, see if the containers are replaced at the time for some reason, or if hosts are replaced at the time for some reason. If you see it reliably during the time see if you can do a telnet test from one Loki container to another.