Can confirm in 3.32.9. This happens when system time changes. Workaround: load each affected world once and save/quit to reset the timestamp to 0.