However, we do not believe there was a widespread service issue on AWS’s platform. Luke Deryckx, the CTO of Downdetector’s parent company Ookla, told TechRadar on Wednesday, “We see a small number of credible reports that some AWS users had issues with their platform yesterday. That outage, caused by a software problem, affected everything from Disney amusement parks and Netflix videos to robot vacuums and Adele ticket sales. That number jumped 42% in the past year, as more and more companies rely on it with a significant portion of their employee base working remotely.Īny outage at AWS did not seem to be having the cascading effects that were seen last December.

The popular messaging service has more than 156,000 paying corporate customers (including Fortune). ET, but said that issue had been resolved at 9:48 p.m. Slack also experienced a separate outage for some customers the previous night at approximately 8 p.m. ET, its own service health dashboard showed that AWS was not, in fact, down. Amazon said that despite AWS outages appearing on Downdetector as of 12:23 p.m.

ET, the company added it was starting to see “signs of improvement” but was “still monitoring the situation.

We’re looking into the cause and will provide more information as soon as it’s available.”Īs of 12:07 p.m. Slack acknowledged the outage on its website’s status page, saying, “We’re investigating the issue where Slack is not loading for some users. Downdetector, which tracks internet outages, was showing significant spikes at both Slack and Amazon Web Services, although Amazon repeatedly denied to Fortune that it suffered a widespread outage.

Aws slack