Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack is offline

status.slack.com

Post reply on HN
Print view View original

31–40 of 131 posts

Re: Slack is offline

#31

Post by minimaxir »

internalfx wrote: post #27
gtdawg wrote: post #25

Earlier quoted context omitted.

Looks like it. When I first loaded HN 2 minutes after this outage started, the story was #2. Then I refreshed after 3 minutes and it wasn't on the front page at all. Used the search tool to find it and then upvoted.

Looks like somebody wants to keep this quiet. 65 points in 12 minutes is good enough to be #1.

It is infeasable to keep a global outage quiet.

Re: Slack is offline

#35

Post by grzm »

internalfx wrote: post #27
gtdawg wrote: post #25

Earlier quoted context omitted.

Looks like it. When I first loaded HN 2 minutes after this outage started, the story was #2. Then I refreshed after 3 minutes and it wasn't on the front page at all. Used the search tool to find it and then upvoted.

Looks like somebody wants to keep this quiet. 65 points in 12 minutes is good enough to be #1.

High comment rates can also trigger the "overheated discussion detector", which will downweight a submission.

Re: Slack is offline

#36

Post by Florin_Andrei »

munk-a wrote: post #3
cadr wrote: post #2

When the status page is returning a 500 error... not a good sign.

It's an even worse sign when the page half-loads with some stylesheets missing.

Maybe they should not serve the static content with "Cache-Control: max-age=1". That's rarely a good idea.

Re: Slack is offline

#37

Post by urda »

kiloreux wrote: post #11

I just realized that being a remote team. I can't join any of my teammates. Neither see live changes to the infrastructure and the repositories. The things we take for granted.

If slack being down means you lose all insight into your build process and code management, you seriously need to introduce a secondary option immediately.

Re: Slack is offline

#39

Post by typomatic »

urda wrote: post #37
kiloreux wrote: post #11

I just realized that being a remote team. I can't join any of my teammates. Neither see live changes to the infrastructure and the repositories. The things we take for granted.

If slack being down means you lose all insight into your build process and code management, you seriously need to introduce a secondary option immediately.

OP didn't say "all insight". There's a difference between being unable to see a stream of change events and not being able to see the current state of the system. The latter is completely unacceptable, whereas the former is just annoying.
Post reply on HN