If you’d like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one. PDT on October 1, the majority of DNS records for the domain had refreshed, and connectivity to Slack returned to baseline levels. We’re grateful to the internet service providers and DNS community members who worked quickly to refresh records around the globe, improving conditions for many impacted users.īy around 8:49 a.m. In the meantime, we reached out to third-party DNS resolvers to request they refresh the record for the domain, which would resolve the issue for Slack users on that DNS resolver. Because some internet service providers and public resolvers persist records for up to 24 hours as a standard practice, the issue continued for a percentage of users.
As a result, some third-party DNS resolvers failed to return records for the domain. at last we were all together on the top his foot being by now surrounded by a solid mass of ice. on September 30, but some third-party DNS resolvers still expected the configuration to exist in our domain. 'But the line's quite slack down here,' he shouted. Out of caution, we rolled back this configuration change at 10:02 a.m.
A small number of third-party DNS resolvers did not properly interpret the change, causing some users to be unable to connect to Slack. PDT on September 30, we introduced a DNS (Domain Name System) configuration change to our domain, designed to improve the security of domain name lookups. This may have prevented access to the Slack desktop app, mobile app, or any websites under the domain.Īt 8:21 a.m. JSlack, the widely used messaging platform, experienced an outage of just over an hour early Thursday, disrupting life in offices around the world (including this reporter’s). published 22 February 2022 (Image: Shutterstock / rafapress) If you experienced issues with Slack not working for you this morning, you're not alone. PDT, some users were unable to load Slack.
0 kommentar(er)
