Well, he is still responsible for the process through which the number was derived (assuming the process was put in place by him).
Pretty sure twitter have a dashboard with these numbers, and don't do it manually. So if this dashboard makes data up, I'm pretty sure VP of Product's head is on the table, since it's a really sensitive data to report wrong.
And twitter firing him can be a way to protect the top exec from the SEC, blaming him for everything.
If he's on paternity leave he won't have been responsible for a number that came out last week.