201–210 of 840 posts
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.
I'm migrating to Rocket.chat on Digital Ocean as we speak. Has anyone else made the move or tested Rocket.chat?
My old company used a mix of Slack and RocketChat. Functionally, it's fine but I was never a big fan of the UI and how attachments were handled. Also, cross-channel search was kinda bad. Mind you, this was well over a year ago so I'm sure things have improved.
Earlier quoted context omitted.
I would be shocked if Slack operations wasn’t aware of this return to work spike and didn’t pre-scale in anticipation.
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
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?
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
When I was at Uber, we noticed that most incidents are directly caused by human actions that modify the state of the system. Therefore, a large "backlog" of human actions that modify the system state have a much higher chance of causing an incident. My bet is that this incident is caused by a big release after a post-holiday "code freeze".
To elaborate a bit more on this point, you have to think about it like any complex system failure - it's almost never one thing, but rather a combination of many different factors. The factors around post NYE releases: - high risk changes that weren't released pre-holidays get released. Depending on the company, this could mean a 1-week to 1-month delay between implementation and release. The greater that interval, t…
Earlier quoted context omitted.
If you're asking genuinely then I can tell you my experience when I was part of a SaaS shop, though the times have changed a lot and "my metric is not necessarily your metric". But it was roughly "one large impact a month, for six months", with large caveats that upper management for whatever company had to be working with the product during that month. Large companies don't care if X service went out during the nigh…
> But migrating everything is _so painful_ This is a key point is the popularity amongst VCs in investing in B2B SaaS. I take their (and your) word for it. But honestly, I don't actually understand this. Why is migration so hard?
The really big one, for companies of a certain size / cash flow, is compliance. Companies spend a lot of time developing compliant work flows around a service like Slack.
Migrating to another service requires rewriting the compliance narrative. The current compliance people might not have the confidence or willpower to do that effectively, and can raise legal objections to any such migration indefinitely.
My biggest frustration with these outages is they're hard outages across all of Slack. There's no reasonable work arounds or fallback features. A plaintext web interface would keep my team moving along while they resolve their issues.
"Let's see, I'll look up so and so's name with Sla.... shoot"
"Okay, I'll just find that thing I .... nevermind"
Earlier quoted context omitted.
My feeling is this is an AWS issue. Our services hosted in AWS are not working either.
I have also been having intermittent issues with Twitter also this morning (can't load tweets etc) and was wondering if it was connected.
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.
One of those affects money via SLA's. Slack is still up, just not usable.
I.e., it's down.
(And if you're saying that according to the legal blah blah blah of the SLA that this isn't technically "down", then there might as well not be an SLA.)