zlacker

Tell HN: HN was down

submitted by uyzstv+(OP) on 2025-12-17 16:48:18 | 599 points 313 comments
[source] [links] [go to bottom]

- HN errored on all authenticated requests with 502 Bad Gateway. It did still respond to a limited amount of unauthenticated requests with presumably cached pages, which did not get updated. The last post on /newest claimed "0 minutes ago", but was actually much older (1:32:57 PM GMT) and not the newest post.

- This status page actually identified the outage: https://hackernews.onlineornot.com/ - Pages by Hund and Statuspal did not show the outage.

- The last post before the outage was https://news.ycombinator.com/item?id=46301823 (1:39:59 PM GMT). The last comment was https://news.ycombinator.com/item?id=46301848 (1:41:54 PM GMT).

- There was an average of ~4 seconds per comment just prior to the outage. Based on this, HN likely went down at 1:41:58 PM GMT.

replies(60): >>markus+e >>spoone+g >>ortusd+q >>zelphi+C >>sltr+D >>manbit+F >>sosode+M >>busymo+61 >>silver+71 >>rzerow+b1 >>voxleo+e1 >>Fergus+k1 >>wavemo+U1 >>ashf02+V1 >>wek+Z1 >>zzixp+h2 >>fatty_+o2 >>pedro3+t2 >>ProofH+03 >>bennyd+63 >>steven+n3 >>numpad+K3 >>chiste+24 >>esafak+54 >>al_bor+74 >>rob+i4 >>dhruv3+J4 >>thatge+a5 >>khaled+B5 >>Elfene+Q5 >>neurol+16 >>sangee+m6 >>neurol+G6 >>gaigal+S6 >>liampu+y7 >>arbirk+48 >>rustac+Q8 >>ajdude+39 >>agumon+v9 >>russel+ga >>Purple+pa >>gepiti+Eb >>Silver+Wb >>Kim_Br+sc >>daniel+od >>dvaun+ff >>laCour+Sf >>arm32+5h >>oidar+th >>xxs+Aj >>dang+zk >>steve_+Gl >>bossyT+Po >>khobra+ss >>whynot+Cv >>dustfi+8D >>codykl+3P >>compli+JV >>Aperoc+pw1 >>ramong+uf2
1. markus+e[view] [source] 2025-12-17 16:49:08
>>uyzstv+(OP)
Yes was down for me. Ontario, Canada.
2. spoone+g[view] [source] 2025-12-17 16:49:18
>>uyzstv+(OP)
Yes
3. ortusd+q[view] [source] 2025-12-17 16:50:12
>>uyzstv+(OP)
Looks like 3 hrs

https://hackernews.onlineornot.com/incidents/yaz-eOJeARBL

https://downforeveryoneorjustme.com/hacker-news

Strangely, nothing from the statuspal, which is the first google result

https://hacker-news.statuspal.io/

replies(1): >>rozenm+O
4. zelphi+C[view] [source] 2025-12-17 16:51:36
>>uyzstv+(OP)
Yep "having trouble serving my request" or so.
5. sltr+D[view] [source] 2025-12-17 16:51:37
>>uyzstv+(OP)
Yeah I couldn't log in for a bit this morning. It's concerning how often and how many times I tried. Glad it's resolved.
replies(1): >>imiric+t3
6. manbit+F[view] [source] 2025-12-17 16:51:43
>>uyzstv+(OP)
TIL I have a "open Hacker News" hand reflex
replies(17): >>kevin0+42 >>thesur+83 >>Andrew+A3 >>jstumm+E5 >>ChrisM+H7 >>ectosp+89 >>wincy+C9 >>1shoon+ma >>select+Ee >>numpad+5g >>lysace+Tj >>direct+Ip >>nottor+fz >>cbrack+C41 >>Errone+H91 >>yigith+lQ1 >>lockni+L12
7. sosode+M[view] [source] 2025-12-17 16:52:05
>>uyzstv+(OP)
Yes, and I'm a little ashamed to admit my morning routine wasn't the same without it.
replies(1): >>fedreg+E3
◧◩
8. rozenm+O[view] [source] [discussion] 2025-12-17 16:52:19
>>ortusd+q
Interestingly it stayed up if you weren't logged in.
replies(5): >>jedber+J2 >>davnic+K2 >>smalle+f4 >>bryanr+O5 >>Izkata+u8
9. busymo+61[view] [source] 2025-12-17 16:53:37
>>uyzstv+(OP)
I run the app called HACK and received user emails that the HN website was down.
replies(1): >>maverw+32
10. silver+71[view] [source] 2025-12-17 16:53:37
>>uyzstv+(OP)
Yes, was down for me too this morning
11. rzerow+b1[view] [source] 2025-12-17 16:53:52
>>uyzstv+(OP)
Yes
12. voxleo+e1[view] [source] 2025-12-17 16:53:58
>>uyzstv+(OP)
Yes, it' been out for me too, southern hemisphere, GMT -03
13. Fergus+k1[view] [source] 2025-12-17 16:54:03
>>uyzstv+(OP)
Yeah & chatgpt was trying to gaslight me - claiming it was my fault. Happy to put that bum in its place...
replies(1): >>chiste+H6
14. wavemo+U1[view] [source] 2025-12-17 16:56:04
>>uyzstv+(OP)
When it was down my thought was "damnit, I'll actually have a productive workday now."
replies(2): >>dwa359+a4 >>tzs+n4
15. ashf02+V1[view] [source] 2025-12-17 16:56:13
>>uyzstv+(OP)
Yes, and on one request I saw a message like "Restarting server - this won't take long", and soon after it's back up.
16. wek+Z1[view] [source] 2025-12-17 16:56:20
>>uyzstv+(OP)
Yes, it was down for a few hours
◧◩
17. maverw+32[view] [source] [discussion] 2025-12-17 16:56:25
>>busymo+61
Thank you for HACK. I love it!
◧◩
18. kevin0+42[view] [source] [discussion] 2025-12-17 16:56:33
>>manbit+F
I did not know how addicted I was to HN until today lol
19. zzixp+h2[view] [source] 2025-12-17 16:57:11
>>uyzstv+(OP)
First AWS/Azure/Cloudflare and now HN?!?
replies(2): >>imiric+R3 >>philip+v4
20. fatty_+o2[view] [source] 2025-12-17 16:58:13
>>uyzstv+(OP)
I got irrationally angry when it refused to load the website
replies(2): >>DonHop+O3 >>imvetr+X3
21. pedro3+t2[view] [source] 2025-12-17 16:58:30
>>uyzstv+(OP)
Yes, I got an error message, but I cleared my cookies and was able to access.
◧◩◪
22. jedber+J2[view] [source] [discussion] 2025-12-17 16:59:13
>>rozenm+O
If you aren't logged in you get a cached version from the CDN/cache. Reddit works the same way.
◧◩◪
23. davnic+K2[view] [source] [discussion] 2025-12-17 16:59:13
>>rozenm+O
that'll be because it's served from cache when you're not logged in
24. ProofH+03[view] [source] 2025-12-17 16:59:49
>>uyzstv+(OP)
I wake up, and look at HackerNews lol. This morning sucked hahaha
25. bennyd+63[view] [source] 2025-12-17 17:00:08
>>uyzstv+(OP)
Yes, I had to touch grass this morning.
◧◩
26. thesur+83[view] [source] [discussion] 2025-12-17 17:00:13
>>manbit+F
Same! Right there with "every day must begin with coffee"
27. steven+n3[view] [source] 2025-12-17 17:01:12
>>uyzstv+(OP)
https://www.stevenjgarner.com/HN-Down-2025-12-17-07-48-UTC-0...
◧◩
28. imiric+t3[view] [source] [discussion] 2025-12-17 17:01:34
>>sltr+D
Next time try not to beat a dead horse expecting it to resurrect. :)
replies(1): >>mlhpdx+xc
◧◩
29. Andrew+A3[view] [source] [discussion] 2025-12-17 17:02:03
>>manbit+F
It just reinforces for me that addiction is a human problem not a problem with technology

I know dang basically works tirelessly to not change the format in order to not induce those addictive patterns

but yet here we all are

replies(3): >>chiste+u4 >>dzink+47 >>Purple+E7
◧◩
30. fedreg+E3[view] [source] [discussion] 2025-12-17 17:02:10
>>sosode+M
This was more impactful to my day than the last AWS and CloudFlare outages...
replies(1): >>messe+Q4
31. numpad+K3[view] [source] 2025-12-17 17:02:24
>>uyzstv+(OP)
Could have been accidental flagging of sorts. Didn't work on PC for few minutes while showing fine on phone.
◧◩
32. DonHop+O3[view] [source] [discussion] 2025-12-17 17:02:31
>>fatty_+o2
You handle your irrational anger much better than whatevermrfukz who keeps pooping his pants.
replies(1): >>fatty_+E4
◧◩
33. imiric+R3[view] [source] [discussion] 2025-12-17 17:02:42
>>zzixp+h2
We can live without the former, but not HN!
replies(1): >>gjsman+64
◧◩
34. imvetr+X3[view] [source] [discussion] 2025-12-17 17:03:05
>>fatty_+o2
you could refuse to be angry to mock it
35. chiste+24[view] [source] 2025-12-17 17:03:23
>>uyzstv+(OP)
It was the first time since I started using this website (August last year) that it was down.

I'm still impressed nonetheless.

I'd like to know what caused the outage and how it could have been prevented, for learning purposes.

36. esafak+54[view] [source] 2025-12-17 17:03:28
>>uyzstv+(OP)
A lot of the outage indicators failed. Someone needs to create an outage indicator reliability dashboard.
replies(3): >>Nextgr+B4 >>chiste+K4 >>arionm+95
◧◩◪
37. gjsman+64[view] [source] [discussion] 2025-12-17 17:03:29
>>imiric+R3
You won't be employed without the former.
38. al_bor+74[view] [source] 2025-12-17 17:03:32
>>uyzstv+(OP)
Is this still a valid account for HN status? It says it’s the official one, but with the changes at Twitter to no longer show chronological feeds (at least for users that aren’t logged in), it’s rather useless. The top 5 listed post (for me) are seemingly random from 2014 - 2022.

https://x.com/HNStatus

Is there a better place to check, beyond a basic down detector that may provide more insight or signal that the outage is acknowledged?

replies(4): >>zipy12+R4 >>Furiou+Da >>alexfo+gO >>dang+171
◧◩
39. dwa359+a4[view] [source] [discussion] 2025-12-17 17:03:46
>>wavemo+U1
hahaha
◧◩◪
40. smalle+f4[view] [source] [discussion] 2025-12-17 17:04:06
>>rozenm+O
That only worked for a while, eventually I couldn't load comment pages even logged out.
41. rob+i4[view] [source] 2025-12-17 17:04:08
>>uyzstv+(OP)
Maybe PG is more involved now and hired the "10,000 lines of AI code a day" person who made a deployment mistake?

https://x.com/paulg/status/1953289830982664236?s=46

◧◩
42. tzs+n4[view] [source] [discussion] 2025-12-17 17:04:14
>>wavemo+U1
Next time you can avoid that fate by opening HN in a private browsing (or whatever your browser calls its equivalent) window. This outage, like the vast majority of HN outages, only affected logged in requests.

I suppose you could also just clear your HN cookies in regular browsing window, but then when they fix it you'd have to log in again.

replies(3): >>neom+ed >>dpolon+ok >>ycombi+mR
◧◩◪
43. chiste+u4[view] [source] [discussion] 2025-12-17 17:04:31
>>Andrew+A3
It's a website with the smartest people in the world. The level of conversations here are unrivaled in internet communities.

It's understandable to be addicted. Lol.

I visit this place multiple times a day.

