To everyone that is experiencing this issue, does it involve accessing much older records, say before 1500's?
I know there is issues with vandals in the high traffic high viewable areas of the Middle ages that detach like 400 random records from the middle ages and attaches them all as children to one record. See GXJW-2WP for an example.
Then when they have enough of these single parent PIDs, then they will add as a spouse some other high value PID. It then results in a log of 400 merges, then they will detach the parents and results in 400 unmerges. They do this to dozens, with 400 children each, and they do this over and over again. This all is creating a huge mess of the log files, and I'd image it could cause other issues, as already described.
I can only guess that the vandals goals are to create a Denial of Service situation. They are creating such a huge garbage in garage out situation that no one will ever want to use this site.
At this moment, FamilySearch has no way to keep vandals from creating a new account after they are identified and deleted. Frankly, this site should never have come online, without a provision already in place to prevent folks from freely creating a new account.
On the other hand, they could be experiencing processing shortages from the 1950 census records introduction. But the above described issues can't be helping this either.
Pardon my userID. I am involved and don't want the vandals tracking me.