4 ms·
Maybe I'm reading too much into it, but "We've received word that all workspaces are having troubles connecting to Slack." makes it sound like their internal mo
by r1ch 8y ago
Maybe I'm reading too much into it, but "We've received word that all workspaces are having troubles connecting to Slack." makes it sound like their internal monitoring didn't catch whatever is causing this. I was personally experiencing issues for about 20-30 minutes before the status update was posted.
- bsiemon 8y agoI think that is just the tongue in cheek language they like to use.
- Dirlewanger 8y agoYeah, it's really funny and ironic when you cost customers money!
- joobus 8y agoTheir subsequent update makes it sound like they still don't have a clue. > Our team is still looking into the cause of the connectivity issues, and we'll continue to update you on our progress.
- raphaelj 8y agoWe started having issues connecting to Slack 4 hours before they reported a status.
- parliament32 8y agoPretty much every time there's a slack outage it takes them a solid 20 minutes to update their status page. Several times I've emailed them 10 minutes into an outage (following "nobody at the office can reach slack, but their status page says smooth sailing, we should do more diagnostics in case it's office internet or something..."), then gotten a response 10 minutes later to the tune of "we're aware, we just updated our status page, go look at that". I think they consider updating their status page a PR problem, so they avoid if if the issue can be fixed in under X minutes. Which also makes their uptime totals completely bogus.