![]() ![]() ![]() Nevertheless, with tech powerhouses Cisco and Microsoft as competitors, Slack can no longer afford to look weak. "You remember those outages you remember the old days when would be down, and it would be down for very perceivable amounts of time." ![]() "Once upon a time, in the very, very, very early days of Slack, they were built on a model that couldn't scale," said Michael Facemire, an analyst at Forrester Research. ![]() Some analysts pointed out that Slack's performance was much worse when it was starting out. We're learning and evolving and growing and making the service better along the way." "This is such a complex piece of software. "To be frank, we're still learning as we go," said Julia Grace, senior director of infrastructure engineering at Slack, based in San Francisco. Since January 2015, the company has grown from 1.1 million daily users to 8 million regular users today. In an interview last month, a Slack representative acknowledged the company's rapid growth has been challenging to keep up with at times. Despite the troubles, Slack has yet to announce the leader of a safety engineering team it formed in March to improve its uptime. 9, about 2.5 hours on May 21 and roughly 20 minutes on May 23. That list of outages includes more than two hours last Oct. But when contacted again on Thursday, a Slack spokesperson said the company had done another review and identified eight major Slack outages in that time frame. Last month, Slack said it had suffered only four significant disruptions since May 2017. Slack said this week's outage was due to "a bug included in an offline batch process of data." Whether Slack is suffering only growing pains, as opposed to a severe flaw in its technology, is difficult to determine without insight into the exact cause of each incident. "I think the recent outages certainly open up an avenue of attack by Slack's competitors and will raise red flags for customers and prospects as to whether they can rely on the app for business-critical communications," said Irwin Lazar, an analyst at Nemertes Research, based in Mokena, Ill. If you’d like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one.Analysts warned if the Slack outages continue, rivals Microsoft, Cisco and Atlassian could use them as a reason for companies to avoid the fast-growing startup. 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. on September 30, but some third-party DNS resolvers still expected the configuration to exist in our domain. 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. PDT, some users were unable to load Slack. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |