The wrong person wrote that message
Missed an opportunity to make a joke about root cause analysis of the root CA audit data loss.
Addressed to "Many of you" -- So, uh, guys, we're not 100% sure which roots are impacted (is that important?).
This is likely an error on our side -- We don't know how this happened and the one person capable of reading the log files is not present, or we don't log, or it was malicious activity from some unknown third party.
It looks like it rolled back to an old backup -- again, we have some logging issues to resolve. No idea what happened, but it's possible that the system spontaneously decided to initiate a restore, or maybe Todd in storage was messing with snapshots...
lost data for about 147 roots -- I know, specific huh? Anyway, the mail log guy was available and he tells us that there were 146 similar emails sent along with the one we got a panicked reply about. So, yeah, we think 147 is about right. But maybe not.
If you received a message -- But the mail log guy is not quite as competent with regex so, while he was able to identify the message content match, he might have munged the To: field. Alternately, they discovered that the initial message was poorly crafted and likely caught in spam filters.
Please don't panic -- You really should panic
Sorry for the confusion -- Really? Sorry for the confusion. How about "Sorry for the fuck ups"