Search Console Hit by 64-Hour Data Delay and a Date Picker Stuck in 1969; Google Log Lists 10 Issues in 2026

Ras Al Khaimah, United Arab Emirates, 15 October 2026.

Google Search Console users have had a difficult week. The Performance report fell more than 64 hours behind on 11 October, and on 13 and 14 October its custom date picker repeatedly failed, with the end date stuck in 1969. Both problems were reported by Search Engine Roundtable and later cleared, and Google had not commented publicly on either at the time of that coverage. As of 15 October, Google's own Search Console data anomalies page lists ten known data issues dated 2026 and none yet for October.

What happened

The data delay. On Sunday 11 October, Search Engine Roundtable reported that Performance report data in Search Console was more than 64 hours behind at about 7am Eastern time, against a usual delay of a few hours. The gap had narrowed to about 44 hours by 11am the same day, and the report appeared back to normal on the morning of 12 October. The publication noted that the delay came shortly after the September 2026 spam update finished rolling out; Google's Search Status Dashboard lists that update as running from 24 September to 8 October. There is no evidence from Google that the two are related.

The date picker bug. On 13 October, users reported that choosing a custom date range in the Performance report failed: the end date showed as 1969 (one user saw 1 January 1970), and changing it produced an error. Preset ranges such as 7 days, 28 days and 3, 6, 12 and 16 months kept working. According to Search Engine Roundtable, the bug was fixed that morning, broke again on the morning of 14 October and was fixed again later that day.

A 1969 or 1970 date is the usual sign of a date value being read as zero in Unix time, which starts on 1 January 1970. Google has not said what caused the fault.

What Google's own log shows for 2026

Google keeps a public record of known Search Console data problems from the last 3 to 16 months. We reviewed every entry dated 2026 on 15 October. Neither of this week's problems appears on it.

Date(s) as listed by Google	Report	Issue
13 August	Discover (and Generative AI in Discover)	Logging error lowered clicks and impressions
13 to 17 August	Generative AI in Search	Logging error lowered impressions; data restored on 21 August
24 June	Discover (and Generative AI in Discover)	Logging error lowered clicks and impressions
21 May	Discover	Logging error lowered clicks and impressions
7 May onwards	Performance report	FAQ rich results no longer shown, so FAQ impressions drop
7 May onwards	FAQ rich result report	Same FAQ retirement, reflected in the rich result report
7 to 8 May	Discover	Logging error lowered clicks and impressions
16 to 27 April	Performance report	"Job listing" and "Job details" appearance types not reported
3 April	Performance report	Logging error meant impressions were not reported accurately from 13 May 2025 to 27 April 2026; clicks unaffected
28 February and 1 March	Bulk data export	Two days missing for some properties and will not be recovered

Three patterns stand out. Discover data was hit by logging errors on four separate occasions in 2026. The long-running impressions error, which Google says it resolved, means any year-on-year comparison spanning May 2025 to April 2026 should be read with care, because impressions, CTR and average position were affected. And the two days missing from bulk exports in February and March are permanent gaps for affected properties.

Google's note on that impressions error says that, now it is resolved, sites may see a decrease in impressions in the Performance report. Only impressions and related metrics were affected, according to Google; clicks were not.

Context

Search Console has added several new data views this year, including Generative AI performance reports introduced in June and, on 24 September, web multimodal search reporting covering Lens, Circle to Search, image uploads and Chrome's "Search this image". Each new report is a new data source to log, and two of this year's ten anomaly entries already concern the Generative AI reports.

Search Engine Roundtable noted that the last comparable Performance report delay was in December 2025, and that Google took some time to confirm that issue.

What to do

• Annotate this week. Mark 11 to 14 October in your reporting so a late or partial data pull is not mistaken for a traffic change.
• Use preset ranges or the API while the picker is unreliable. Preset date ranges kept working during the bug, and the Search Analytics API and bulk export are separate from the web interface's date picker.
• Check the anomalies page before diagnosing a drop. Four Discover logging errors in one year is a reminder to rule out a reporting fault first.
• Re-baseline impressions. If you compare against May 2025 to April 2026, note Google's impressions logging error in any report to stakeholders.
• Store your own copy. The two unrecoverable bulk export days show why teams relying on Search Console data should keep their own archive.

Conclusion

Neither of this week's Search Console problems changed the underlying data as far as is publicly known: the delay cleared within about a day and the date picker was fixed twice. Google has not commented on either, and neither appears on its anomalies log.

The log itself is the more useful record for planning. Ten entries in 2026, four of them Discover logging errors and one an impressions error spanning almost a year, are a reason to check Google's notes before reading any sharp change in Search Console as a real shift in search performance.

Questions and answers

Was the Search Console date picker bug fixed?

According to Search Engine Roundtable, the custom date picker broke on 13 October 2026, was fixed that morning, broke again on 14 October and was fixed again later that day. Preset date ranges kept working throughout.

Did Google confirm the Search Console data delay?

Google had not commented publicly at the time of reporting, and neither this week's delay nor the date picker bug appeared on Google's data anomalies page when we checked on 15 October 2026.

Where does Google list known Search Console data problems?

On its Data anomalies in Search Console help page, which records known issues from the last 3 to 16 months.

How many Search Console data anomalies has Google listed for 2026?

Ten entries dated 2026 as of 15 October, including four Discover logging errors, the FAQ rich result retirement (listed in two reports), an impressions logging error, a Job listing reporting gap and two missing bulk export days.

###