{"id":7826,"date":"2025-10-21T10:03:29","date_gmt":"2025-10-21T10:03:29","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2025\/10\/21\/aws-declares-major-outage-resolved-after-nearly-24-hours-of-disruption\/"},"modified":"2025-10-21T10:03:29","modified_gmt":"2025-10-21T10:03:29","slug":"aws-declares-major-outage-resolved-after-nearly-24-hours-of-disruption","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2025\/10\/21\/aws-declares-major-outage-resolved-after-nearly-24-hours-of-disruption\/","title":{"rendered":"AWS Declares Major Outage Resolved After Nearly 24 Hours of Disruption"},"content":{"rendered":"<p>    AWS Declares Major Outage Resolved After Nearly 24 Hours of Disruption<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>Amazon Web Services (AWS), the world\u2019s largest cloud computing provider, has officially marked a widespread outage in its US-EAST-1 region as resolved, following nearly a full day of cascading failures that disrupted services for millions worldwide. <\/p>\n<p>The incident, which began late on October 19, 2025, and persisted until early afternoon on October 20, highlighted the fragility of global internet infrastructure reliant on AWS\u2019s backbone. <\/p>\n<p>By 3:01 PM PDT, AWS confirmed all services had returned to normal operations, though some backlogs in data processing for tools like AWS Config and Redshift were expected to clear within hours.<\/p>\n<p>The outage originated from DNS resolution issues affecting the DynamoDB API endpoint in the US-EAST-1 region, AWS\u2019s busiest data center in Northern Virginia. <\/p>\n<p>At 11:49 PM PDT on October 19, elevated error rates and latencies emerged across multiple services, initially pinpointed to DynamoDB, a core database service powering everything from user data to application backends. <\/p>\n<p>Engineers identified the root cause by 12:26 AM PDT on October 20, linking it to a faulty DNS update that prevented applications from locating server IP addresses, akin to a broken phonebook for the internet. <\/p>\n<p>This failure triggered a domino effect: EC2 instance launches stalled due to DynamoDB dependencies, Network Load Balancer health checks failed, and connectivity broke for services like Lambda, SQS, and CloudWatch.\u200b<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-100-aws-services-impacted\"><strong>100+ AWS Services Impacted<\/strong><\/h2>\n<p>The blast radius was immense, impacting over 100 AWS services and spilling over to consumer-facing platforms. <\/p>\n<p>Popular apps such as Snapchat, Fortnite, Roblox, and Coinbase went offline, with users unable to log in or access features amid surging <a href=\"https:\/\/cybersecuritynews.com\/aws-outage\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">complaints on<\/a> DownDetector.<\/p>\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\">\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-twitter\">\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\"><img data-recalc-dims=\"1\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/s.w.org\/images\/core\/emoji\/16.0.1\/72x72\/1f53b.png?ssl=1\" alt=\"\ud83d\udd3b\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\"> AWS Outage Impacts Amazon, Snapchat, Prime Video, Canva and More \u2013 Update <\/p>\n<p>Read more: <a href=\"https:\/\/t.co\/zSW1UCNRUa\">https:\/\/t.co\/zSW1UCNRUa<\/a><\/p>\n<p>A widespread Amazon Web Services (AWS) outage on Monday disrupted operations for millions of users worldwide, knocking out access to everything from streaming giants\u2026 <a href=\"https:\/\/t.co\/ZPZkMNZvR9\">pic.twitter.com\/ZPZkMNZvR9<\/a><\/p>\n<p>\u2014 Cyber Security News (@The_Cyber_News) <a href=\"https:\/\/twitter.com\/The_Cyber_News\/status\/1980262666599010554?ref_src=twsrc%5Etfw\">October 20, 2025<\/a>\n<\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n<\/div>\n<\/div>\n<\/figure>\n<p>Gaming services like Epic Games\u2019 Fortnite reported server downtimes, while financial platforms including Venmo and banking apps from Lloyds and Halifax in the UK faced login hurdles. <\/p>\n<p>Even Amazon\u2019s own ecosystem suffered Prime Video buffering spiked, Ring doorbells lost remote access, and e-commerce checkouts faltered. <\/p>\n<p>AI startup Perplexity attributed its disruptions directly to the AWS issue, with CEO Aravind Srinivas noting on X that funds remained safe but access was blocked. <\/p>\n<p>Government agencies, airlines like Delta, and media outlets including Disney+ and The New York Times also logged interruptions, underscoring AWS\u2019s 33% market dominance in cloud infrastructure.\u200b<\/p>\n<p>Critics pointed to the 75-minute diagnostic delay and initial \u201call clear\u201d status page messages as transparency shortfalls, echoing past AWS critiques on outage notifications. <\/p>\n<p>No cyberattack was suspected; it stemmed from an internal update error in a foundational service.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-aws-response\"><strong>AWS Response<\/strong><\/h2>\n<p>AWS\u2019s response involved parallel mitigations: flushing DNS caches, throttling EC2 launches to stabilize subsystems, and scaling up polling rates for SQS queues tied to Lambda. <\/p>\n<p>By 2:24 AM PDT, the core DynamoDB DNS fix was deployed, yielding early recovery signs, though network issues lingered into the morning. <\/p>\n<p>Temporary throttles on operations like asynchronous Lambda invocations helped prioritize critical paths, with full EC2 launch restoration by 2:48 PM PDT. <\/p>\n<p>Global features dependent on US-EAST-1, such as IAM updates and DynamoDB Global Tables, also rebounded, allowing support case creations to resume.<\/p>\n<p>AWS promised a detailed post-incident summary, emphasizing ongoing backlog processing for analytics in Connect and Redshift. <\/p>\n<p>Experts like those at ThousandEyes noted no external network anomalies, confirming the issue\u2019s internal nature and rapid recovery post-mitigation. <\/p>\n<p>As services return to normal, affected users should try their operations again and check the <a href=\"https:\/\/health.aws.amazon.com\/health\/status\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">AWS Health Dashboard<\/a> for updates.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(180deg,rgb(238,238,238) 94%,rgb(169,184,195) 100%)\"><strong>Follow us on <a href=\"https:\/\/news.google.com\/publications\/CAAqMggKIixDQklTR3dnTWFoY0tGV041WW1WeWMyVmpkWEpwZEhsdVpYZHpMbU52YlNnQVAB?hl=en-IN&amp;gl=IN&amp;ceid=IN:en\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Google News<\/a>, <a href=\"https:\/\/www.linkedin.com\/company\/cybersecurity-news\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">LinkedIn<\/a>, and <a href=\"https:\/\/x.com\/cyber_press_org\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">X<\/a> for daily cybersecurity updates. <a href=\"https:\/\/cybersecuritynews.com\/contact-us\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Contact us<\/a> to feature your stories.<\/strong><\/p>\n<p>The post <a href=\"https:\/\/cybersecuritynews.com\/aws-outage-resolved\/\">AWS Declares Major Outage Resolved After Nearly 24 Hours of Disruption<\/a> appeared first on <a href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Guru Baran<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/aws-outage-resolved\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>AWS Declares Major Outage Resolved After Nearly 24 Hours of Disruption Amazon Web Services (AWS), the world\u2019s largest cloud computing provider, has officially marked a widespread outage in its US-EAST-1 region as resolved, following nearly a full day of cascading failures that disrupted services for millions worldwide. The incident, which began late on October 19, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,1440],"tags":[130],"class_list":["post-7826","post","type-post","status-publish","format-standard","hentry","category-cyber-security-news","category-tech-news","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/7826"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=7826"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/7826\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=7826"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=7826"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=7826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}