There's a delay as information makes its way from engineering to external comms.
Very likely, the indexing issue happened late in the afternoon after the comms person had gone home for the day (the tweet is 4:00 PM), a situation room was convened with a bunch of SREs and engineers with expertise, they sent an e-mail to external comms saying "Post that we're having issues with indexing", they got to work diagnosing the problem, they pushed a fix in a couple hours, and then they sent another e-mail saying "The issue is fixed."
The external comms person checks their phone after the kids have gone to bed, sees an urgent message about an indexing failure, posts that on the status blog, then checks the rest of their e-mail and sees that it's resolved, so they post that.
Very likely, the indexing issue happened late in the afternoon after the comms person had gone home for the day (the tweet is 4:00 PM), a situation room was convened with a bunch of SREs and engineers with expertise, they sent an e-mail to external comms saying "Post that we're having issues with indexing", they got to work diagnosing the problem, they pushed a fix in a couple hours, and then they sent another e-mail saying "The issue is fixed."
The external comms person checks their phone after the kids have gone to bed, sees an urgent message about an indexing failure, posts that on the status blog, then checks the rest of their e-mail and sees that it's resolved, so they post that.