This might be the longest downtime I've ever seen for Slack.
Slack outage: Connectivity issues affecting all workspaces
171–180 of 278 posts
Re: Slack outage: Connectivity issues affecting all workspaces
#172Earlier quoted context omitted.
Funny, our self-hosted infrastructure goes down weekly.
No offense, but you're probably doing it wrong
You just gave a good argument of why s/he should use Slack. Yeah s/he might be doing it wrong, but so what? One should focus on core business, not system administration.
Re: Slack outage: Connectivity issues affecting all workspaces
#173Does anyone know about any Slack alternatives that support bots, GIFYs and emojis ? And above all that is not ridiculously slow.
There's Google Chat if you use G Suite like us. https://chat.google.com/welcome
Or Atlassian's Stride is really great too: https://www.stride.com/
If your org happens to be part of the Microsoft Office 365 ecosystem, there's Microsoft Teams. All of the products support bots, gifys, and emojis. I personally think Google Chat and Stride are much faster than slack too. I haven't tried Microsoft Teams yet.
Re: Slack outage: Connectivity issues affecting all workspaces
#174Earlier quoted context omitted.
I think it's inexcusable for a chat program to go down in 2018. * your hdd failed? Use a raid * your power went out? Use a UPS * your DNS went down? Use a fallback (slack2) * your whole datacenter flooded? Good thing you have multiple replicated cloud instances that seamlessly take over See, these are the issues that "the cloud" was supposed to solve. Not give us the same problems as before, just with a recurring bil…
Slack is text, channels, images, video, sound, search, audio calls, video calls, screen share (and interface share), bots, myriad integrations, and more. Calling it just "send text from one computer to another" is wrong.
I think maybe their point is that even if other pieces break, why shouldn't it be possible for the text communication to keep working?
Re: Slack outage: Connectivity issues affecting all workspaces
#175What does Slack as a company use to communicate when Slack the product is down? :>
Re: Slack outage: Connectivity issues affecting all workspaces
#176Hope Slack considers doing a post-mortem similar to Gitlab[1]. Sharing what they learned and giving customers context is appreciated. [1]: https://about.gitlab.com/2017/02/10/postmortem-of-database-o...
Yes, that way we can beat them up for years to come based on whatever mistake they made. It would be even better if they told us which employee made the mistake so we can incessantly mock that employee openly and publicly every time Slack is ever mentioned on HN. When GitHub was purchased by Microsoft, Gitlab came up quite a bit and we got to rehash that whole database outage over again many times over those few days. It was sad.
If it were my company, I would say a little as humanly possible.
Re: Slack outage: Connectivity issues affecting all workspaces
#177I imagine people felt more productive today without Slack
Re: Slack outage: Connectivity issues affecting all workspaces
#178You know how much of the community uses one messaging system when 15 minutes after it going down, it has over 40 points on the front page! This says a lot about how it's a single point of failure in modern company comms. It's even worrying to think about how some users probably have production-dependent (dare I postulate it) workflows in Slack that get crippled by its outage... ITT: Chat about decentralisation that w…
I worked at an open source company where they hosted their own IRC server. There are OSS alternatives to Slack and I wonder if that company has tried to adopt any of them. This all goes back to one basic fact: The Cloud is Someone Else's Computer(tm). If your hosted Confluence or Jira is down, you can go walk over to your IT team and they'll be like, "Yea we know. We broke something. We're working on it." If you're u…
That's uptime-as-anecdote. Yes, you can throw your entire IT department at your outage instead of waiting on the vendor to fix it. How many of us work somewhere where the entire IT team is as large as the team that works on Slack's uptime?
Re: Slack outage: Connectivity issues affecting all workspaces
#179Earlier quoted context omitted.
Yes it's a single point of failure, but so what? I don't particularly care whether other organizations fail at the same time as I do, I just care whether I fail. Hosting my own chat system does not solve that problem. In fact, it may make it worse because then I have to worry about system administration, and Slack probably has more expertise on that. It's likely that they can fix this problem for all customers faster…
I think it's inexcusable for a chat program to go down in 2018. * your hdd failed? Use a raid * your power went out? Use a UPS * your DNS went down? Use a fallback (slack2) * your whole datacenter flooded? Good thing you have multiple replicated cloud instances that seamlessly take over See, these are the issues that "the cloud" was supposed to solve. Not give us the same problems as before, just with a recurring bil…
Let me add more reasons:
1) Software human mistake, when some software error/exception throws much larger issues, that require manual restore with service downtime.
2) Geodistributed datacenters is VERY expensive thing, so not implemented fully.
3) Bad system design, full of "one point of failure".
Re: Slack outage: Connectivity issues affecting all workspaces
#180Earlier quoted context omitted.
I worked at an open source company where they hosted their own IRC server. There are OSS alternatives to Slack and I wonder if that company has tried to adopt any of them. This all goes back to one basic fact: The Cloud is Someone Else's Computer(tm). If your hosted Confluence or Jira is down, you can go walk over to your IT team and they'll be like, "Yea we know. We broke something. We're working on it." If you're u…
That's uptime-as-anecdote. Yes, you can throw your entire IT department at your outage instead of waiting on the vendor to fix it. How many of us work somewhere where the entire IT team is as large as the team that works on Slack's uptime?
How many self-hosted setups need the complexity and matching team size of a centralized service serving millions of users?