replies(7): >>fwip+S5 >>the_af+r9 >>phanta+Od >>linhns+4j >>steve_+Yk >>andrep+ar >>krapp+981
◧◩
44. philip+v4[view] [source] [discussion] 2025-12-17 17:04:40
>>zzixp+h2
Time to update the meme: https://preview.redd.it/cloudflare-had-a-rough-day-today-and...
◧◩
45. Nextgr+B4[view] [source] [discussion] 2025-12-17 17:04:49
>>esafak+54
A lot of them got fooled by the caching; pages for signed-out users are cached heavily and those kept returning successful responses even if the actual backend server was down.
replies(1): >>dizhn+L6
◧◩◪
46. fatty_+E4[view] [source] [discussion] 2025-12-17 17:04:55
>>DonHop+O3
Interesting that you mention that, how do you keep track of his comments? Some sort of plugin/scraper?
replies(1): >>Jtsumm+t6
47. dhruv3+J4[view] [source] 2025-12-17 17:05:14
>>uyzstv+(OP)
I was quiet surprised really. HN almost never goes down.
replies(1): >>Aachen+Wc
◧◩
48. chiste+K4[view] [source] [discussion] 2025-12-17 17:05:16
>>esafak+54
And an outage reliability indicator for that outage reliability indicator.
replies(1): >>willis+wf
◧◩◪
49. messe+Q4[view] [source] [discussion] 2025-12-17 17:05:36
>>fedreg+E3
At least during those outages I could procrastinate on HN.
replies(1): >>the_ar+Hi
◧◩
50. zipy12+R4[view] [source] [discussion] 2025-12-17 17:05:41
>>al_bor+74
https://hn.hund.io/ Is a status page, no idea if official or not, but it didn't register here for some reason.

I didn't read the post text, it's identified there haha, my bad! I wish the text post text wasn't grey, I gloss over it too easily.

replies(2): >>lagnia+F6 >>laCour+ug
◧◩
51. arionm+95[view] [source] [discussion] 2025-12-17 17:06:33
>>esafak+54
So a downdetectorsdowndetector.com but for Hacker News?
52. thatge+a5[view] [source] 2025-12-17 17:06:36
>>uyzstv+(OP)
Thought for a second I got banned for something lol
replies(3): >>elxr+6b >>Aachen+xf >>verzal+Rh
53. khaled+B5[view] [source] 2025-12-17 17:08:37
>>uyzstv+(OP)
It was down if you tried to access it while authenticated (i.e. you have a cookie). It was loading fine for unauthenticated sessions (e.g. incognito).
◧◩
54. jstumm+E5[view] [source] [discussion] 2025-12-17 17:08:43
>>manbit+F
I say. Vibe coded 4 apps once I got past that, on my way to half a billion in ARR already.
◧◩◪
55. bryanr+O5[view] [source] [discussion] 2025-12-17 17:09:18
>>rozenm+O
also went down if you went to login, and people's individual pages were also down. So as far as I saw the front page was up as long as you were not logged in, however I'm not sure if that wasn't just luck of the draw, I had one experience where it looked like maybe the front page was sometimes down for not logged in users as well.

on edit: ok others pointed out it was cached pages I saw. explains it.

56. Elfene+Q5[view] [source] 2025-12-17 17:09:28
>>uyzstv+(OP)
I got stuck in an infinite loop.

Try opening HN -> it's down, better check HN to see everyone talking about a major website being down -> Try opening HN -> loop

replies(7): >>neom+Vc >>HPsqua+Gk >>mustak+qr >>RJIb8R+fF >>Imusta+WL >>Rendel+o91 >>Errone+y91
◧◩◪◨
57. fwip+S5[view] [source] [discussion] 2025-12-17 17:09:39
>>chiste+u4
It's really not 'the smartest people.' It's people interested in tech, and often in making-a-lot-of-money-in-tech. It does have a lot of people with significant industry experience, which is cool.
replies(1): >>workso+I9
58. neurol+16[view] [source] 2025-12-17 17:10:00
>>uyzstv+(OP)
Yup, France here , Paris 1809.

HN was down about an hour ago.

Glad to see it back !

Cheers.

59. sangee+m6[view] [source] 2025-12-17 17:11:28
>>uyzstv+(OP)
Thought it had something to do with some model updates, like Gemini Flash 3 for a moment.
◧◩◪◨
60. Jtsumm+t6[view] [source] [discussion] 2025-12-17 17:11:59
>>fatty_+E4
> how do you keep track of his comments?

You can just look at them, turn on showdead in your profile and you'll see a bunch of flag-killed comments in this discussion by whatevermrfukz. No need for a plugin or scraper.

replies(1): >>fatty_+N7
◧◩◪
61. lagnia+F6[view] [source] [discussion] 2025-12-17 17:12:47
>>zipy12+R4
This site said HN was fine and green the entire time it was down.
62. neurol+G6[view] [source] 2025-12-17 17:12:57
>>uyzstv+(OP)
Hi, Got an error an hour ago on phone, not loged.

Anyway, glad to see you back.

Paris 1812.

Cheers from France.

◧◩
63. chiste+H6[view] [source] [discussion] 2025-12-17 17:13:00
>>Fergus+k1
You use ChatGPT to know if a site is down?
◧◩◪
64. dizhn+L6[view] [source] [discussion] 2025-12-17 17:13:09
>>Nextgr+B4
This site also got it right: https://downforeveryoneorjustme.com/hacker-news

I believe it's because they accept user reports.

replies(1): >>esafak+D7
65. gaigal+S6[view] [source] 2025-12-17 17:13:42
>>uyzstv+(OP)
I got confused by the "minutes ago" thing.

Working with full dates in the HTML and doing a tiny JavaScript that calculates the "minutes ago" would actually be a neat improvement.

◧◩◪
66. dzink+47[view] [source] [discussion] 2025-12-17 17:14:13
>>Andrew+A3
This one is at least healthy-ish for the mind. I’d much rather hacker news than any other news. Social Media is an emotional rage-bait cesspool these days. If it’s not for Hacker News those of us who abstain from the rest would be living in the dark.
67. liampu+y7[view] [source] 2025-12-17 17:16:10
>>uyzstv+(OP)
Smart. Have to use that error budget before year end...
replies(1): >>dylan6+y8
◧◩◪◨
68. esafak+D7[view] [source] [discussion] 2025-12-17 17:16:21
>>dizhn+L6
Yes! Now we see what a difference it makes.
◧◩◪
69. Purple+E7[view] [source] [discussion] 2025-12-17 17:16:24
>>Andrew+A3
But, would the addiction become worse if HN changed, or would there be a point where they could cure it?
replies(1): >>ZuoCen+Gn1
◧◩
70. ChrisM+H7[view] [source] [discussion] 2025-12-17 17:16:32
>>manbit+F
So do I, but it was such a shock that I just passed out, and when I woke up, it was back up.
replies(1): >>ZuoCen+Vn1
◧◩◪◨⬒
71. fatty_+N7[view] [source] [discussion] 2025-12-17 17:17:01
>>Jtsumm+t6
thank you
72. arbirk+48[view] [source] 2025-12-17 17:18:04
>>uyzstv+(OP)
We need a serious post mortem for this
◧◩◪
73. Izkata+u8[view] [source] [discussion] 2025-12-17 17:19:31
>>rozenm+O
Not completely, I'm not logged in on my work laptop and it was only working some of the time (and not like some pages were cached and some weren't, I was refreshing the same page and sometimes it worked and sometimes not).
replies(1): >>cess11+49
◧◩
74. dylan6+y8[view] [source] [discussion] 2025-12-17 17:19:36
>>liampu+y7
I always hated the late use-it-or-loose-it at the end of the year where you end up buying the things that were denied requests from earlier in the year. You just cost me half a year of using the damn thing.
replies(1): >>wiredp+191
75. rustac+Q8[view] [source] 2025-12-17 17:20:30
>>uyzstv+(OP)
I'll admit this ruined my morning
76. ajdude+39[view] [source] 2025-12-17 17:21:12
>>uyzstv+(OP)
I was able to view the site without being signed in (i.e. private window) but any browser I was logged into wouldn't load.

I'm sure it's a coincidence but it started working again shortly after emailing hn@ycombinator.com

◧◩◪◨
77. cess11+49[view] [source] [discussion] 2025-12-17 17:21:13
>>Izkata+u8
That's how I concluded that it wasn't a ban on my account but rather more serious.
◧◩
78. ectosp+89[view] [source] [discussion] 2025-12-17 17:21:27
>>manbit+F
I learn more reading the comments here than anywhere else. Thanks everyone for my addiction.
◧◩◪◨
79. the_af+r9[view] [source] [discussion] 2025-12-17 17:22:42
>>chiste+u4
> It's a website with the smartest people in the world.

Nice joke!

At least, I hope it was a joke...

80. agumon+v9[view] [source] 2025-12-17 17:23:02
>>uyzstv+(OP)
hn applied ycombinator too strictly
◧◩
81. wincy+C9[view] [source] [discussion] 2025-12-17 17:23:25
>>manbit+F
I’ve turned on no procrast mode and set it to ten minutes per hour. Helped me a lot!
replies(1): >>HanCli+Ge
◧◩◪◨⬒
82. workso+I9[view] [source] [discussion] 2025-12-17 17:23:41
>>fwip+S5
> It's really not 'the smartest people.'

This was especially obvious during Covid, I even stopped visiting because the comment section was so crazy.

83. russel+ga[view] [source] 2025-12-17 17:26:00
>>uyzstv+(OP)
HN being down makes you start wondering about the differences between routine, addiction, compulsion, and habit.
◧◩
84. 1shoon+ma[view] [source] [discussion] 2025-12-17 17:26:30
>>manbit+F
If you're looking to put the brakes on that, I've used LeechBlock to add a 5-second timer to opening a new HN window (along with other block schedules). The timer even fails if it loses focus, so it really helps slow you down.

https://www.proginosko.com/leechblock/

replies(3): >>squeef+Ph >>embedd+Bu >>mgarci+xx4
85. Purple+pa[view] [source] 2025-12-17 17:27:06
>>uyzstv+(OP)
In other words, productivity in tech skyrocketed for hours..though it seems some work was flavoured with irrational anger.
◧◩
86. Furiou+Da[view] [source] [discussion] 2025-12-17 17:27:42
>>al_bor+74
Only way I have figured out how to to change the "Following" sort order back to chronological is from the mobile app: click the down arrow on the "Following" tab. Change the sort from "popular" to "most recent."

Seems to reset it on the web view, too.

replies(1): >>al_bor+mo
◧◩
87. elxr+6b[view] [source] [discussion] 2025-12-17 17:29:05
>>thatge+a5
I thought I was being rate-limited for opening posts too fast, which has happened before.

After more than an hour I thought, "wow this is pretty harsh" and "so much of my exposure to learning things is directly tied to HN posts". I was lost lol.

88. gepiti+Eb[view] [source] 2025-12-17 17:31:10
>>uyzstv+(OP)
Athens, Greece yes it was down.
89. Silver+Wb[view] [source] 2025-12-17 17:32:21
>>uyzstv+(OP)
I tried to refresh an embarrassing amount of times
90. Kim_Br+sc[view] [source] 2025-12-17 17:34:14
>>uyzstv+(OP)
In with the rest, yes, and my first thought is always "I have an internet outage" when HN is down. :-P
◧◩◪
91. mlhpdx+xc[view] [source] [discussion] 2025-12-17 17:34:50
>>imiric+t3
So now we call the refresh button CPR?
◧◩
92. neom+Vc[view] [source] [discussion] 2025-12-17 17:36:58
>>Elfene+Q5
Yeah me too. Wake up -> HN down -> That's weird, oh well it's usually only down for a few minutes -> I should check if HN is still down -> That's weird, oh well it's usually only down for a few minutes -> I should check if HN is still down -> loop.

That was a few hours ago. I'm glad this loop is broken.

