I had this issue last night. What was really odd was that algolia’s API was throttling - 429 error code - when I was connected to my wifi, but when I switched to my cell network it worked fine. Then this morning it worked fine on both.
Sure thing, we’re experimenting with some Load-Balancing heuristics and instrumentations, and it looks it got rate-limited by the engine who got surprised all traffic was coming from a single IP /o\",
We were experimenting some rate limiting settings and the load balancer IP in front of the hn cluster wasn't excluded, both features haven't been mixed before (doesn't make much sense to rate limit a search cluster behind a load balancer).
[HN Search admin speaking] We disabled the rate-limit for now. A load-balancer experimentation that didn't behave as expected (the LB's IP getting rate-limited).
Let’s say it was a mix of HN alerting (hnwatcher), good timing (Friday evening) and luck :) very happy to have seen this in time. Have a nice WE as well!
15 comments
[ 2.9 ms ] story [ 47.4 ms ] threadI'm testing from two separate internet connections, with different ISPs, in the same region.
If there's a way to provide more info or some kind of error, let me know.
And it's working for me now. Hope I didn't cause any panic; sorry about that.
It was "offline" for me and a friend for about an hour, but it's back up now. Might be some kind of intermittent issue.
edit (18 mins after this comment): it's blank again for me, and I'm getting a 429 error.
I must say I expected this post to kind of go into the ether, not for Algolia's VP of Engineering to reply with a solution within an hour :)
Have a nice weekend!