On August 26, 2020 around 9:30 a.m. PDT, some customers in North America had trouble loading Slack and may have experienced a "Something's gone awry" error message.
We carried out a thorough investigation and observed trends with ISPs in the region, but found no evidence of an issue on our side. By 12:05 p.m., error rates had subsided, and we received confirmation from several users that they could use Slack again. While no remedial action was taken on our side, we're analyzing data from this event to understand ways to mitigate an issue like this in the future.
9:42 PM PST
Our investigation indicates affected users in North America should be able to load Slack again. Please let us know if you're encountering any trouble.
2:00 PM PST
We're continuing to investigate the source of the issue, but we're seeing signs of improvement as the rate of connection errors are down from previous levels.
Please let us know at email@example.com if you're encountering any trouble. Thanks for your patience today.
12:30 PM PST
Some customers may be unable to load Slack. Initial reports indicate this is isolated to an Internet Service Provider (ISP) in North America. We're sorry for the disruption. Thank you for bearing with us.
11:37 AM PST
On August 26, 2020 between 4:03 p.m. PDT and 5:16 p.m. PDT, some customers had trouble connecting to Slack.
We launched an investigation and determined the issue was caused by an ongoing load test that impacted our core service. As the test ended, users were able to connect to Slack again by 5:16 p.m. PDT. We're working on preventive measures to ensure this doesn't happen in the future.
4:03 PM PST