Slack is experiencing a service disruption

<a href="https:&#x2F;&#x2F;lists.dns-oarc.net&#x2F;pipermail&#x2F;dns-operations&#x2F;2021-September&#x2F;021340.html" rel="nofollow">https:&#x2F;&#x2F;lists.dns-oarc.net&#x2F;pipermail&#x2F;dns-operations&#x2F;2021-Sep...</a>

You can test it at home using &quot;delv www.slack.com @4.2.2.1 +rtrace&quot; (4.2.2.[1-6] are Level 3&#x27;s servers):<p><pre><code> ;; fetch: www.slack.com&#x2F;A ;; fetch: com&#x2F;DS ;; fetch: .&#x2F;DNSKEY ;; fetch: slack.com&#x2F;DS ;; fetch: com&#x2F;DNSKEY ;; fetch: www.slack.com&#x2F;DS ;; validating slack.com&#x2F;SOA: got insecure response; parent indicates it should be secure ;; no valid RRSIG resolving &#x27;www.slack.com&#x2F;DS&#x2F;IN&#x27;: 4.2.2.1#53 ;; broken trust chain resolving &#x27;www.slack.com&#x2F;A&#x2F;IN&#x27;: 4.2.2.1#53 ;; resolution failed: broken trust chain</code></pre>

Could be related to the currently ongoing Let&#x27;s Encrypt certificate expiration event(1) that is causing fun for engineers today(2).<p>(1) <a href="https:&#x2F;&#x2F;community.letsencrypt.org&#x2F;t&#x2F;help-thread-for-dst-root-ca-x3-expiration-september-2021&#x2F;149190" rel="nofollow">https:&#x2F;&#x2F;community.letsencrypt.org&#x2F;t&#x2F;help-thread-for-dst-root...</a><p>(2) <a href="https:&#x2F;&#x2F;twitter.com&#x2F;search?q=letsencrypt&amp;src=typed_query&amp;f=live" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;search?q=letsencrypt&amp;src=typed_query&amp;f=l...</a>

If you can&#x27;t reach slack.com, here&#x27;s their status page: <a href="https:&#x2F;&#x2F;slack-status.azureedge.net&#x2F;2021-09&#x2F;06c1e17de93e7dc2" rel="nofollow">https:&#x2F;&#x2F;slack-status.azureedge.net&#x2F;2021-09&#x2F;06c1e17de93e7dc2</a>

From their status page<p>&gt; 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.

Switching to Cloudflare DNS fixed this for me

I like how all 5 status updates (as of now) basically say the same thing, though they rushed the third one and forgot to apologize :)

Wow no DNS A Record for slack.com. Somebody fucked up

These are my favorite outages

Started a new job in July. It&#x27;s my first time using slack so heavily for day to day business needs. After some adjustment I&#x27;ve gotten used to it and enjoy it a lot. Now it&#x27;s down and I feel like I can&#x27;t do anything. We have gchat available but no one else is using it and we can&#x27;t recreate our slack channels in gchat. I&#x27;ve been rendered totally ineffective.

Finally, we can get some work done, kekkek

As I&#x27;ve used slack over the last 5 years I&#x27;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 &quot;quality via escalation&quot; anti-pattern.

Could it be related to: <a href="https:&#x2F;&#x2F;techcrunch.com&#x2F;2021&#x2F;09&#x2F;21&#x2F;lets-encrypt-root-expiry&#x2F;" rel="nofollow">https:&#x2F;&#x2F;techcrunch.com&#x2F;2021&#x2F;09&#x2F;21&#x2F;lets-encrypt-root-expiry&#x2F;</a>?

<a href="https:&#x2F;&#x2F;downdetector.com&#x2F;status&#x2F;slack&#x2F;" rel="nofollow">https:&#x2F;&#x2F;downdetector.com&#x2F;status&#x2F;slack&#x2F;</a>

Shopify has been down quite a bit today as well.

I managed to find a work around by connecting using my company&#x27;s VPN but still can&#x27;t do directly on my home line

It can&#x27;t be great, working something where if you cause an outage, your entire industry knows in five minutes.

Slack is continuing to have issues this morning. You know it&#x27;s bad when even the status page is down.

Anyone have theories if they could have (and if so, why didn&#x27;t they) just put back the signatures?

If only DNS wasn&#x27;t so slow.

We had this issue with a desktop client, this seems to be working for us as a fix:<p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;Zap42&#x2F;status&#x2F;1443647882045927427" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;Zap42&#x2F;status&#x2F;1443647882045927427</a><p>Also, just waiting, or maybe rebooting.<p>Edit: ah wrong thread sorry! This is re: letsencrypt.

It&#x27;s quite bad at the moment. I can&#x27;t message anyone at work!

Productivity, on the other hand, is through the roof.

&gt;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 &#x27;em know to flush their DNS record. I&#x27;m sure the T1 rep will absolutely know how to handle that.

This is a good thing.