After doing some investigating during our transition between server it seems we had a bit of DNS desync. The old server was getting decommissioned so I setup a new hosting environment with new server names to match. For whatever reason name.com didn't propagate the new server details to everyone equally. Some were loading the old server, some were loading the new server, neither database was communicating with eachother from the desync fork point. I could attempt to restore the old server's DB but that will mean all the posts made on this DB will be lost not from the point of merge, but the original desync date on the 25th.
Either way posts and data will be lost due to the unexpected name server difficulties. At this point, it is deciding what database we keep. It is something that must be decided soon as more data will be lost the longer we take to decide. That being said I am leaning toward leaving things as they are as it seems the least obtrusive and will require the least work from me. I really am not in a position to work on the server right now as I am in the middle of a 3 week trip to Japan and wifi access has been unreliable and my phone is unbearably slow, free data being limited to 2G speeds while roaming.