I have not experienced this issue before. are you still observing this problem?
The journalctl log during the issue time might contain a clear reason for the problem.
My first thought was if there's backup running during that time, and I kept on reading until spotting it:
"Our backup infrastructure uses Bacula, and backups are executed on Fridays, so I'm wondering if increased I/O load could somehow expose an...