replies(1): >>squeef+Fh
◧◩
93. Aachen+Wc[view] [source] [discussion] 2025-12-17 17:37:01
>>dhruv3+J4
You don't visit enough my friend :)

It's down about 8.4 minutes per week. On 26% of days it doesn't work at least once, and on 12% of days it has more than one consecutive failed check. The longest uptime streak was 24 days

I've been keeping track since exactly 2 years (to the day!) because I was surprised that it seemed briefly down for me on a daily basis. Was I getting unlucky and hitting it every time, or was it just down very often? Nobody posted anything so I started answering the question for myself :p

I've been meaning to post the tracker to HN but there's a pesky bug I want to fix: the "is it currently down" stat. I don't know how this is beyond me but something in the code bugs out. So this is my first time posting about it

replies(1): >>ayewo+TI
◧◩◪
94. neom+ed[view] [source] [discussion] 2025-12-17 17:38:07
>>tzs+n4
Is it my imagination or did they used to automatically serve you a logged out page when it was down?
95. daniel+od[view] [source] 2025-12-17 17:38:40
>>uyzstv+(OP)
As soon as I noticed it was down I came to hacker news to post about it, but...
◧◩◪◨
96. phanta+Od[view] [source] [discussion] 2025-12-17 17:40:39
>>chiste+u4
99% of social science or political topics and 50% of technical topics here do not… read as smart, and you’d be much better off spending the same time reading the first chapter of a relevant 101-level college textbook.
replies(1): >>seizet+ng
◧◩
97. select+Ee[view] [source] [discussion] 2025-12-17 17:44:02
>>manbit+F
I already knew that. :)
◧◩◪
98. HanCli+Ge[view] [source] [discussion] 2025-12-17 17:44:12
>>wincy+C9
What are you using to control this?
replies(2): >>randal+vp >>bee_ri+Np
99. dvaun+ff[view] [source] 2025-12-17 17:46:27
>>uyzstv+(OP)
Will we get a post mortem?
◧◩◪
100. willis+wf[view] [source] [discussion] 2025-12-17 17:47:42
>>chiste+K4
We apologize again for the fault in the fault indicator. Those responsible for sacking the people who have just been sacked have been sacked.
◧◩
101. Aachen+xf[view] [source] [discussion] 2025-12-17 17:47:43
>>thatge+a5
Your comment history doesn't sound IP-ban-worthy. Is there an alt that has you worried? :P
102. laCour+Sf[view] [source] 2025-12-17 17:49:18
>>uyzstv+(OP)
I'm with Hund. Our hn.hund.io page did not catch this because it was requesting the cached, unauthenticated page. It now monitors authentication as well.
replies(3): >>jonahx+hg >>joncra+pg >>sammy2+QT
◧◩
103. numpad+5g[view] [source] [discussion] 2025-12-17 17:50:03
>>manbit+F
obligatory: https://xkcd.com/477/
◧◩
104. jonahx+hg[view] [source] [discussion] 2025-12-17 17:50:57
>>laCour+Sf
Is this a mistake by hund, or the configuration of hund by HN?
replies(1): >>laCour+Qg
◧◩◪◨⬒
105. seizet+ng[view] [source] [discussion] 2025-12-17 17:51:17
>>phanta+Od
It's entirely possible that this is the smartest place on the internet, but also often dumb. In fact, it seems likely. More of an indictment of the rest of the places on the internet.
replies(3): >>squeef+Ji >>ssdspo+js >>the_af+6J
◧◩
106. joncra+pg[view] [source] [discussion] 2025-12-17 17:51:23
>>laCour+Sf
Thank you. I was thinking myself or my corporate IP was shadowbanned
◧◩◪
107. laCour+ug[view] [source] [discussion] 2025-12-17 17:51:44
>>zipy12+R4
This was monitoring the unauthenticated news page, which is why it didn't catch it. It now monitors authentication as well. It is not official, and was made by a co-founder years ago.
replies(1): >>eddyg+Qm
◧◩◪
108. laCour+Qg[view] [source] [discussion] 2025-12-17 17:53:21
>>jonahx+hg
Mistake on our part (Hund) for not monitoring authentication. This page is unofficial and was made by a co-founder several years ago.
109. arm32+5h[view] [source] 2025-12-17 17:54:22
>>uyzstv+(OP)
The "site status" apps are all smoke and mirrors, how unreliable.
110. oidar+th[view] [source] 2025-12-17 17:55:50
>>uyzstv+(OP)
What was the longest that HN has been down? I feel like this is up there.
◧◩◪
111. squeef+Fh[view] [source] [discussion] 2025-12-17 17:56:55
>>neom+Vc
sounds very much like an evil social media dopamine feedback loop. ironic given everyone on HN is so anti social media.... its clearly only bad for kids though i should add, silly of me to exclude such a detail
replies(3): >>neom+oj >>bee_ri+tp >>ptsd_d+UV
◧◩◪
112. squeef+Ph[view] [source] [discussion] 2025-12-17 17:57:44
>>1shoon+ma
so youve got the willpower to do something about it but not enough to just stop doing it?
replies(3): >>dwedge+Vi >>1shoon+3m >>MikeTh+Yv
◧◩
113. verzal+Rh[view] [source] [discussion] 2025-12-17 17:58:18
>>thatge+a5
Me too and I was wondering what I did!
◧◩◪◨
114. the_ar+Hi[view] [source] [discussion] 2025-12-17 18:01:43
>>messe+Q4
I felt like changing HN down page to show top 30 posts from this week before or after the generic message.
◧◩◪◨⬒⬓
115. squeef+Ji[view] [source] [discussion] 2025-12-17 18:01:49
>>seizet+ng
> It's entirely possible that this is the smartest place on the internet,

i cant find the link, but there was a post about how to "be nice" and it was a revelation to a worrying amount of "geniuses" on here. bare in mind the sum total of the advice was "be nice, dont be rude"

replies(1): >>seizet+QW
◧◩◪◨
116. dwedge+Vi[view] [source] [discussion] 2025-12-17 18:02:21
>>squeef+Ph
Have you never suffered from habitual reflexes? I blocked twitter for a while in my hosts file and a dozen times over those first few days I instinctively opened a new tab and typed twitter in
replies(2): >>squeef+Cp >>sunrun+9u
◧◩◪◨
117. linhns+4j[view] [source] [discussion] 2025-12-17 18:02:47
>>chiste+u4
Also the level of flak is unrivaled.
◧◩◪◨
118. neom+oj[view] [source] [discussion] 2025-12-17 18:04:16
>>squeef+Fh
I've been on this internet hit shit since the 90s lil bro, s' all good.
replies(1): >>strbea+Uj
119. xxs+Aj[view] [source] 2025-12-17 18:05:04
>>uyzstv+(OP)
PSA - if you delete your cookies, HN gets it easier. Or just test it in a private window.

It did work without being logged on. The auth service appeared to be down as the log in attempt (just showing the page) failed.

replies(1): >>scotty+ul
◧◩
120. lysace+Tj[view] [source] [discussion] 2025-12-17 18:06:36
>>manbit+F
⌘-T, N, <RET>

Did it like 5 times during that 1h-ish outage. :(

◧◩◪◨⬒
121. strbea+Uj[view] [source] [discussion] 2025-12-17 18:06:37
>>neom+oj
I can stop any time I want, I just don't want!
◧◩◪
122. dpolon+ok[view] [source] [discussion] 2025-12-17 18:08:41
>>tzs+n4
Huh. Dunno why, but when it failed on Firefox I tried Chrome, and it worked. I wrote it off as a Mozilla issue, but this would better explain that I think
123. 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.

replies(24): >>shmeee+7l >>echelo+co >>Rooste+Mp >>shlomo+Rq >>altair+xt >>bicepj+Bw >>irishc+Oy >>nottor+0z >>neilv+LA >>andy_p+DC >>tsouka+KF >>showca+pH >>racl10+7I >>gianca+8I >>Imusta+DL >>maxloh+NS >>mmooss+XT >>8cvor6+EY >>xandri+W21 >>walrus+zd1 >>stmw+Sm1 >>Quantu+ht1 >>rldjbp+Zj2 >>_shadi+bk2
◧◩
124. HPsqua+Gk[view] [source] [discussion] 2025-12-17 18:10:02
>>Elfene+Q5
Sometimes I'll catch myself absentmindedly reopening the browser and checking two or three front pages, seconds after having just checked them and closed the browser.
replies(1): >>notach+Dw
◧◩◪◨
125. steve_+Yk[view] [source] [discussion] 2025-12-17 18:10:46
>>chiste+u4
> the smartest people in the world

But also, people like me. Be careful what you choose to believe on this website

◧◩
126. shmeee+7l[view] [source] [discussion] 2025-12-17 18:11:32
>>dang+zk
Looking forward to the post mortem. :)
replies(1): >>michel+Zl
◧◩
127. scotty+ul[view] [source] [discussion] 2025-12-17 18:13:47
>>xxs+Aj
Now it makes sense. I was puzzled about why it was working on the phone browser and not on my system. I'm logged into HN on my system.
128. steve_+Gl[view] [source] 2025-12-17 18:14:48
>>uyzstv+(OP)
I was fortunate enough to get to watch a bunch of kids racing and bouncing in bouncy castles in our school gym during HN's downtime.

It's not that much different from HN, come to think of it.

(ha, ha)

◧◩◪
129. michel+Zl[view] [source] [discussion] 2025-12-17 18:16:06
>>shmeee+7l
dang
replies(1): >>shmeee+6O
◧◩◪◨
130. 1shoon+3m[view] [source] [discussion] 2025-12-17 18:16:27
>>squeef+Ph
Yes.
◧◩◪◨
131. eddyg+Qm[view] [source] [discussion] 2025-12-17 18:20:22
>>laCour+ug
Thanks! I checked that page and wondered why it stayed green. I resorted to checking https://downforeveryoneorjustme.com/hacker-news
◧◩
132. echelo+co[view] [source] [discussion] 2025-12-17 18:26:29
>>dang+zk
I didn't realize you were carrying the pager too! Kudos!
replies(1): >>malwra+px
◧◩◪
133. al_bor+mo[view] [source] [discussion] 2025-12-17 18:27:17
>>Furiou+Da
It sounds like this would only work for logged in users.
134. bossyT+Po[view] [source] 2025-12-17 18:28:51
>>uyzstv+(OP)
I have never before seen this website down.
◧◩◪◨
135. bee_ri+tp[view] [source] [discussion] 2025-12-17 18:31:01
>>squeef+Fh
HN is obviously social media and it is silly to say otherwise. It is just social media that occasionally has interesting stuff. The SNR is just slightly higher.
◧◩◪◨
136. randal+vp[view] [source] [discussion] 2025-12-17 18:31:10
>>HanCli+Ge
It's a setting available on the page you get from clicking on your own username.
replies(1): >>HanCli+Qt
◧◩◪◨⬒
137. squeef+Cp[view] [source] [discussion] 2025-12-17 18:31:40
>>dwedge+Vi
> I blocked twitter for a while in my hosts file and a dozen times over those first few days I instinctively opened a new tab and typed twitter in?

youd go through that effort when you could have just stopped though.

replies(1): >>frikk+Fs
◧◩
138. direct+Ip[view] [source] [discussion] 2025-12-17 18:32:13
>>manbit+F
I'm glad I'm not the only one. If I type 'n' into any browser it autocompletes to HN.
replies(2): >>embedd+0u >>geocra+fG
◧◩
139. Rooste+Mp[view] [source] [discussion] 2025-12-17 18:32:20
>>dang+zk
No apology needed. We all needed to stop procrastinating anyways :)
◧◩◪◨
140. bee_ri+Np[view] [source] [discussion] 2025-12-17 18:32:21
>>HanCli+Ge
It is on your profile, the “noprocrast” dropdown.
◧◩
141. shlomo+Rq[view] [source] [discussion] 2025-12-17 18:38:06
>>dang+zk
Crazy that Dang literally manages HN in his sleep!

