Could be related to the currently ongoing Let's Encrypt certificate expiration event(1) that is causing fun for engineers today(2).<p>(1) <a href="https://community.letsencrypt.org/t/help-thread-for-dst-root-ca-x3-expiration-september-2021/149190" rel="nofollow">https://community.letsencrypt.org/t/help-thread-for-dst-root...</a><p>(2) <a href="https://twitter.com/search?q=letsencrypt&src=typed_query&f=live" rel="nofollow">https://twitter.com/search?q=letsencrypt&src=typed_query&f=l...</a>
If you can't reach slack.com, here's their status page:
<a href="https://slack-status.azureedge.net/2021-09/06c1e17de93e7dc2" rel="nofollow">https://slack-status.azureedge.net/2021-09/06c1e17de93e7dc2</a>
From their status page<p>> Less than 1% of users may be experiencing trouble connecting to Slack<p>This is a good example of how to not communicate uptime issues. It clearly shows that Slack is trying to downplay the problem and do damage control. This is not smart and gets customers upset.
Started a new job in July. It's my first time using slack so heavily for day to day business needs. After some adjustment I've gotten used to it and enjoy it a lot. Now it's down and I feel like I can't do anything. We have gchat available but no one else is using it and we can't recreate our slack channels in gchat. I've been rendered totally ineffective.
As I've used slack over the last 5 years I've come to the conclusion that they have a quality problem of some sort. The software just behaves weird, especially in the voice and screen sharing areas.<p>It seems like their management runs the "quality via escalation" anti-pattern.
Could it be related to: <a href="https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/" rel="nofollow">https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/</a>?
We had this issue with a desktop client, this seems to be working for us as a fix:<p><a href="https://twitter.com/Zap42/status/1443647882045927427" rel="nofollow">https://twitter.com/Zap42/status/1443647882045927427</a><p>Also, just waiting, or maybe rebooting.<p>Edit: ah wrong thread sorry! This is re: letsencrypt.
>We are aware of connectivity issues (…) In order to resolve this faster, your ISP (Internet Service Provider) will need to flush their DNS record for slack.com. Please reach out to your networking team to provide them with this information.<p>Yeah, sure, lemme just pick up the phone and call my ISP and let 'em know to flush their DNS record. I'm sure the T1 rep will absolutely know how to handle that.