Live data from Hacker News

Slack is down

status.slack.com

231–240 of 840 posts

Re: Slack is down

#231
post #155

Maybe we can chat with coworkers here. Is there a Carl around?

I have tried to sell my organisation on a shared Google Chat doc for 90s style realtime ICQ chat in times like these, but there has been little uptake.

Well now's the time for a big push!

Oh wait, how would you share the link...

Re: Slack is down

#232
post #162

I find it amazing that we can be about an hour and a half into a service being completely unusable(ie. Slack telling me it 'cannot connect'), yet it's still marked as an 'incident' instead of an 'outage' in their own status page

It's marked as an outage now.

Interestingly their uptime for the quarter is still 100% despite a full-red dashboard. I wonder if that's something that is calculated only after an outage is resolved

Re: Slack is down

#233

Earlier quoted context omitted.

It's marked as an outage now.

and yet they're still proudly proclaiming: "Uptime for the current quarter: 100%"

Every time this kind of thing happens HNers love to grip about how the status pages aren't correct yet. It's so weird -- like the people freaking out about the outage are going to be updating their uptime trackers right now or something. Who cares? It'll be fixed later.

Re: Slack is down

#235
post #203

Earlier quoted context omitted.

I wouldn't, since my personal theory is that the outage is due to AWS and GCP autoscale capacity exhaustion. We'll find out soon enough! EDIT: And down goes Notion, too: https://news.ycombinator.com/item?id=25634159

>AWS and GCP autoscale capacity What does this mean? What do cloud providers do when customers scale down their services? Do the providers literally power down servers? Do they sell the capacity to new customers?

They rate limit how fast you can auto scale which is dependent on a slew of factors.

Re: Slack is down

#236

Funny how status.slack.com has reported Incidents and Outages for a while now, but still the "Uptime for the current quarter" is reported at 100% on the bottom right of the status table.

It may depend on how they define the "quarter". If they take the quarter as the last 91 days and round the number to the closest percent, you might not see it changed unless the outages go more than 91x24x0.5% or 10.92 hours.. It's quite subjective and a guess.

Re: Slack is down

#238
post #203

Earlier quoted context omitted.

I wouldn't, since my personal theory is that the outage is due to AWS and GCP autoscale capacity exhaustion. We'll find out soon enough! EDIT: And down goes Notion, too: https://news.ycombinator.com/item?id=25634159

>AWS and GCP autoscale capacity What does this mean? What do cloud providers do when customers scale down their services? Do the providers literally power down servers? Do they sell the capacity to new customers?

They sell unused capacity at a much lower price (spot instances on AWS, preemptible VMs on GCP).

I don't know if they power down some servers if usage stays low for a very long time.

Re: Slack is down

#240
post #17

These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.

EFnet was always splitting every few hours. I don't really miss IRC compared to modern chat systems.

I spent a few hours setting up a chat client for a reason. Slack takes all this away from me.
Post reply on HN