We all knew that but I haven't seen any confirmation before this.

replies(5): >>dang+vu >>qingch+7N >>easter+Ct1 >>utopce+PE1 >>sizzle+3L1
◧◩◪◨
142. andrep+ar[view] [source] [discussion] 2025-12-17 18:39:17
>>chiste+u4
Poe's Law for a parody of the self-important sv techbro
replies(1): >>the_af+SJ
◧◩
143. mustak+qr[view] [source] [discussion] 2025-12-17 18:40:17
>>Elfene+Q5
I woke up and was wondering if I’ve just woken up in hell!
◧◩◪◨⬒⬓
144. ssdspo+js[view] [source] [discussion] 2025-12-17 18:44:41
>>seizet+ng
Intelligence has many dimensions.
145. khobra+ss[view] [source] 2025-12-17 18:45:24
>>uyzstv+(OP)
Man if I had a coin every time I email the mods and this thing goes down, I'd strangely have two coins.
◧◩◪◨⬒⬓
146. frikk+Fs[view] [source] [discussion] 2025-12-17 18:46:07
>>squeef+Cp
We all admire your absolute mastery of your own habitual reflexes and mind. For the rest of us, there is a daily battle of wits, desires, weakness, and habit.

If I could snap my fingers and break toxic habits and patterns, I would have done so decades ago :)

◧◩
147. altair+xt[view] [source] [discussion] 2025-12-17 18:49:15
>>dang+zk
Decades ago I had to write a Perl script to auth to the site for proper downtime checking. Some things never change :) Good luck with the triage.
◧◩◪◨⬒
148. HanCli+Qt[view] [source] [discussion] 2025-12-17 18:50:27
>>randal+vp
Whoa. A website that cares about its users enough to _easily support limiting access to itself_?

That's so refreshing in terms of being a user-focused feature, and yet it stands in sharp contrast against today's engagement-hyperfocused climate. I never would have thought to look on a website's own settings page to limit my access to that same website.

I love it, thank you for pointing me to this!

◧◩◪
149. embedd+0u[view] [source] [discussion] 2025-12-17 18:51:20
>>direct+Ip
Save typing hundreds of letters per day, and replace about:newtab with news.ycombinator.com, now you can just do CTRL+T :)
replies(1): >>tom133+5E
◧◩◪◨⬒
150. sunrun+9u[view] [source] [discussion] 2025-12-17 18:51:42
>>dwedge+Vi
I deleted the YouTube mobile app a few months ago and I still reflexively reach for the app icon every now and then. Thanks YouTube Shorts.
◧◩◪
151. dang+vu[view] [source] [discussion] 2025-12-17 18:53:02
>>shlomo+Rq
failing to manage HN in my sleep is more like it
replies(12): >>comman+Bv >>dijit+Ev >>notach+mw >>jonny_+vH >>sailfa+uJ >>franci+PM >>zenopr+fO >>djmips+rl1 >>feczer+cr1 >>wkat42+ws1 >>nubine+zu1 >>sizzle+8L1
◧◩◪
152. embedd+Bu[view] [source] [discussion] 2025-12-17 18:53:21
>>1shoon+ma

    echo '127.0.0.1 news.ycombinator.com' | sudo tee -a /etc/hosts
Does the trick as well :) For bonus points (and so you can't workaround it with your phone), do it on your router/switch instead.

You'll still open new tabs and go to HN, but you'll be reminded quickly, and every day can be downtime day \o/ (for you, personally)

◧◩◪◨
153. comman+Bv[view] [source] [discussion] 2025-12-17 18:58:05
>>dang+vu
Do you have nightmares of failing to manage HN when you sleep too?
154. whynot+Cv[view] [source] 2025-12-17 18:58:07
>>uyzstv+(OP)
I Still found it funny that we have downdetector, downdetectordowndetector, downdetectordowndetectordowndetector,... (I lost count) but downdetector doesn't detect HN's status.
◧◩◪◨
155. dijit+Ev[view] [source] [discussion] 2025-12-17 18:58:15
>>dang+vu
We all have our moments, and I personally consider HN to be “best effort”, almost like a volunteer project. I’m not certain I’m correct: but thats the optics I have so my expectations are adjusted to that.

So don’t beat yourself up please.

When I worked for “SaaS unicorn” we typically had multiple levels of escalation, and acknowledging would have done nothing because the alarm would continue firing until fixed. Not sure what’s changed in 15 years of ops, I had assumed it would be better now- I can’t imagine silencing an alert totally by acknowledging it- if its still occurring.

I’m totally fine with how you handled it, if anything I am thankful. But that seems to be a system I would improve if I had the time.

“mute” is different than “resolve” to me, and both should exist. (Where mute is an acknowledgement of an issue as ongoing.)

replies(2): >>scottl+2F >>gianca+pI
◧◩◪◨
156. MikeTh+Yv[view] [source] [discussion] 2025-12-17 18:59:35
>>squeef+Ph
To be fair, making a change (particularly changing a habit) takes time. Having something there to remind and nudge you helps make this easier, especially when you're tired, stressed, 'just looking for a short break', etc, etc.

It's like they say: "Your demons will comfort you when no one else will. That's why it's so hard to get rid of them"

◧◩◪◨
157. notach+mw[view] [source] [discussion] 2025-12-17 19:01:18
>>dang+vu
And that is a good thing. Sleep tight!
◧◩
158. bicepj+Bw[view] [source] [discussion] 2025-12-17 19:02:02
>>dang+zk
Even after providing firebase endpoint, crawlers come to the site ?
replies(3): >>busymo+FE >>Bender+wF >>dang+F71
◧◩◪
159. notach+Dw[view] [source] [discussion] 2025-12-17 19:02:12
>>HPsqua+Gk
That's a sign of addiction and I highly recommend changing your behaviour towards those pages!
replies(1): >>chesch+dQ
◧◩◪
160. malwra+px[view] [source] [discussion] 2025-12-17 19:04:57
>>echelo+co
I feel such a sense of kinship for anyone who carries a pager, almost 7 years at my current role doing it. Super cool that dang is among our number :)
replies(3): >>geocra+8E >>idontw+OH >>wkat42+5t1
◧◩
161. irishc+Oy[view] [source] [discussion] 2025-12-17 19:10:41
>>dang+zk
> The reason I did that is that the anti-crawler protections also unfortunately hit some legit users

How does this happen?

replies(3): >>Bender+wC >>ohhnoo+oP >>pjc50+0Z
◧◩
162. nottor+0z[view] [source] [discussion] 2025-12-17 19:11:23
>>dang+zk
Can't speak for others, but I'm sure i'll be pretty fine if no one gets woken up if HN is down...

Of course, they'd better restore service after they wake up naturally, because I need my HN dose. But it's not worth losing sleep over it.

◧◩
163. nottor+fz[view] [source] [discussion] 2025-12-17 19:12:14
>>manbit+F
What? You mean you ... close the HN tab?
◧◩
164. neilv+LA[view] [source] [discussion] 2025-12-17 19:19:28
>>dang+zk
Maybe it would be fine if ops alerts were silenced during normal US sleeping hours?

HN is important, but unlikely much harm could be done before morning.

(Source: Lost a lot of sleep at one place, enough to realize that sleep interruption and deficit has significant costs.)

◧◩◪
165. Bender+wC[view] [source] [discussion] 2025-12-17 19:27:43
>>irishc+Oy
How does this happen?

Not the person you are asking. Bot operators have an incentive to make crawlers look as much like a human as possible so they do not get blocked. Some of them fail miserably and some nearly succeed. That makes it trivial to accidentally block a real person. I am personally fine with that given I do not pay for this site and have no SLA or contract with it.

replies(1): >>arccy+tL
◧◩
166. andy_p+DC[view] [source] [discussion] 2025-12-17 19:28:29
>>dang+zk
I’d love to know more about what running a site like HN involves, would be great to get a write up of what it’s like running something like this at this scale (and what kind of traffic you guys get)!
replies(1): >>alwa+LF
167. dustfi+8D[view] [source] 2025-12-17 19:30:36
>>uyzstv+(OP)
It would be a nice feature if hackernews had a simple news.ycombinator.com/status page that I could trust. I don't like loading those some-sketchy-domain/status-right-now sites.
replies(1): >>mmooss+4M
◧◩◪◨
168. tom133+5E[view] [source] [discussion] 2025-12-17 19:35:17
>>embedd+0u
at that moment my productivity would drop to zero
replies(1): >>Imusta+eM
◧◩◪◨
169. geocra+8E[view] [source] [discussion] 2025-12-17 19:35:30
>>malwra+px
Yep, have been on constant "pager duty" for 2+ years, although I have more help now and I get paged 1-3 times a week instead of per night. Still, carry my lappy everywhere I go. Bought an ARM Windows laptop to get that 20hr battery life so I could worry less during my travels. You know, fancy things like going get food or going grocery shopping.
replies(1): >>malwra+p11
◧◩◪
170. busymo+FE[view] [source] [discussion] 2025-12-17 19:38:06
>>bicepj+Bw
Unfortunately, the firebase API is very bad as they even acknowledge that in their github page.
◧◩◪◨⬒
171. scottl+2F[view] [source] [discussion] 2025-12-17 19:39:44
>>dijit+Ev
This. If it were a business-critical money fountain, I'd expect follow-the-sun SRE coverage. I don't think it is, so I can probably accept drinking my morning coffee without scrolling HN once in a while. There's only so much one can beat oneself up about a slow/incorrect response when the on-call is handled by what, just one person? maybe two people in the same time zone?

(Might be wise though to have PagerDuty configured to re-alert if the outage persists.)

◧◩
172. RJIb8R+fF[view] [source] [discussion] 2025-12-17 19:40:25
>>Elfene+Q5
HN is how I discover whether other sites are down or not, so it serves a critical function, so of course I check it frequently.

/s

◧◩◪
173. Bender+wF[view] [source] [discussion] 2025-12-17 19:42:07
>>bicepj+Bw
Most crawlers have no concept of what that is. They will follow links to this site and then follow links out of this site even after being told not to [1]. The majority of crawlers follow zero rules, RFC's, etc... The few platforms that do follow standards and rules are akin to a law abiding citizen in Mos Eisley.

[1] - rel="nofollow"

◧◩
174. tsouka+KF[view] [source] [discussion] 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.
replies(1): >>dang+nb1
◧◩◪
175. alwa+LF[view] [source] [discussion] 2025-12-17 19:43:31
>>andy_p+DC
I can’t put my finger on anything within the last decade, but I seem to recall it running in something close to its current form on a single core on a single server for a long time:

>>5229522

Re: traffic, dang said (2022):

>>33454140

I took it as a good reminder that the hard part is the human part: that high-overhead features and UI fripperies are nice but not necessary (or sufficient) to keep a community healthy and vibrant over the decades.

