We've made some configuration changes that we believe should allow all impacted users to once again access Slack. Thank you all for your patience and help in debugging the intermittent and location-sensitive empty DNS responses that have plagued us this weekend. If problems persist and clearing your local machine's DNS caches does not fully fix the problem, please email firstname.lastname@example.org for help.
Between 7:52am PDT and 7:58am PDT Slack was serving 503 errors for 50% of all requests to slack.com. This was caused by a DNS misconfiguration and the change has now been reverted. The status.slack.com was also overloaded during this time and it may have been inaccessible.
We continuously monitor the status of slack.com and all its related services. If there are any interruptions in service, a note will be posted here. We will also post notices of scheduled downtime on this page.
Slack is a distributed platform and during any given incident it is rare for all Slack teams to be affected. For this reason, we report our uptime as an average derived from the number of affected users.
If you are experiencing problems connecting to Slack and do not see a notice posted, please email email@example.com. Follow us on Twitter for status updates.