Google’s most-used reporting tool went quiet this weekend, and the timing could not be more awkward. Barry Schwartz reported on Sunday morning that the Search Console performance report was more than 64 hours stale, a delay he called incredibly unusual for this particular report. Performance data normally refreshes within a few hours, so a gap approaching three days is the kind of thing that makes every practitioner check whether it is just their own property. It is not, the delay is affecting everyone.
This is the report that usually just works, which is why the delay matters. Search Console has routine delays in the page indexing report and several of the enhancement reports, and nobody blinks at those anymore. The performance report is different because it has been the dependable one, the screen that agencies screenshot for client reports and that site owners open every Monday morning. The last time it fell this far behind was December 2025, and Google took a while to acknowledge that episode too. As of Sunday, Google had still not commented on this one, which follows the same pattern as the December episode.
The timing is what makes this sting. The September 2026 spam update finished rolling out on October 8, and right now SEOs are trying to assess exactly what it did to their sites. The performance report is the one window into post-update clicks and impressions that Google gives you directly, and it is fogged up at the exact moment you need it clear. To make matters worse, the third-party tracking tools have had a rough few weeks scraping Google’s results, so the independent data that usually fills the gaps is thinner than normal. Everyone is flying with partial instruments.
Speculation started immediately, and some of it is already overheating. A few voices are calling the delay a sign that a core update is about to drop. Schwartz pushed back on that reading, though he agreed that a core update should be coming soon regardless. I land on the cautious side here, because Google has never used reporting delays as a signal of anything, and the industry has a long habit of inventing ghosts out of infrastructure noise. A late report is a late report until Google says otherwise, and inventing patterns out of infrastructure noise is how practitioners talk themselves into breaking things that were fine.
While the data is stale, my approach stays deliberately simple:
- Change nothing. Decisions made on stale data are guesses dressed up as analysis, and guesses made right after a spam update finishes are how you undo recoveries that were quietly working.
- Write down the gap. Add an annotation in your analytics platform noting the delay window, so that a dip or a jump you see next week does not get misread as a traffic event.
- Lean on the 24-hour view. The short-window data in Search Console runs on separate infrastructure and has stayed current through this episode, which gives you a rough pulse while the main report catches up.
- Cross-check with your server logs and GA4. If Search Console is your only source of truth about search traffic, this weekend is your reminder that it was never really the truth, just the most convenient window into it.
History says the data will come back and it will be backfilled. Google fixed the December 2025 episode eventually, even though it was slow to confirm there was a problem at all. The pattern this time looks the same, with the 24-hour view still collecting, which suggests the collection pipeline is fine and only the reporting aggregation is stuck. Be patient and resist the urge to rewrite your September spam update analysis until the numbers are complete, because decisions made on partial data rarely survive contact with the full picture.
Failon’s POV: A reporting delay is an operational hiccup rather than a strategy event, which is exactly why most people overreact to it. The practitioners who get hurt by this are the ones with no measurement redundancy: no log analysis, no analytics annotations, no client-facing process for the days when the data is late. I would spend this week building exactly that redundancy, because there will be a next outage. The September 2026 spam update taught everyone to watch their data closely, and my earlier piece on the Gemini UTM parameters rollout showed how attribution keeps getting more fragmented, not less. The through line is the same, and it keeps showing up in every outage. When the dashboard goes dark, the people with three ways to see traffic keep working, and everyone else starts guessing.