(And on the subject of the human side, if you didn’t catch Anna Wiener’s 2019 profile, it’s here:

https://www.newyorker.com/news/letter-from-silicon-valley/th... )

replies(2): >>tempes+WK >>ilamon+pL
◧◩◪
176. geocra+fG[view] [source] [discussion] 2025-12-17 19:45:55
>>direct+Ip
I had the same thing for Slashdot.org for many, many years. Both the reflex and the browser autocomplete. I still miss the old /. It was like HN + Hackaday + Usenet.
replies(1): >>neom+rq1
◧◩
177. showca+pH[view] [source] [discussion] 2025-12-17 19:51:28
>>dang+zk
Short lived and driven by good intentions– all's good. Thanks again for keeping this thing going!
◧◩◪◨
178. jonny_+vH[view] [source] [discussion] 2025-12-17 19:51:33
>>dang+vu
Your sleep is more important than our work distraction.
replies(1): >>seemaz+Ir1
◧◩◪◨
179. idontw+OH[view] [source] [discussion] 2025-12-17 19:53:07
>>malwra+px
Do you carry a literal pager? We use the PagerDuty app.
replies(3): >>geocra+5L >>kunwon+oN >>malwra+EZ
◧◩
180. racl10+7I[view] [source] [discussion] 2025-12-17 19:54:51
>>dang+zk
dang!
◧◩
181. gianca+8I[view] [source] [discussion] 2025-12-17 19:54:54
>>dang+zk
The transparency is deeply appreciated by me and others. We don't pay to keep HN on, so we cannot complain. Thank you and the rest of the team for all you do to give us a corner of the internet that is quite 'different' from the rest of the wild west that is the web.
◧◩◪◨⬒
182. gianca+pI[view] [source] [discussion] 2025-12-17 19:55:45
>>dijit+Ev
Yeah we don't exactly pay to be on HN, not much to complain about. I appreciate everyone who works on HN.
replies(1): >>jacque+Vw1
◧◩◪
183. ayewo+TI[view] [source] [discussion] 2025-12-17 19:58:31
>>Aachen+Wc
Would love to see it when you do get round to posting it :)
◧◩◪◨⬒⬓
184. the_af+6J[view] [source] [discussion] 2025-12-17 19:59:15
>>seizet+ng
> It's entirely possible that this is the smartest place on the internet, but also often dumb. In fact, it seems likely. More of an indictment of the rest of the places on the internet.

Almost every (non-troll) online community that is relatively peaceful and has some semblance of moderation to remove flamewars thinks of itself as "the best community". Usually as compared to reddit, though if it's on reddit they will compare themselves to some other (hated) sub.

It's a fact of the internet. Every online community thinks of itself as the smartest, more thoughtful, more civilized. HN is no exception.

It goes without saying HN is not the smartest or more thoughtful online community. It's just... ok. Not the worst, not the best. Certainly NOT the place with the smartest people, though some smart people frequent it. As a regular, you can soon figure out HN's unspoken rules, blindspots, and areas where the group opinion is more likely to be accurate.

replies(1): >>jrowen+oU
◧◩◪◨
185. sailfa+uJ[view] [source] [discussion] 2025-12-17 20:00:50
>>dang+vu
Yeah, I mean how dare you?! I pay good money for high uptime SLAs! :)
◧◩◪◨⬒
186. the_af+SJ[view] [source] [discussion] 2025-12-17 20:02:46
>>andrep+ar
It's a testament to Poe's Law that I genuinely cannot tell if the OP was being funny or not.
replies(1): >>mrguyo+TX
◧◩◪◨
187. tempes+WK[view] [source] [discussion] 2025-12-17 20:07:50
>>alwa+LF
The other reality is that as much as this industry is up its ass about scalability you can run a very very busy site on a single machine now a days.

A lot of people out here designing their blogs like its 1989.

replies(1): >>andy_p+zo5
◧◩◪◨⬒
188. geocra+5L[view] [source] [discussion] 2025-12-17 20:08:14
>>idontw+OH
My organization is, for now, using OpsGenie.

My pager noise: https://www.soundjay.com/transportation/sounds/train-crossin...

That will not only wake the dead, it'll wake me no matter how asleep I am.

replies(2): >>malwra+801 >>darkwa+B91
◧◩◪◨
189. ilamon+pL[view] [source] [discussion] 2025-12-17 20:09:34
>>alwa+LF
From dang's 2022 comment about traffic:

The most interesting number is the 1300 submissions because that hasn't grown since 2011 - it just fluctuates. Everything else has been growing more or less linearly for a long time, which is how we like it.

I find that surprising, as 2011-2022 covers an exponential rise in SEO spam and "growth hackers" attempting to drive traffic and links.

Or was 1,300 the number of non-flagged submissions?

replies(1): >>dang+pf5
◧◩◪◨
190. arccy+tL[view] [source] [discussion] 2025-12-17 20:09:58
>>Bender+wC
some humans also try their best to make themselves look like bots...
replies(3): >>Imusta+KL >>slater+GV >>ZuoCen+Lm1
◧◩
191. Imusta+DL[view] [source] [discussion] 2025-12-17 20:11:01
>>dang+zk
I was personally worried if there was some major outage of the whole world or something the first time hackernews didnt work because I didnt expect hackernews to go down but rather, something even more catastrophic than aws going down must happen (because we see major cloud outage posts)

https://downforeveryoneorjustme.com/hacker-news

This website had many instances of reports, the last I saw were 52 reports in only a short frame of time, the maximum reports on this are 118 it seems.

> 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.

Its okay I suppose, have you figured out who is crawling hackernews so much tho, was it a ddos attack or an AI company trying to get data, doesn't hackernews support an api and I am sure that there are datasets for it too so Its interesting why they might crawl but we all know the reasons why as they have been discussed here.

◧◩◪◨⬒
192. Imusta+KL[view] [source] [discussion] 2025-12-17 20:11:41
>>arccy+tL
beep boop.
◧◩
193. Imusta+WL[view] [source] [discussion] 2025-12-17 20:13:04
>>Elfene+Q5
Yeah, I had assumed something very major must have happened for HN to go down, lmao and I even asked in some linux discord server regarding it asking if there is a major outage as hackernews is down
◧◩
194. mmooss+4M[view] [source] [discussion] 2025-12-17 20:13:54
>>dustfi+8D
> news.ycombinator.com/status page

That's not so useful when news.ycombinator.com is having problems.

replies(1): >>dustfi+uV
◧◩◪◨⬒
195. Imusta+eM[view] [source] [discussion] 2025-12-17 20:14:41
>>tom133+5E
mine already has and I dont even have hackernews as my new tab :)

On all fairness though, mine is same for the original comment where just pressing n autocompletes it to https://news.ycombinator.com/

◧◩◪◨
196. franci+PM[view] [source] [discussion] 2025-12-17 20:17:35
>>dang+vu
No worries, please take care of your sleep and thanks for all your hard work
◧◩◪
197. qingch+7N[view] [source] [discussion] 2025-12-17 20:18:54
>>shlomo+Rq
I was today years old when I found out Dan sleeps.
replies(1): >>gaudys+G31
◧◩◪◨⬒
198. kunwon+oN[view] [source] [discussion] 2025-12-17 20:19:59
>>idontw+OH
It may interest you to know that pagers are still a thing, Motorola still makes them, and I know that one major use case is volunteer fire departments

I used to work on Motorola Minitor 5 pagers. Looks like they recently released their newest model, the Minitor 7

I wonder if pagers are still used in hospitals? I imagine so

replies(4): >>sharps+FQ >>sgeren+uR >>Errone+e91 >>ZuoCen+Vm1
◧◩◪◨
199. shmeee+6O[view] [source] [discussion] 2025-12-17 20:23:12
>>michel+Zl
In my defense, I was commenting at 0 min, since then he made several updates explaining the situation.
replies(1): >>dang+U71
◧◩◪◨
200. zenopr+fO[view] [source] [discussion] 2025-12-17 20:24:00
>>dang+vu
Which is fine! I don't mind if it's down for a few hours. It reminds me that it's just a place to stop by for a bit before moving on. Like a digital coffee shop that sometimes has a leaky pipe and isn't open right at 7am.

I hope it doesn't change (much).

◧◩
201. alexfo+gO[view] [source] [discussion] 2025-12-17 20:24:00
>>al_bor+74
https://xcancel.com/HNStatus only uses chronological ordering (after any pinned tweets) and that has the last message 12 Dec 2023.

(Basically whenever you see an x.com link just change it to xcancel.com and avoid the nonsense.)

202. codykl+3P[view] [source] 2025-12-17 20:30:07
>>uyzstv+(OP)
I thought HN traffic got blocked on my work's network for a second, phew! My lunch breaks would've gotten a lot more dull.
◧◩◪
203. ohhnoo+oP[view] [source] [discussion] 2025-12-17 20:31:47
>>irishc+Oy
Last week if you are using a VPN + a browser that limits fingerprinting, you were likely to see error messages accessing HN.
◧◩◪◨
204. chesch+dQ[view] [source] [discussion] 2025-12-17 20:36:34
>>notach+Dw
I feel like I need to avoid channelling Bob Saget from Half Baked when I say that is not addiction. That's a habit.
replies(2): >>cbrack+x41 >>notach+RR2
◧◩◪◨⬒⬓
205. sharps+FQ[view] [source] [discussion] 2025-12-17 20:38:40
>>kunwon+oN
The AUBMC hospital is definitely using them as well as the paramilitary in that country, at least until recently.
◧◩◪
206. ycombi+mR[view] [source] [discussion] 2025-12-17 20:41:08
>>tzs+n4
I couldn't access it in private or regular.
◧◩◪◨⬒⬓
207. sgeren+uR[view] [source] [discussion] 2025-12-17 20:42:08
>>kunwon+oN
Doctors on call at hospitals also routinely still use pagers. There was a planet money episode on it a couple years ago: https://www.npr.org/2023/12/08/1197955913/doctors-pagers-bee...
replies(1): >>xeonmc+bh1
◧◩
208. maxloh+NS[view] [source] [discussion] 2025-12-17 20:49:53
>>dang+zk
Frankly, I don't understand why someone would even try to crawl Hacker News.

There is an official dump which doesn't even require parsing HTML at all: https://console.cloud.google.com/marketplace/details/y-combi...

replies(1): >>dang+E81
◧◩
209. sammy2+QT[view] [source] [discussion] 2025-12-17 20:55:23
>>laCour+Sf
You should add a graph of visitors per-minute for the status page for the past 24 hours or so. Would really help for situations like this
◧◩
210. mmooss+XT[view] [source] [discussion] 2025-12-17 20:56:18
>>dang+zk
In a situation like this one, good crisis leadership is essential. dang, HN will help you with tips from vast collected experience (please chip in):

1. Blame: The first thing to do is to point the finger. That doesn't mean analysing the technical issue, which can delay this step and limit your options, but figuring out who is politically easiest to blame. Often, that's the new guy, but outside contractors and vendors without good connections are also a common solution. Even if you are technically responsible for hiring them, you can always push them under the bus with a little skill. This small sacrifice helps unify, focus, and motivate the rest of the team.

2. Emotion: Inject your emotion into the situation and make that the implicit, but indisputable priority. Particularly, outrage and anger - This is completely _____. These people are utterly _____ (I'd use all caps, but that's not allowed on HN). Make sure everyone's attention is over their shoulder, on your emotion, and infect the team with it. Threats are an effective tool here - this is a crisis, and anyone who is calm is not emotionally engaged. Otherwise, they won't care enough about this problem - without you driving them, they probably wouldn't care much at all. Anyway, you don't have time for niceties like empathy or even basic respect.

3. Speed: Respnsiveness to stakeholders is very important. People need answers now. Give them answers they want to hear, outcomes they will be comfortable with. Don't worry if different groups hear different things. Your team will find a way to make it all work - that's their job.

4. Communication: Good communication is essential. Make sure you clearly tell your team what they should be doing; repeat it several times to prevent misunderstanding. Especially people with experience can have minds of their own; keep them on track. The situation is a crisis so you can't take any risks; stay on top of them and everything they do, and give input if you're not certain they are doing exactly what you would be doing.

5. Victimhood: Find a way to turn the tables: Make it about you, and how you're the victim here, and feed the fire with more outrage. With this and outrage, nobody will undermine the team by challenging your ideas or authority, which is the most essential component of a successful outcome. Remember, without you this all falls apart.

Have I missed anything?

replies(1): >>yearol+pz1
◧◩◪◨⬒⬓⬔
211. jrowen+oU[view] [source] [discussion] 2025-12-17 20:58:46
>>the_af+6J
> It goes without saying HN is not the smartest or more thoughtful online community.

How does that go without saying? Name some others then, compare and contrast. As-is your argument is just posturing.

