Ask HN: Is there a problem with HN Algolia search? | Hacker News Reader

Ask HN: Is there a problem with HN Algolia search?

31 pointsspk_8 comments

Everyday I come in the morning and go to https://hn.algolia.com/, and read the top items from the last 24 hours. However, today I noticed that there are no stories indexed for the last 24 hours https://hn.algolia.com/?dateRange=last24h&page=0&prefix=false&query=&sort=byPopularity&type=story

Not sure if this is a bug that I should be reporting to HN or ask a question to fellow peers who have similar routine as mine on how they are coping up today.

View on HN

I think it's the HN API. The problem also affects hnrss.org: https://news.ycombinator.com/item?id=33786127

HN's API is fine - most likely hnrss.org uses the HN Search API.

I've contacted Algolia and they're looking into it. More here: https://news.ycombinator.com/item?id=33790811

Edit: they've found the problem and are currently backfilling the missing data. If anyone still experiences trouble with HN Search after (say) 24 hours from now, please let us know at hn@ycombinator.com.

The algolia search is buggy sometimes, and hnrss would miss one or two posts for the front page

I think nobody is going test it thoroughly, it's not a big deal, just a bit annoying

I noticed that hnrss misses some of the second-chance pool stories (https://news.ycombinator.com/pool), I even raised a GH issue, only to be told that it is expected behavior of the system.

Why not use

https://besthackernews.herokuapp.com/

Though personally I read HN through

https://serializer.io/

with only HN enabled and other sites disabled, it allows also sync with other devices through unique URL, very practical. I just check first link ocassionally if I didn't miss something.

Yes, something is off. Yesterday it was 20h behind.

Two days ago this article was posted:

https://news.ycombinator.com/item?id=33755016

It details a stylometric grouping attack on users. I wonder if the API was killed in response?

Interesting, maybe some aggressive request limits have been put in place and hn.algolia.com was too aggressive in calling the API?

Reply on news.ycombinator.com