Table of Contents
I check Search Console every morning before coffee, mostly out of habit at this point after nineteen years in this business. So when the performance report stops updating, I notice fast. That’s exactly what happened over the weekend of October 11, 2026, and it was bad enough that it made the SEO news cycle.
What went wrong
The performance report in Google Search Console, the one that shows clicks, impressions, CTR, and average position, stopped refreshing on schedule. By Sunday morning, October 11, the data was running more than 64 hours behind. For a report that normally updates within a few hours, that’s a significant gap, not a minor hiccup.
Barry Schwartz at Search Engine Roundtable was the one tracking it closely, posting updates throughout the day as the lag number climbed and then, eventually, came back down.
Why this particular report matters
Search Console has plenty of components that lag from time to time. Indexing reports are notorious for it. But the performance report is the one most site owners and SEOs actually check daily, because it’s where you see whether your traffic is moving, whether a page dropped out of the results, or whether a recent change helped or hurt. When that data goes stale, you’re flying without instruments for a couple of days.
The timing lines up with the September spam update
This delay surfaced in the days following Google’s September 2026 spam update. That timing alone doesn’t prove a connection, Google systems have all kinds of moving parts, but when a reporting delay shows up right after a major update rolls out, it’s natural for the SEO community to wonder if the two are related.
It’s also worth noting this wasn’t an isolated glitch. Around the same period, third-party rank tracking tools were separately struggling to pull data from Google, a problem that had been building for weeks. Two different reporting pipelines running into trouble in the same stretch is the kind of thing that gets people asking questions, even without a confirmed cause.
Was this a sign of a core update coming?
Some people in the community floated the idea that the delay might be an early signal of a core update on the way. Schwartz pushed back on that theory in his reporting, saying he didn’t think the delay itself was the tell, even though there’s broad agreement a core update is due before long anyway. Worth separating the two: a reporting delay and an algorithm update are not necessarily connected just because they’re both circulating in the same news cycle.
How it resolved
The good news is this didn’t drag on. By 11am ET that same Sunday, the lag had already dropped from 64 hours down to 44. By the following morning, Monday, October 12, the report was back to normal. So the whole episode ran roughly a day and a half from first being noticed to fully resolving.
Google did not publicly comment on the cause during or after the delay, at least not as of this writing.
What to take from this if you manage sites
If you noticed a flat or frozen performance report that weekend, it wasn’t your property. It was a platform-wide delay affecting everyone pulling data from Search Console. The practical lesson is simple: when a core reporting tool goes quiet for an unusually long stretch, check whether others are seeing the same thing before you start troubleshooting your own site. In this case, patience was the right call, the data caught up on its own within about 36 hours.