replies(1): >>the_af+xZ
◧◩◪
212. dustfi+uV[view] [source] [discussion] 2025-12-17 21:04:09
>>mmooss+4M
True. how about https://ycombinator-status.com or https://status.ycombinator.com. They can drop that link on their official ycombinator.com site just so it is easy to tell that it is legit when they are not down. They can maintain the status for all of their official sites there. Well, with the exception of ycombinator-status.com of course. I guess they can post that status on some-sketchy-domain/status-right-now - LOL!

Maybe ycombinator does have an official status page somewhere, but it is not easy to find if that is the case.

◧◩◪◨⬒
213. slater+GV[view] [source] [discussion] 2025-12-17 21:05:18
>>arccy+tL
You're absolutely right!
214. compli+JV[view] [source] 2025-12-17 21:05:38
>>uyzstv+(OP)
[flagged]
◧◩◪◨
215. ptsd_d+UV[view] [source] [discussion] 2025-12-17 21:06:50
>>squeef+Fh
I guese developed this addiction on Facebook and now that I don’t use it, I come for methadon shot to HN
◧◩◪◨⬒⬓⬔
216. seizet+QW[view] [source] [discussion] 2025-12-17 21:12:29
>>squeef+Ji
1. niceness and genius are orthogonal

2. your characterization of the article sounds uncharitable

3. my point isn't exactly that this is necessarily the smartest place

replies(1): >>squeef+Rn2
◧◩◪◨⬒⬓
217. mrguyo+TX[view] [source] [discussion] 2025-12-17 21:18:51
>>the_af+SJ
There's a reason why HN of all places has such a terrible record of handling actual sarcasm and telling it apart from genuine belief and that reason is NOT that "HN is really smart" lol
replies(1): >>the_af+001
◧◩
218. 8cvor6+EY[view] [source] [discussion] 2025-12-17 21:22:56
>>dang+zk
> anti-crawler protections

Sometimes I could not open the comment section, receiving a blank page with "... We're sorry" or something along these lines when opening from new private window. It works when opening normally.

Logging in on the private window seems to resolve the issue. Can you take a look on this if possible?

replies(1): >>dang+781
◧◩◪
219. pjc50+0Z[view] [source] [discussion] 2025-12-17 21:24:38
>>irishc+Oy
Every filter process has false positives and false negatives, especially when crawlers are trying to fake their status.
◧◩◪◨⬒⬓⬔⧯
220. the_af+xZ[view] [source] [discussion] 2025-12-17 21:26:45
>>jrowen+oU
> Name some others then, compare and contrast.

No need, because whether an online community is more thoughtful or smarter than another is very subjective. Almost by definition, HN is not it. Extraordinary claims require extraordinary evidence, and all that. Of course, by internet law, HN (or a subset of its members) considers itself to be the smartest, more thoughtful online community.

There are communities I like better, which are smarter and more thoughtful, but I've no desire to argue with you.

> As-is your argument is just posturing

Nah. Hard pass. Nice try though!

replies(1): >>jrowen+g62
◧◩◪◨⬒
221. malwra+EZ[view] [source] [discussion] 2025-12-17 21:27:14
>>idontw+OH
Oh no, I just always hear it termed that way and it captures the “feeling” for me since it feels like a dedicated device. I just just carry a work phone w/ PagerDuty during my shift.
◧◩◪◨⬒⬓⬔
222. the_af+001[view] [source] [discussion] 2025-12-17 21:28:45
>>mrguyo+TX
Agreed! I think HN is average, and its userbase think themselves smarter than they really are.

... but I still cannot tell if the original commenter was sarcastic or not! ;)

◧◩◪◨⬒⬓
223. malwra+801[view] [source] [discussion] 2025-12-17 21:29:28
>>geocra+5L
Haha I made the mistake of using the default iPhone ringtone, now when strangers get called in public my heart rate spikes. Too scared to change it.
◧◩◪◨⬒
224. malwra+p11[view] [source] [discussion] 2025-12-17 21:36:07
>>geocra+8E
Rough shift, my worst was every other week and my boss prior to hiring me was 24/7 just like you. I just carry a backpack with a few batteries + my work laptop, fortunately only a few really bad stories but hooooo boy me and that backpack have seen some fun times.
◧◩
225. xandri+W21[view] [source] [discussion] 2025-12-17 21:44:25
>>dang+zk
Hey dang, don't worry. It's just a site for reading articles and reacting to them.

Enjoy your deserved sleep and if for a couple of hours it's down, so be it.

Thanks for your continued service!

replies(1): >>powvan+o61
◧◩◪◨
226. gaudys+G31[view] [source] [discussion] 2025-12-17 21:47:02
>>qingch+7N
I was today years old when I found out that dang's first name is Dan
replies(1): >>anonym+d91
◧◩◪◨⬒
227. cbrack+x41[view] [source] [discussion] 2025-12-17 21:50:48
>>chesch+dQ
There is a noprocrast feature in your settings to specify how long you can stay on for a single session and the frequency at which you can view HN. Super helpful!
◧◩
228. cbrack+C41[view] [source] [discussion] 2025-12-17 21:51:13
>>manbit+F
There is a noprocrast feature in your settings to specify how long you can stay on for a single session and the frequency at which you can view HN. Super helpful!
◧◩◪
229. powvan+o61[view] [source] [discussion] 2025-12-17 22:00:21
>>xandri+W21
100%

Though I will say, HN is a pretty great source of information about major outages like the recent AWS and Cloudflare issues. I had a moment this morning where I thought, oh, is there a larger issue and then, oh, HN is down, huh, the next option is so far down my list that it's going to take me a moment to think of it.

I hope that serves as a testament to how great this site and the community is. Thanks for all your hard work keeping it that way!

replies(1): >>derrid+zk1
◧◩
230. dang+171[view] [source] [discussion] 2025-12-17 22:04:14
>>al_bor+74
We post there when we know we're down and it may take more than a few minutes. But in this case we didn't know! >>46303196
◧◩◪
231. dang+F71[view] [source] [discussion] 2025-12-17 22:08:13
>>bicepj+Bw
Oh my god. It's the crawlopalypse.
replies(1): >>collin+eP3
◧◩◪◨⬒
232. dang+U71[view] [source] [discussion] 2025-12-17 22:08:55
>>shmeee+6O
Yes sorry! Normally I put in "[editing - bear with me...]" or some such.
replies(1): >>michel+ks1
◧◩◪
233. dang+781[view] [source] [discussion] 2025-12-17 22:10:07
>>8cvor6+EY
Best to email your IP address to hn@ycombinator.com so we can see if it's blocked.
◧◩◪◨
234. krapp+981[view] [source] [discussion] 2025-12-17 22:10:36
>>chiste+u4
Any professional forum or technical subreddit with good moderation and gatekeeping blows Hacker News out of the water any day of the week.
◧◩◪
235. dang+E81[view] [source] [discussion] 2025-12-17 22:14:50
>>maxloh+NS
These are not, er, experienced crawlers.

https://www.youtube.com/watch?v=Sbpl3ywNlpA#t=56s

◧◩◪
236. wiredp+191[view] [source] [discussion] 2025-12-17 22:16:21
>>dylan6+y8
This problem is really bad at my work.

We commonly run into finance issues about half way through the year. We get to the point where 10x HDMI cables get declined from Finance and we get reprimanded for not tracking where each HDMI or Ethernet Cable go. Near to the end of the year, the budget refreshes and finance (without consultation to us) ends up buying a bunch of random stuff.

"Guys, we brought 11 iPad Minis that need to be setup"

Oh so we can also get the HDMI cables now?

"No sorry, we just spent all the remaining money, have you audited the cables recently?"

◧◩◪◨⬒
237. anonym+d91[view] [source] [discussion] 2025-12-17 22:16:56
>>gaudys+G31
You'll never guess what letter dang's last name starts with.
replies(1): >>smolde+Hb1
◧◩◪◨⬒⬓
238. Errone+e91[view] [source] [discussion] 2025-12-17 22:17:02
>>kunwon+oN
There's a company in England called "Cascode" who make firefighter alerters. These are really basic "beeper" pagers, which you can program to have a bunch of different tones and LED patterns based on the RIC and Subcode.

I look after several thousand of these across several hundred paging sites.

They're relatively inexpensive (70 quid or so in quantity) and they last about six weeks on a commonly-available AA battery. The batteries go flat enough to trigger the "low battery" beep at about 3am, for some reason. I don't know why.

There's no messaging involved, although the encoders are capable of sending a text string. The message is "get up and get down to the fire station right now", which generally needs no further explanation. POCSAG is unencrypted, so there would be privacy concerns with sending actual incident information in the clear with it.

While we're on the subject of old tech, until BT finally cut the last of them off, we use dialup modems to control the encoders (not dialup internet, just a hundreds-of-miles serial cable) as a backup, and dot-matrix printers to print out a hardcopy message for the crews to pick up.

All very low-tech. All very fixable. All stays working if you don't mess with it.

https://cascode.co.uk/products/2ar2-and-2ar3/

replies(1): >>wkat42+jt1
◧◩
239. Rendel+o91[view] [source] [discussion] 2025-12-17 22:17:51
>>Elfene+Q5
Funny, I don't seem to need an outage to get stuck in a HN loop...
◧◩
240. Errone+y91[view] [source] [discussion] 2025-12-17 22:18:45
>>Elfene+Q5
Not just me then?

"Shit, HN is down! Hm, I wonder if there's anything about it on HN?"

until stack overflow occurs.

◧◩◪◨⬒⬓
241. darkwa+B91[view] [source] [discussion] 2025-12-17 22:18:56
>>geocra+5L
The "for now" is very important because it will be sunset in 1 year and something. I can recommend you Incident.io or Rootly as alternatives.
◧◩
242. Errone+H91[view] [source] [discussion] 2025-12-17 22:19:19
>>manbit+F
Do you log into things and reflexively type "ls", too?
◧◩◪
243. dang+nb1[view] [source] [discussion] 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.

replies(1): >>tsouka+y92
◧◩◪◨⬒⬓
244. smolde+Hb1[view] [source] [discussion] 2025-12-17 22:31:19
>>anonym+d91
A as in Ang, clearly.
replies(1): >>qingch+Rc1
◧◩◪◨⬒⬓⬔
245. qingch+Rc1[view] [source] [discussion] 2025-12-17 22:38:03
>>smolde+Hb1
No, he's Asian. The n is doing double-duty. His last name is Ng :p
replies(1): >>fragme+wD1
◧◩
246. walrus+zd1[view] [source] [discussion] 2025-12-17 22:41:41
>>dang+zk
Just out of curiosity, if HN is still running on one physical system, what does a daily or weekly traffic chart look like for the switch port facing it?
◧◩◪◨⬒⬓⬔
247. xeonmc+bh1[view] [source] [discussion] 2025-12-17 23:05:22
>>sgeren+uR
Do doctors in the Middle East also carry pagers?
◧◩◪◨
248. derrid+zk1[view] [source] [discussion] 2025-12-17 23:27:19
>>powvan+o61
> huh, the next option is so far down my list that it's going to take me a moment to think of it.

Option 4: take your grab bag with the tcp over IP shortwave radio, sextant and head for pre-cached month supply of food in the hills.

