6 ms·
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 t
by hypewatch 6y ago
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.
- ciarannolan 6y agoI tried on my regular home internet, then my cell phone, then had a friend who's in the same geographic area as me (but different ISP) try it.
- redox_ 6y agoThanks for sharing, this is surprising as the rate-limit should be per IP :/ Investigating.
- redox_ 6y agoShould be good now.
- hypewatch 6y agoThanks! It’s a small world on HN haha. What was the issue? If you don’t mind me asking
- redox_ 6y agoSure 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\
- slashvar2701 6y agoWe 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).