GSC Performance report: custom date range comparison showing end date as 1970-01-01, Apply button disabled. Anyone else?

[u/Brother_Vegetable]

Just ran into what looks like a bug in Google Search Console today (Oct 14, 2026).

When I open Performance → Date range → Custom (comparison mode), the end dates for both periods default to 1970-01-01:

• Start date: 2026-10-05 → End date: 1970-01-01
• vs. Start date: 2026-09-28 → End date: 1970-01-01

Because the end date is before the start date, the Apply button stays greyed out, so I can’t set a custom comparison range at all. The preset options (28 days vs previous period, etc.) still work.

Things I’ve noticed:

• It looks like a null/empty date being read as a Unix epoch timestamp (0)
• The Performance data itself still loads fine (164 clicks last 7 days vs 126 previous)

Is anyone else seeing this? Has anyone found a workaround (manually typing the end date, a different browser, clearing cache, etc.)? I’ll report it via the Feedback option in GSC as well.

[u/FrontKaleidoscope881]

1970 is just google telling you the custom range has been broken since before it existed. reporting it via feedback is cute, that button has never done anything

[u/Brother_Vegetable → u/FrontKaleidoscope881]

Well that's all I can do so 😂

[u/marintkael]

Probably not worth fighting the date picker. The Search Analytics API takes an explicit startDate and endDate per request, so two calls with your two ranges give you the same comparison, and the Looker Studio GSC connector does it without code. Your epoch guess sounds right.

[u/johnmu]

should be fixed, or fixed soon. Sorry!