Three buckets from three seperate sites (same account) all stopped syncing changes. CLI sync runs, sits, finishes, no output or changes.

I have three buckets under one account. For each one a server runs a sync via CLI V2 to it's dedicated bucket. I noticed that newer files weren't showing up. If I run aws s3 sync D:\MyFolder s3://mybucket, it will think about it for 5-10 minutes and finish with no output. I checked my credentials and region. No issues there. I can cp and rm files and folders in all three buckets. So access is there. It's like it runs and doesn't see changes. For the smallest bucket, I emptied, deleted, and recreated. That server was able to begin successfully syncing again. Bucket sizes are between 450GB-700GB. If I output the --debug information to a text file, I get an 85MB file with no clear errors. It's parsing the objects. I'm not sure what to look at next. I'd rather not delete and re-upload. Especially if this can happen again. Any guidance would be greatly appreciated. It's worth mentioning that that 85MB file with al the parsing was run against one folder with one item in it. Like it's parsing the whole bucket despite the narrow scope.