{"id":16162,"date":"2022-02-23T02:28:33","date_gmt":"2022-02-23T02:28:33","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/23\/down-day-slack-github-walmart-aws-all-suffer-outages-or-other-issues\/"},"modified":"2022-02-23T02:28:33","modified_gmt":"2022-02-23T02:28:33","slug":"down-day-slack-github-walmart-aws-all-suffer-outages-or-other-issues","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/23\/down-day-slack-github-walmart-aws-all-suffer-outages-or-other-issues\/","title":{"rendered":"Down day: Slack, GitHub, Walmart, AWS all suffer outages or other issues"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

Several large sites and services suffered issues and downtime today in what could be a range of possible coincidences or might share a common root cause.<\/p>\n

Salesforce.com Inc.\u2019s Slack led the pack, with some reports<\/a> suggesting it was offline for as long as five hours, but it was not alone. Microsoft Corp.-owned GitHub, Walmart Inc., Peloton Inc.,\u00a0Comcast Cable Communications LLC\u2019s Xfinity and Amazon Web Services Inc. are all reported to have had issues.<\/p>\n

That AWS was on the list led some to suggest that AWS issues could have been to blame for the service disruption on other sites and services.<\/p>\n

Slack first posted on a support thread<\/a> at 9:25 a.m. EST that it was investigating reports that the team communications service was not loading for some users. By 12:07 p.m., a status update said that \u201cwe\u2019re seeing signs of improvement.\u201d The last update at 2:24 p.m. stated that \u201cwe\u2019ve resolved the issue.\u201d<\/p>\n

\u201cThanks for bearing with us and we apologize for the disruption to your work day!\u201d the final status concluded but did not provide any information as to what the issue was.\u00a0Slack last suffered an outage on Jan. 4<\/a> that was about five hours long as well. Slack did not disclose what caused the outage in the previous case either.<\/p>\n

Data Center Dynamics noted<\/a>\u00a0that it\u2019s possible that Slack\u2019s outage was caused by an unrelated software issue and just occurred at the same time as the AWS and Xfinity issues. That could be true, but it\u2019s an interesting coincidence.<\/p>\n

The AWS Service Health Dashboard did not show any outages during the time Slack was experiencing issues, but that has occurred before when there have been AWS issues. Reports to Downdetector show a different picture<\/a>, with reports of issues with AWS starting to flow in from around 9 a.m. before peaking at 11:27 a.m.<\/p>\n

Despite being owned by Microsoft, GitHub still has services hosted on AWS and suffered outages at around the same time, although the first reports of issues<\/a> started at 4 a.m. Reports<\/a> of Walmart having issues peaked at 11:33 a.m.<\/p>\n

Other companies were reported to be having issues at around the same time. Users of Zoom Video Communications Inc., another AWS customer, reported issues<\/a>\u00a0as well, with the number peaking after 11 a.m.<\/p>\n

Without any confirmation as to the cause of the outages by those affected, it\u2019s impossible to know exactly what the cause was, but there is one common thread: AWS is the host in most if not all of the cases.<\/p>\n

Photo: Slack<\/h5>\n
\n
\n

Show your support for our mission by joining our Cube Club and Cube Event Community of experts. Join the community that includes Amazon Web Services and Amazon.com CEO Andy Jassy, Dell Technologies founder and CEO Michael Dell, Intel CEO Pat Gelsinger and many more luminaries and experts.<\/span><\/h3>\n<\/div><\/div>\n