Unverified60% confidenceEventExact time
The 2017 AWS S3 US-East region outage caused a large number of websites and applications that relied on its storage service to go down simultaneously.
2
Sources
60%
Confidence
Long-term
Relevance
7/15/2026
First Seen
Sources
Related Claims
UnverifiedThe 2017 S3 outage affected a large number of well-known services including Slack, Trello, and IFTTT, and AWS's own service health status dashboard was also unable to display fault information normally because it relied on S3.77% similarUnverifiedAfter the 2017 S3 outage, AWS added multiple safety measures, including limiting the server capacity that can be removed in a single operation and accelerating the subsystem restart process.75% similarUnverifiedShinyHunters' preferred attack methods include exploiting misconfigured AWS S3 bucket permissions, credential stuffing attacks, and purchasing or exchanging previously leaked access credentials.61% similarUnverifiedThe most dangerous target of SSRF (Server-Side Request Forgery) in cloud environments is the IMDS instance metadata service, with AWS's IMDS address being 169.254.169.254.59% similarUnverifiedCompanies such as Amazon and Microsoft have used TLA+ in critical systems (such as the S3 storage protocol and Azure Cosmos DB) to discover concurrency defects that could not be exposed through code review and testing alone.58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/517697API
curl https://kongchang.com/api/v1/knowledge/claims/517697MCP
get_claim(id=517697)