◧◩◪◨
249. djmips+rl1[view] [source] [discussion] 2025-12-17 23:34:08
>>dang+vu
I appreciate what you do. Hope you got some rest when it was all over.
◧◩◪◨⬒
250. ZuoCen+Lm1[view] [source] [discussion] 2025-12-17 23:42:42
>>arccy+tL
lol
◧◩
251. stmw+Sm1[view] [source] [discussion] 2025-12-17 23:43:56
>>dang+zk
dang - just to say, we've all done it...
◧◩◪◨⬒⬓
252. ZuoCen+Vm1[view] [source] [discussion] 2025-12-17 23:44:09
>>kunwon+oN
Now, whenever I see a pager, I think of explosions. Haha.
◧◩◪◨
253. ZuoCen+Gn1[view] [source] [discussion] 2025-12-17 23:50:39
>>Purple+E7
Perhaps this is the role of HN - at least it still allows us to reflect.
◧◩◪
254. ZuoCen+Vn1[view] [source] [discussion] 2025-12-17 23:52:18
>>ChrisM+H7
Admirable~
◧◩◪◨
255. neom+rq1[view] [source] [discussion] 2025-12-18 00:11:53
>>geocra+fG
digg too, till they ruined it...still can't believe they ruined digg.
◧◩◪◨
256. feczer+cr1[view] [source] [discussion] 2025-12-18 00:18:34
>>dang+vu
You deserve a lot of rest!
◧◩◪◨⬒
257. seemaz+Ir1[view] [source] [discussion] 2025-12-18 00:23:04
>>jonny_+vH
I was curiously productive this morning..
replies(2): >>koakum+Sy1 >>arnavp+aU1
◧◩◪◨⬒⬓
258. michel+ks1[view] [source] [discussion] 2025-12-18 00:29:14
>>dang+U71
I was just trolling, thanks for ur work
◧◩◪◨
259. wkat42+ws1[view] [source] [discussion] 2025-12-18 00:30:47
>>dang+vu
You're still a miracle worker. Single-handedly managing a well-known fully user-contributed site not just technically but moderation in contentious times like these and still keeping it working well and encouraging a positive user community can't be an easy task.
replies(1): >>dang+4W1
◧◩◪◨
260. wkat42+5t1[view] [source] [discussion] 2025-12-18 00:35:47
>>malwra+px
I wish I could still buy a pager where I live :'(
◧◩
261. Quantu+ht1[view] [source] [discussion] 2025-12-18 00:37:12
>>dang+zk
> the anti-crawler protections also unfortunately hit some legit users, and we don't want to block legit users

Was the blocking returning “Sorry.” instead of any page content? A couple of days ago there was a few hours where when I’d go to HN I could load the main page as a non-logged in user. But if I tried to log in I would get “Sorry.” instead. I also got the sorry message if I tried to click on user profiles of other people and a few other pages.

I am assuming that the reason I could see the front page itself and discussions on posts on the front page is that they were in a shared cache for non-logged in users, but that when I clicked on some pages like some random user pages those were not in cache and hit the origin server and it blocked those with “Sorry.” like it did for log-in attempts.

I also tried to go to the unblock IP page, but that one also returned “Sorry.”

For a while I was scratching my head wondering if I had gotten some malware on one of my computers that was aggressively making requests to HN, and that I had become IP banned because of that. Since I think my actual request rate from browsing and commenting should be pretty average. I read HN a lot, but not that much :p

Later in the day, or the next day, things were back to normal and I could log in again. Presumably after those anti-crawler protections had been relaxed again.

replies(1): >>dang+6i5
◧◩◪◨⬒⬓⬔
262. wkat42+jt1[view] [source] [discussion] 2025-12-18 00:37:42
>>Errone+e91
Encryption is easily doable even with one way pagers. With one way you will lose the perfect forward secrecy option but that's usually ok.
replies(1): >>Errone+vg2
◧◩◪
263. easter+Ct1[view] [source] [discussion] 2025-12-18 00:40:25
>>shlomo+Rq
I like hacker news but I don't think this site is worth getting paged over lol
replies(1): >>archon+9W1
◧◩◪◨
264. nubine+zu1[view] [source] [discussion] 2025-12-18 00:48:20
>>dang+vu
I was starting to think you never slept, I remember that one time I emailed you at 1am. :)
265. Aperoc+pw1[view] [source] 2025-12-18 01:03:10
>>uyzstv+(OP)
During that time I couldn't load HN web page, but my HN CLI tool could connect to HN: https://github.com/Aperocky/hnterminal, but only read.
◧◩◪◨⬒⬓
266. jacque+Vw1[view] [source] [discussion] 2025-12-18 01:07:25
>>gianca+pI
We pay with content and with the fact that we attract the talent that eventually ends up powering ycombinator investment rounds.
replies(2): >>phanta+0B1 >>spacec+PG2
◧◩◪◨⬒⬓
267. koakum+Sy1[view] [source] [discussion] 2025-12-18 01:28:19
>>seemaz+Ir1
I took a shower for the first time in one week
replies(2): >>fouc+TN1 >>bigbup+D32
◧◩◪
268. yearol+pz1[view] [source] [discussion] 2025-12-18 01:34:44
>>mmooss+XT
Engagement: make sure that every member of the team is either on the incident bridge or has dropped what they are doing to watch you diagnose the problem. The more eyes on the problem, the more awareness of the pain will be absorbed by all. If members need to leave to get food or put children to bed, tell them to order delivery and to ask their spouse to do their job. Demonstrate human touch by allowing them to turn off camera while they are eating.

Comprehensiveness: propose extreme, sweeping solutions, such as a lights-out restart of all services, shutting down all incoming requests, and restoring everything to yesterday's backup. This demonstrates that you are ready to address the problem in a maximally comprehensive way. If someone suggests a config change rollback, or a roll-forward patch, ask them why are gambling company time with localized changes, and ask them why are they willing to gamble company time on technical analysis?

Root Cause Analysis Meeting: spend the entire meeting time rehashing the events, pointing fingers and assigning blame. Be sure to mention how the incident could've been over sooner if you just restarted and rolled back every single thing. Be sure to demonstrate out-of-the-box thinking by discussing unrealistic grandiose solutions. When the time is up, run the meeting over by 30 minutes and force all to stay while realistic solution ideas are finally discussed in overtime. This makes it clear to the team that nothing is more important than this incident's RCA--their time surely is not. If someone asks to tap out to pick their kids up after school, remind them that they are making enough money to call them an Uber.

Alerting: be sure to identify anything remotely resembling leading indicators, and add Critical-level wake-you-up alerts with sensitive thresholds for those indicator. Database exceeding 50% CPU? Critical! Filesystem queue length exceeding 5? Critical! Heap usage over 50%? Critical! 100 errors in one minute on a 100000 requests per minute service? Critical! Single log line indicating DNS resolution failure anywhere in the system? Critical! (What if AWS's DNS is down again?) Service requests rate 10% higher than typical peak? Critical! If anyone objects to such critical alerts, ask them why do they want to be responsible for not preventing the next incident?

◧◩◪◨⬒⬓⬔
269. phanta+0B1[view] [source] [discussion] 2025-12-18 01:50:42
>>jacque+Vw1
It’s ad-supported. Any post with comments disabled is definitely an ad. Probably a lot of the others are, too.
replies(2): >>myster+kL1 >>abusta+yU1
◧◩◪◨⬒⬓⬔⧯
270. fragme+wD1[view] [source] [discussion] 2025-12-18 02:14:19
>>qingch+Rc1
That's exactly what a French person with the last name of Les would say!
◧◩◪
271. utopce+PE1[view] [source] [discussion] 2025-12-18 02:28:07
>>shlomo+Rq
By demonstration he didn't.
◧◩◪
272. sizzle+3L1[view] [source] [discussion] 2025-12-18 03:38:22
>>shlomo+Rq
What if Dang made an AI agent of himself for when he sleeps?
◧◩◪◨
273. sizzle+8L1[view] [source] [discussion] 2025-12-18 03:39:18
>>dang+vu
Time to train an AI agent on your moderation activity and get some well deserved sleep!
replies(1): >>dang+TV1
◧◩◪◨⬒⬓⬔⧯
274. myster+kL1[view] [source] [discussion] 2025-12-18 03:41:00
>>phanta+0B1
I assumed the main purpose was to show off the ycombinator batches when they launch.
◧◩◪◨⬒⬓⬔
275. fouc+TN1[view] [source] [discussion] 2025-12-18 04:18:59
>>koakum+Sy1
looks like a redditor snuck into HN
◧◩
276. yigith+lQ1[view] [source] [discussion] 2025-12-18 04:55:54
>>manbit+F
I stopped using google.com for Internet access check, I now use HN.
◧◩◪◨⬒⬓
277. arnavp+aU1[view] [source] [discussion] 2025-12-18 05:41:20
>>seemaz+Ir1
came back just in time for me to spend the first hour of my work
◧◩◪◨⬒⬓⬔⧯
278. abusta+yU1[view] [source] [discussion] 2025-12-18 05:45:04
>>phanta+0B1
Your comment makes me realize that I consume HN differently than many others, because I've never seen a post with comments disabled and I've been around here for at least ten years. It's not that I don't think they don't exist — they obviously do because you're mentioning them. I've just never encountered one, primarily because I don't casually browse HN, ever. I subscribe to a pushbullet channel that notifies me when a post hits 500 up votes. That's it. The list of submissions on the home page (even on reddit) is just overwhelming to me so I use the pushbullet channel as a sort of community curated "best of" or "trending" signal.

Not to say that I don't procrastinate or waste time doing other nonsense. I can definitely spend a lot of time reading HN comments, as I'm doing right now.

Anyway,anyone who finds themselves with a problem with HN should try that out :)

replies(1): >>phanta+2C2
◧◩◪◨⬒
279. dang+TV1[view] [source] [discussion] 2025-12-18 05:59:26
>>sizzle+8L1
We're working on it! well, some of it.

I'm pretty happy with how it's developing—the trendline is promising—but not ready to rely on it in prod yet.

◧◩◪◨⬒
280. dang+4W1[view] [source] [discussion] 2025-12-18 06:00:48
>>wkat42+ws1
Thanks, I'll take it! except for the single-handedly part - gotta share the love with https://news.ycombinator.com/posts?id=tomhow.
◧◩◪◨
281. archon+9W1[view] [source] [discussion] 2025-12-18 06:01:17
>>easter+Ct1
You might be underestimating HN's popularity.
replies(1): >>lockni+oY1
◧◩◪◨⬒
282. lockni+oY1[view] [source] [discussion] 2025-12-18 06:29:44
>>archon+9W1
> You might be underestimating HN's popularity.

I think you're confusing popularity with criticality. I'm sure everyone in here can withstand a few hours without browsing the page.

replies(1): >>bayind+T72
◧◩
283. lockni+L12[view] [source] [discussion] 2025-12-18 07:07:01
>>manbit+F
> TIL I have a "open Hacker News" hand reflex

You mean it's not your homepage?

◧◩◪◨⬒⬓⬔
284. bigbup+D32[view] [source] [discussion] 2025-12-18 07:24:37
>>koakum+Sy1
Bet that felt great.
◧◩◪◨⬒⬓⬔⧯▣
285. jrowen+g62[view] [source] [discussion] 2025-12-18 07:52:32
>>the_af+xZ
I see you're downvoted, it wasn't me. I wasn't making any claim, you're making claims and disparaging remarks that you won't substantiate.
replies(1): >>the_af+5t2
◧◩◪◨⬒⬓
286. bayind+T72[view] [source] [discussion] 2025-12-18 08:11:46
>>lockni+oY1
If you like the thing you're managing, then its health is critical for you, not your users.

It's dang's baby at this point, and this is a good thing, as long as HN doesn't affect his life in ways he doesn't want.

replies(1): >>lockni+ec2
◧◩◪◨
287. tsouka+y92[view] [source] [discussion] 2025-12-18 08:29:05
>>dang+nb1
Thanks. It is so easy to change the IP using mobile that the unbanning is little hassle.
◧◩◪◨⬒⬓⬔
288. lockni+ec2[view] [source] [discussion] 2025-12-18 08:55:33
>>bayind+T72
[flagged]
replies(2): >>bayind+Qm2 >>dang+We5
289. ramong+uf2[view] [source] 2025-12-18 09:26:03
>>uyzstv+(OP)
when I realised the api still worked I put this together https://hackernewsx.com just to realise it will just work if I cleared my site data.
◧◩◪◨⬒⬓⬔⧯
290. Errone+vg2[view] [source] [discussion] 2025-12-18 09:37:04
>>wkat42+jt1
It's doable but it would be custom firmware and it's not really necessary. Two way paging isn't really worth doing because then you need a massive device with a massive battery, or something that uses uncontrolled mobile phone networks (and generally still has a massive battery, that lasts about a day).

