zlacker

[return to "Tell HN: HN was down"]
1. dang+zk[view] [source] 2025-12-17 18:09:25
>>uyzstv+(OP)
Yes, sorry! We're investigating, but my current theory is we got overloaded because I relaxed some of our anti-crawler protections a few days ago.

(The reason I did that is that the anti-crawler protections also unfortunately hit some legit users, and we don't want to block legit users. However, it seems that I turned the knobs down too far.)

In this case, though, we had a secondary failure: PagerDuty woke me up at 5:24am, I checked HN and it seemed fine, so I told PagerDuty the problem was resolved. But the problem wasn't resolved - at that point I was just sleeping through it.

I'll add more as we find out more, but it probably won't be till later this afternoon PST.

Edit: later than I expected, but for those still following, the main things I've learned are (1) pkill wasn't able to kill SBCL this time - we have a script that does that when HN stops responding, but it didn't work, so we'll revise the script; and (2) how to get PagerDuty not to let you go back to sleep if your site is actually still down.

◧◩
2. tsouka+KF[view] [source] 2025-12-17 19:43:14
>>dang+zk
During the last week my IP was banned for unknown reason. Glad to hear it might not be a problem from my side.
◧◩◪
3. dang+nb1[view] [source] 2025-12-17 22:28:44
>>tsouka+KF
Yes, sorry! This is the problem - we don't want to block legit users, but if we loosen the bolts, we get flooded.

If you browse HN while logged in, that should immunize you against this happening. Also, if it does happen again, you can unban your IP as described at https://news.ycombinator.com/newsfaq.html. But you have to do that from a different IP address, of course.

If those things don't work, email hn@ycombinator.com and we'll get it sorted.

[go to top]