Google’s time filter in its search engine broke a few days ago, sparking confusion among users who rely on it to narrow results by date. The glitch Reid Mwichary posted about on Mastodon and shared on Hacker News highlighted how the filter returned no results or incorrect timestamps, disrupting workflows that depend on recent data.

Mwichary’s brief note triggered a flurry of comments on Hacker News, where the community quickly identified the symptom: the time picker was selecting the wrong range, often defaulting to an empty set. Google_manifested the issue after a backend update that inadvertently altered the query parameters for the time filter. Users reported similar problems across vneve and other sites that embed Google search.

Google’s engineering team acknowledged the bug and is working on a fix, promising the time filter will be restored soon. In the meantime, users can manually edit the query string to enforce a date range or use third‑party tools.

The incident underscores the fragility of large search infrastructures and the importance of rigorous regression testing for seemingly minor features such as the time filter.