It appears that the issue is occurring again:
I’ve updated the original post with a list of items currently affected.
