Slack outage: Connectivity issues affecting all workspaces

Post by dustinmoorenet » Wed, Jun 27, 2018, 4:15 PM UTC

dota_fanatic wrote: post #163

mikec3010 wrote: post #154

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

Post by [deleted] » Wed, Jun 27, 2018, 4:16 PM UTC

bgribble wrote: post #141

switch007 wrote: post #126

Earlier quoted context omitted.

That's interesting. More speculation: they haven't given any detail in 2 hours, perhaps if it's an upstream/3rd-party problem, they haven't been given any info.

I know it's not exactly scientific, but the front page of https://downdetector.com shows a number of services that have problem spikes starting anywhere from 3am US/Eastern to 9am US/Eastern and continuing through now (11:24 US/Eastern): Google Home, Fortnite, Exede, Level 3, New York Times, AWS. Maybe totally unrelated to each other, who knows.

Post by coryfklein » Wed, Jun 27, 2018, 4:17 PM UTC

trcollinson wrote: post #176

dannyrosen wrote: post #153

Hope 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…

Post by sammorrowdrums » Wed, Jun 27, 2018, 4:18 PM UTC

ufmace wrote: post #165

sammorrowdrums wrote: post #102

Surely some of the Slack team are hiding on here? Any idea what's going on? ;)

If they are, I sure hope they're doing something more productive than surfing HN

  - nope but maybe at some point a yep
  - still nope
  - nope
  - nope

Post by rbranson » Wed, Jun 27, 2018, 4:19 PM UTC

mikec3010 wrote: post #154

FooBarWidget wrote: post #90

Earlier 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…