You wouldn't even need particularly good encryption, you'd just need something adequate to stop casual eavesdropping really - "keep them busy for half an hour" would stop people from sniffing the POCSAG traffic and tweeting it, so that people show up at incidents and hang around filming it on their phones.

This incidentally is what a guy in England got arrested for a few years ago, exactly that. It's perfectly legal to listen to and decode pager messages (or any other radio messages), you're just not allowed to pass them on to people or act upon them, and posting them on twitter and then going round to rubberneck at the ongoing incident very much ticks those boxes. As with so many things in the UK, to paraphrase Aleister Crowley, "Don't Be A Dick shall be the whole of the law".

◧◩
291. rldjbp+Zj2[view] [source] [discussion] 2025-12-18 10:07:27
>>dang+zk
> 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.

it is a shame that it needs to be this way. as a lurker who doesn't stay logged in nor use incognito mode, i have seen "Sorry" page way too often, even when opening the "past" page from the homepage.

truly hope you find a solution that reduces friction for all. personally, it is back to "Sorry" situation for now.

PS: for others facing a similar situation, it all disappears after logging in, which has been the most reliable solution thus far.

replies(1): >>dang+Th5
◧◩
292. _shadi+bk2[view] [source] [discussion] 2025-12-18 10:09:53
>>dang+zk
> anti-crawler protections

what type of protections are used on HN? rate-limiting? ip range blacklist?

◧◩◪◨⬒⬓⬔⧯
293. bayind+Qm2[view] [source] [discussion] 2025-12-18 10:32:49
>>lockni+ec2
I have a pretty firm grip on life and touch plenty of grass both literally and figuratively.

However, when something I care about crashes and burns once in a blue moon, I make sure to put the fire out, at least to make it survive till regular hours. Things I care about can be both business and personal, and nobody bugs me for them.

Maybe we shouldn't make any assumptions about people we don't personally know, while we are at it.

replies(1): >>lockni+Uw3
◧◩◪◨⬒⬓⬔⧯
294. squeef+Rn2[view] [source] [discussion] 2025-12-18 10:42:54
>>seizet+QW
1. but social skills and genius are 2. im still staggered at how elementary it was 3. ok?
◧◩◪◨⬒⬓⬔⧯▣▦
295. the_af+5t2[view] [source] [discussion] 2025-12-18 11:28:26
>>jrowen+g62
Which disparaging remarks? I just claimed HN is ok/average, not "the smartest place on the internet", and that it's typical of online communities to consider themselves "the best".

The unsubstantiated claim that "HN is the smartest place on the internet" is an extraordinary claim requiring extraordinary evidence, which wasn't provided.

The downvotes only prove my point.

replies(1): >>jrowen+pt3
◧◩◪◨⬒⬓⬔⧯▣
296. phanta+2C2[view] [source] [discussion] 2025-12-18 12:44:11
>>abusta+yU1
> Anyway,anyone who finds themselves with a problem with HN should try that out :)

To be clear, I wasn’t complaining. Just pointing it out. Aside from any more speculative benefit to YC for running the site, the site does run outright ads.

replies(1): >>abusta+pc3
◧◩◪◨⬒⬓⬔
297. spacec+PG2[view] [source] [discussion] 2025-12-18 13:18:21
>>jacque+Vw1
Actually, I'm doing my best alienating these kind of people :p
replies(1): >>jacque+ue8
◧◩◪◨⬒
298. notach+RR2[view] [source] [discussion] 2025-12-18 14:16:15
>>chesch+dQ
oh interesting (honestly!), how is that it distinguished?
replies(1): >>chesch+q73
◧◩◪◨⬒⬓
299. chesch+q73[view] [source] [discussion] 2025-12-18 15:34:54
>>notach+RR2
Don’t let me distract from this learning opportunity with my armchair expertise. There are a lot of articles out there for this exact topic, but here’s one that’s pretty good.

https://relevancerecovery.com/habit-vs-addiction/

◧◩◪◨⬒⬓⬔⧯▣▦
300. abusta+pc3[view] [source] [discussion] 2025-12-18 15:52:26
>>phanta+2C2
Sorry, I didn't mean to imply you had a problem with ads. By "problem" I meant "if you find yourself procrastinating a lot" (not you specifically, but the reader in general)

Apologies for the misunderstanding

replies(1): >>phanta+rf3
◧◩◪◨⬒⬓⬔⧯▣▦▧
301. phanta+rf3[view] [source] [discussion] 2025-12-18 16:03:52
>>abusta+pc3
On, no issue here, no apology needed at all. I didn’t take it as any kind of dig, or even necessarily aimed at me (and if it was—still not offensive in any way). I’d almost edited my original comment right after posting because it occurred to me the tenseness might allow it to be interpreted as a complaint, and was just using your post as a jumping-off point to finally clarify that, is all.

I did miss exactly what you meant by “problem” in that passage, but get it now, so thanks for that.

◧◩◪◨⬒⬓⬔⧯▣▦▧
302. jrowen+pt3[view] [source] [discussion] 2025-12-18 16:57:25
>>the_af+5t2
> Of course, by internet law, HN (or a subset of its members) considers itself to be the smartest, more thoughtful online community.

I would call that disparaging.

If we're going to be pedantic, the post you initially quoted said "it's entirely possible" and "it seems likely." That's not a claim, that's a suggestion that invites a substantive counter-argument. Just saying "uh no, it's obviously not" is not substantive.

"It goes without saying HN is not the smartest" is more of a claim.

It really should not be that difficult to actually attempt to make an argument rather than point out that someone else's is probabilistically not totally factually correct. It's just bad faith, pure negation. You're defending the lack of substance in your argument by saying someone else's argument lacked substance. Put something forth yourself.

I'm not just trying to debate here, I am genuinely curious to hear about what other communities people find "smarter and more thoughtful." If they can't even be named then yes I am going to call that empty posturing.

replies(1): >>the_af+9D3
◧◩◪◨⬒⬓⬔⧯▣
303. lockni+Uw3[view] [source] [discussion] 2025-12-18 17:09:42
>>bayind+Qm2
> However, when something I care about crashes and burns once in a blue moon, I make sure to put the fire out, at least to make it survive till regular hours.

You are free what you choose to do with your personal life.

Meanwhile, it is pretty obvious that it's pointless to demand or expect personal sacrifice to maintain unrealistic levels of high-availability in services that are far from critical. I mean, do you honestly believe that these messages you and I are writing are so important to get out that someone must sacrifice their personal time to ensure it is served to the world in this very instant instead of, say, 3 or 6 or 13 hours? Absurd.

replies(1): >>bayind+oD3
◧◩◪◨⬒⬓⬔⧯▣▦▧▨
304. the_af+9D3[view] [source] [discussion] 2025-12-18 17:35:47
>>jrowen+pt3
Well, to be fair the comment that sparked this subtree asserted (maybe in jest? I hope!):

> It's a website with the smartest people in the world. The level of conversations here are unrivaled in internet communities.

Surely that HN is without question NOT the "unrivaled" website "with the smartest people in the world" should feel neither disparaging nor a surprise to you?

By the way, you got me wrong: I'm not really making a probabilistic argument. I genuinely don't think HN is populated by the smartest people on the internet. Nothing I've read here, in many years of being a regular, has led me to believe people here are anything other than average internet nerds/hackers/entrepreneurs. Maybe slightly above average? There's certainly interesting conversation to be had here, but why would I think HN has the smartest people?

> I'm not just trying to debate here, I am genuinely curious to hear about what other communities people find "smarter and more thoughtful." If they can't even be named then yes I am going to call that empty posturing.

I've zero interest in going down the route of exchanging subjective opinions with you about what is or isn't smart, nothing good can come out of it. I will point out many "rationalist" communities do believe themselves to be smarter than HN (do I agree with them? Nope. But that's not the point, is it? The point is that most serious online communities will tend to believe themselves better, and HN is no exception).

I'm sorry you feel this is "empty posturing". Maybe I just don't fit with the smartest people on the internet :(

◧◩◪◨⬒⬓⬔⧯▣▦
305. bayind+oD3[view] [source] [discussion] 2025-12-18 17:37:01
>>lockni+Uw3
It looks like I failed to convey what I've tried to say in the first comment. Let me reiterate one more time.

    - I believe dang sees HN as his baby, so *voluntarily* monitors it as a critical infrastructure *for him*.
    - I personally like this kind of commitment from people who like their job, however *I don't expect or demand it in any way*.
    - I also hope that attention doesn't affect his life. *Especially negatively and/or in a crippling way*.
I don't care whether this site is down for 6 seconds or 6 hours. I just wanted to commend him for liking what he's doing this much. I demand nothing from any service provider I use. Let it be a small, one person operation or dang or Amazon/Google.

I also keep servers up in my daily job, and some are more important than others, but none of them requires me to wake up 5AM to solve a problem (by design). So I don't demand anything from others something which I won't do.

As long as nobody is dying, nobody should stop, drop, and work on something else regardless of time, date and location.

◧◩◪◨
306. collin+eP3[view] [source] [discussion] 2025-12-18 18:32:59
>>dang+F71
Yes. It's hard to explain the experience of hosting a website since 2023.

A crazy amount of really dumb bots loading every url on the website in a full headless browser, with default Chrome user-agent string. All different ip addresses, various countries and ASNs.

These crawlers are completely automated and simply crawl _everything_ and don't care at all if there's value in what they're crawling or if there's duplicate content, etc.

There's no attempt at efficiency, just blindly crawl the entire internet 24/7. Every page load (1 per second or more?) is from a different ip address.

◧◩◪
307. mgarci+xx4[view] [source] [discussion] 2025-12-18 21:58:19
>>1shoon+ma
I've made https://deja.de.hueve.ar/hn so it snapshots the frontpage once per day - that way, I now there won't be new updates during the rest of the day, and the dopamine addiction goes down.
◧◩◪◨⬒⬓⬔⧯
308. dang+We5[view] [source] [discussion] 2025-12-19 03:42:48
>>lockni+ec2
Aw, please don't cross into personal attack. You can make your substantive points without that.

https://news.ycombinator.com/newsguidelines.html

Edit: it looks like you've been breaking the site guidelines quite a bit, unfortunately. Could you please not do that? We end up banning accounts that keep doing it and I don't want to ban you.

◧◩◪◨⬒
309. dang+pf5[view] [source] [discussion] 2025-12-19 03:48:48
>>ilamon+pL
Nope, total submissions. And it's still very much within that same window!
◧◩◪
310. dang+Th5[view] [source] [discussion] 2025-12-19 04:24:47
>>rldjbp+Zj2
Yes, and I'm sorry. We do our best but it's both a hard problem and a moving target.
◧◩◪
311. dang+6i5[view] [source] [discussion] 2025-12-19 04:27:30
>>Quantu+ht1
> Was the blocking returning “Sorry.”

> Presumably after those anti-crawler protections had been relaxed again

Yup and yup. Apologies for the inconvenience! If it happens again you're welcome to email us at hn@ycombinator.com with your IP and we'll unblock it for you.

◧◩◪◨⬒
312. andy_p+zo5[view] [source] [discussion] 2025-12-19 05:55:11
>>tempes+WK
This is completely wrong, everyone knows you should rewrite everything in microservices immediately :-D
◧◩◪◨⬒⬓⬔⧯
313. jacque+ue8[view] [source] [discussion] 2025-12-20 04:13:54
>>spacec+PG2
Good for you!
[go to top]