Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The AWS outage that disrupted Fortnite, Roblox, the Epic Games Store, Wordle and other online services was a historical incident on October 19–20, 2025—not a current outage. AWS traced the initial failure to a race condition in its automated DynamoDB DNS-management system in the US-EAST-1 region in Northern Virginia. The resulting cascade affected authentication, databases, matchmaking, scaling, load balancing and other backend services.
Recovery happened in stages. AWS said the customer-impacting incident ended at 2:20 p.m. PDT on October 20, while Amazon’s later public update said all AWS services had returned to normal by 3:01 p.m. PDT. Battlefield 6 players saw disconnects, latency and wrong-region matchmaking, although EA described the game’s connection to the wider AWS incident as possible rather than conclusively proven.
As an Amazon Associate I earn from qualifying purchases.
The short answer: the October 2025 outage is over
The outage began at 11:48 p.m. PDT on October 19, 2025, and centered on AWS’s US-EAST-1 region in Northern Virginia. It caused worldwide downstream problems because many games and consumer services depended on systems running in, connecting through or managed from that region.
This was not a case of every AWS service everywhere going offline, and it did not literally take down the entire internet. However, the failure was large enough to disrupt unrelated products at the same time. Players reported login failures, matchmaking errors, disconnects, latency, inaccessible storefronts and broken account features across several major games and web services.
#1 Best Overall
- 720p resolution - View your favorite movies, shows and games in high definition.
- Alexa voice control - The Alexa Voice Remote lets you easily control your entertainment, search across apps, switch inputs, and more using just your voice. Press and hold the voice button and ask Alexa to easily find, launch, and control content, and even switch to cable.
- Access thousands of shows with Fire TV - Watch over 1.5 million streaming movies and TV episodes with access to thousands of channels, apps and Alexa skills, including Prime Video, Netflix, Hulu, HBO Max, YouTube, Apple TV+, Disney+, ESPN+, Sling TV, Paramount+, and other services right from this TV.*
- DTS Virtual-X Sound - An immersive sound format creates a three-dimensional sound experience with your TV’s speakers.
- Supports HDMI ARC - Sends audio directly from the HDMI jack to a compatible soundbar or AV receiver, removing the need for an extra cable.
AWS’s post-event summary describes three overlapping waves of impact involving DynamoDB, EC2 and Network Load Balancer. Amazon’s public recovery update later said all AWS services were normal by 3:01 p.m. PDT on October 20. Those times are not contradictory: AWS’s 2:20 p.m. endpoint refers to the customer-impacting incident described in its technical summary, while Amazon’s 3:01 p.m. statement reflects final service normalization after recovery work and throttling continued.
If you are experiencing a connection problem now, in August 2026, do not automatically blame this October 2025 incident. Check the game’s current status page, the platform status page and your own connection before troubleshooting further.
Which games and services were affected?
The outage did not affect every title in the same way. In some cases, the game servers themselves were available but players could not authenticate, join a session or reach a required backend service. A web page could also load while account features such as login, streak tracking or cloud synchronization failed.
| Service or game | Reported symptoms | Evidence and qualification |
|---|---|---|
| Fortnite | Login and matchmaking failures | Fortnite Status acknowledged an internet-wide service-provider outage and later said the issue was resolved. This is among the clearest first-party acknowledgments recorded during the incident. |
| Battlefield 6 | Disconnects, latency, server instability and players being placed in incorrect regions | EA/Battlefield communications said the problems might be connected to a broader outage outside EA’s direct control. AWS should not be presented as the conclusively proven cause of every Battlefield 6 symptom. |
| Roblox | Platform access, website functions, joining games and creator services were widely reported as unavailable or unreliable | Contemporary reporting documented widespread disruption. The current Roblox status page may no longer display the October 2025 incident in its visible history. |
| Epic Games Store | Storefront loading and login failures | Contemporary outage coverage recorded problems with the store. The Epic Games status page is the appropriate source for future incidents. |
| Wordle and NYT Games | Login and account-dependent features, including streak tracking, were affected for some users | The page could load for some players, so “Wordle was down” is too broad. The more accurate description is an access, login or account-service disruption. |
| Palworld | Multiplayer connection problems | Palworld published a notice saying its multiplayer problems caused by the global network outage had been resolved. |
| PlayStation Network, Pokémon GO, Rocket League, Clash Royale, Clash of Clans, Lost Ark, Sonic Racing: CrossWorlds and Dead by Daylight | Access, connection or service errors were reported during the incident | These titles appeared in reputable contemporaneous coverage, but the level of direct first-party confirmation varied by service and region. |
| Xbox services | Reported as unaffected during live coverage | Windows Central attributed that resilience to Microsoft Azure rather than AWS. That report should not be interpreted as proof that every Xbox game or feature was unaffected. |
| Steam | Appeared to recover or remain more functional than some affected services | Individual games could still have independent outages, even if Steam itself was operating. |
The contemporary accounts include TechRadar’s live timeline, GameSpot’s coverage, Windows Central’s report and Tom’s Guide’s live updates. Reports from outage monitors and social media are useful for identifying symptoms, but they do not prove that a particular game was completely offline worldwide.
Battlefield 6: what was confirmed?
Battlefield 6 players reported disconnects, high latency, unstable servers and matchmaking that placed players in incorrect regions. These symptoms appeared while AWS was experiencing its major US-EAST-1 disruption.
However, EA did not state that AWS definitively caused the whole Battlefield 6 incident. Its October 20 communication said the problems might be connected to a broader outage outside EA’s direct control. That distinction matters: timing and shared infrastructure make AWS a plausible contributor, but the available evidence does not establish that every Battlefield 6 disconnect, latency spike or matchmaking-region error came from AWS.
For later Battlefield 6 problems, use EA’s official server-status page, which lists Battlefield 6. Once AWS and EA report normal service, persistent wrong-region matchmaking or connection problems are more likely to require game-specific, platform-specific or local-network investigation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- 1080p Resolution - Watch movies and TV shows in high-definition picture quality.
- LED-backlit LCD screen - With reliable and long-lasting LED lighting, this LCD screen delivers a wide range of colors and contrast for a memorable viewing experience.
- Watch what you want - Stream over 1.5 million movies and TV episodes. Watch favorites with subscriptions to Netflix, Prime Video, Disney+, and more. Subscription fees may apply.
- All your entertainment in one place - Watch live and free TV, play video games, and stream music.
- Smart and always getting smarter - Fire TV adds new Alexa skills, features, smart home capabilities, and voice functionality all the time.
What happened to Fortnite, Roblox, Wordle and the Epic Games Store?
Fortnite
Fortnite’s most visible failures were login and matchmaking problems. Fortnite Status attributed the disruption to a service-provider outage, then confirmed that the issue had been resolved. That does not necessarily mean every Fortnite mode, region or feature was completely offline at every point in the incident; it means the services needed to sign in and enter matchmaking were impaired.
Epic’s official Fortnite live-issues guidance is useful for checking current problems, but reinstalling Fortnite cannot repair a provider-side authentication or matchmaking outage.
Roblox
Roblox users experienced widespread problems reaching the platform, loading the website, joining experiences and using creator-related services. Because Roblox is a platform rather than one standalone game, an infrastructure failure can appear in several different ways: the site may open while game joining fails, or players may enter an experience while account and creator functions remain unavailable.
The historical evidence supports describing Roblox as broadly disrupted during the AWS event. It does not support claiming that every Roblox experience failed in every country or that the current Roblox status page necessarily preserves the original incident details.
Wordle and NYT Games
Wordle illustrated why “down” can be misleading. Some users could load the puzzle page, but login and account-linked functions—including streak tracking—were affected. The visible content and the backend account service do not have to fail at the same time.
Epic Games Store
The Epic Games Store experienced storefront and login problems during the outage. A store outage can prevent browsing, authentication, purchases or launching account-dependent services even when installed game files remain intact. It is therefore different from a complete failure of every game installed through Epic.
What exactly failed inside AWS?
AWS’s post-event explanation identifies a latent race condition in DynamoDB’s automated DNS-management system as the initial trigger. In plain English, AWS had multiple automated processes applying DNS changes, and under an unusual timing sequence an older change eventually overwrote a newer one.
Rank #3
- 4k Ultra HD (2160p resolution): Enjoy breathtaking HDR10 4K movies and TV shows at 4 times the resolution of Full HD, and upscale your current content to Ultra HD-level picture quality.
- High Dynamic Range: Provides a wide range of color details and sharper contrast, from the brightest whites to the deepest blacks.
- All-in-one: Get right to your good stuff. With Fire TV, you can enjoy a world of entertainment from apps like Prime Video, Netflix, Disney+, Hulu, and HBO Max. Plus, stream for free with Fire TV Channels, Pluto TV, Tubi, and more. Access over 1.8 million movies and TV episodes. Subscriptions may be required. Feature and content availability may vary.
- Smart Home: Your smart home hub. Pair Fire TV with compatible smart home devices to see live camera feeds, use AirPlay, control your lighting and thermostat, and more.
- Free Content: Stream for free. Access over 1 million free movies and TV episodes from popular ad-supported streaming apps like Fire TV Channels, Tubi, and Pluto TV. Subscriptions may be required. Feature and content availability may vary.
- DynamoDB’s DNS system used multiple independent “enactors” to apply DNS plans.
- One enactor was delayed while retrying an update.
- A second enactor applied a newer DNS plan and began cleaning up older plans.
- The delayed enactor later applied its stale plan, overwriting the newer one.
- The cleanup process removed the active plan, leaving the regional DynamoDB endpoint with an empty DNS record.
- Systems trying to reach
dynamodb.us-east-1.amazonaws.comcould no longer resolve the endpoint correctly, so new connections to DynamoDB in US-EAST-1 failed.
DynamoDB was only the beginning of the wider customer impact. The failed endpoint prevented AWS systems and customer applications from establishing new database connections. That caused retries, queues and dependent service failures, which then complicated AWS’s recovery.
The secondary failures
AWS reported several cascading problems:
- EC2 droplet leases expired. EC2 uses internal leases to track resources. As the incident continued, some leases expired and had to be rebuilt.
- New EC2 launches failed. Customers saw messages such as “insufficient capacity” or “request limit exceeded,” even though the underlying problem was not necessarily a permanent shortage of physical capacity.
- Network configuration propagation accumulated a backlog. Newly launched instances initially lacked normal network connectivity while configuration work caught up.
- Network Load Balancer health checks failed. NLBs removed healthy capacity from service when checks could not complete normally, reducing the ability of applications to serve users.
- Lambda and container services were delayed. Lambda, ECS, EKS and Fargate experienced errors, backlogs, scaling problems or launch failures as their dependencies and control systems were affected.
AWS temporarily throttled EC2 launches and other impaired operations to prevent recovery traffic from overwhelming systems that were already rebuilding. It also disabled the DynamoDB DNS Planner and DNS Enactor automation worldwide while preparing fixes and additional protections.
Why did a Northern Virginia failure affect players worldwide?
The failure location and the user-impact location were different things. The triggering fault was in AWS US-EAST-1, but customers around the world could still be affected if their applications used that region directly or relied on a service whose control-plane, authentication, database, scaling or deployment functions were tied to it.
A game may run match servers in several regions and still fail to let players in if its login service, account database or matchmaking control system cannot respond. A storefront may have content delivered from a separate network but still fail when it needs to authenticate a user or retrieve account data. A company may also have servers outside Northern Virginia while depending on US-EAST-1 to launch, configure or scale them.
AWS specifically noted that customers using DynamoDB global tables could use replicas in other regions, but replication to and from the affected Virginia replica lagged during the incident. That illustrates why multi-region infrastructure is not automatically equivalent to instant failover.
Recommended Free Tools
The available public evidence does not reveal the precise redundancy design of every affected game company. It would be wrong to conclude that each company had the same architecture or that a different design would certainly have prevented its outage. The reliable general lesson is narrower: shared backend dependencies can create a common failure path for products that appear unrelated to players.
Why did services recover at different times?
Restoring the DynamoDB DNS information did not instantly repair every downstream service. AWS’s recovery unfolded in stages:
Rank #4
- REGZA Engine ZR: REGZA Engine ZR is Toshiba's revolutionary Engine. With the power of precise analyzing technology, it drives the maximum potential of picture quality to reach the resolution of 4K for scenes, to deliver stunning picture quality for breath-tak-ing viewing experience.
- AI 4K Upscaler: Toshiba's unique Al upscaling technology provides the near-4K level picture quality for Full HD content. Instead of simply replicating every pixel, it intelligently detects the colors of neighboring pixels and decides the proper color of each pixel by considering the detailed texture of the real sight. No matter what the content is, you can enjoy every scene with the amazing clarity of near-4K quality.
- Dolby Vision*Atmos: Combine Dolby Vision HDR imaging with Dolby Atmos sound to get engaging audio-visual performance, transforming your TV into an entertainment powerhouse with detailed images and acoustics, so as to achieve amazing realism that you'll see, hear, and feel like never before. That is, your truly spectacular home entertainment.
- Ultimate Motion: Ultimate Motion reduces blur in fast moving scenes, offering crisp and clear images for fast action sequences. Its smooth viewing experience puts you into the scene.
- Game Mode: Game mode supports many gaming features such as ALLM (Auto Low Latency Mode), VRR (Variable Refresh Rate) and eARC. With the combination of Ultimate Motion, breathtaking reality and excitement make your gaming experience unforgettable.
- DynamoDB endpoint information was restored. AWS restored the DNS information at approximately 2:25 a.m. PDT on October 20. As cached DNS records expired, customers began reconnecting over roughly the 2:25–2:40 a.m. PDT period.
- EC2 recovery continued. EC2 recovery began around 12:01 p.m. PDT and was complete around 1:50 p.m. PDT, after AWS rebuilt leases and processed queued work.
- Network and load-balancing systems caught up. Network propagation backlogs and failed NLB health checks had to be cleared so healthy capacity could return to service.
- Lambda and container launches recovered. Queued work and scaling operations affecting Lambda, ECS, EKS and Fargate took additional time.
- Customer applications recovered on their own schedules. Vendors had their own retry queues, caches, rate limits, authentication sessions and matchmaking systems. Those systems could remain delayed after AWS dependencies were available again.
AWS said existing EC2 instances launched before the incident generally remained healthy. The major EC2 problems concerned new launches and the subsequent network propagation needed to make those instances usable. This is another reason a player could see some online features return while new servers, matchmaking capacity or freshly scaled services remained unreliable.
Detailed incident timeline
| Event | Time |
|---|---|
| AWS incident began | October 19, 2025, 11:48 p.m. PDT |
| Gaming outage reports became prominent in TechRadar’s monitoring | About October 20, 2:30 a.m. EDT / 7:30 a.m. BST |
| DynamoDB DNS information restored | October 20, 2:25 a.m. PDT |
| Cached DNS records expired and customers began reconnecting | Approximately 2:25–2:40 a.m. PDT |
| EC2 recovery began | 12:01 p.m. PDT |
| EC2 fully recovered | 1:50 p.m. PDT |
| AWS post-event summary’s customer-impacting endpoint | 2:20 p.m. PDT |
| Amazon’s public all-services-normal update | 3:01 p.m. PDT |
The timeline comes from AWS’s technical post-event summary, Amazon’s public update and TechRadar’s contemporaneous monitoring.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat should players do during a similar outage?
First, establish whether the problem is broader than your connection
- Check the public AWS Health Dashboard. AWS says its public dashboard does not require an AWS account and shows public events across AWS regions.
- Check the game or vendor status page: Epic Games, EA and Battlefield or Roblox.
- Check the platform status page if you play through PlayStation, Xbox, Steam or another launcher.
- Compare symptoms across devices or unrelated services. If Fortnite, Roblox, a storefront and another website fail at once, a local router problem is less likely than a provider or platform incident.
What not to do while a provider outage is confirmed
Do not repeatedly reinstall the game, change DNS settings, open router ports or perform repeated factory resets when multiple unrelated services are failing at the same time. Those steps cannot repair a broken remote authentication system, database endpoint or matchmaking backend and may create additional problems.
Repeated login attempts can also add load to a recovering service. Wait for the vendor to confirm recovery and allow time for queued requests, caches, authentication systems and matchmaking capacity to catch up.
What to try after recovery is announced
- Fully close and relaunch the game and its launcher.
- Sign in again only when the service asks you to do so.
- Check login, matchmaking, purchases, cloud saves and other features separately; recovery may be partial.
- Restart your router or test another connection only if the problem affects your device or network rather than multiple services.
- If one game remains broken after AWS and the game vendor report normal service, consult that vendor’s status page before attributing the problem to AWS.
For example, persistent Battlefield 6 wrong-region matchmaking, latency or disconnects after the AWS incident should be investigated as a possible EA, platform, game-update or local-network problem. EA’s wording did not conclusively attribute every Battlefield symptom to AWS.
What this outage says about always-online gaming
The incident demonstrated the difference between a game’s visible server and its wider service dependency chain. A player may think of “the server” as the machine running a match, but modern online games often also require authentication, player accounts, databases, APIs, matchmaking, scaling systems, load balancers, content delivery, telemetry and platform services.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →That does not mean every cloud-hosted game is equally fragile, nor that multi-region deployment guarantees uninterrupted play. A service can be distributed across regions while retaining a single-region dependency for a critical control-plane or account function. Conversely, another provider or product may remain available because it uses a different cloud, architecture or failover arrangement. Windows Central’s contemporaneous report that Xbox services were unaffected is one example, but it is not evidence that every Xbox game would always avoid an AWS-related failure.
Best Value
- EXPANDED CONTRAST FOR ENHANCED VISUAL DETAIL: Get expanded contrast between the lightest and darkest parts of a scene for a wide spectrum of colors, enhanced detail and depth.
- MOTION-BASED SOUND: Feel like you're in the middle of the action with sound that follows objects on screen. Featuring a virtual top channel, every sound is precisely placed in space, placing you in the heart of the scene.
- SECURES PERSONAL DATA** WITH TRIPLE-LAYER PROTECTION: Your TV experiences are secured. Samsung Knox Security defends against harmful apps and phishing sites while keeping sensitive data, such as PINs and passwords, secure. It also safeguards your IoT devices connected to your TV.
- YOUR TV SCREEN, TAILORED TO YOU: Stream your favorite movies and shows and access your favorite apps and games on an intuitive smart TV platform* , with personal data secured by Samsung Knox.** Plus get 7 years of automatic OS updates.***
- A WORLD OF CONTENT AT YOUR FINGERTIPS. NO SUBSCRIPTION REQUIRED: Watch 2,700+ free channels including 400+ Samsung TV Plus premium channels and on free streaming apps. Enjoy national and local news, sports, movies and more. Explore new content being added regularly.
It is also important not to confuse cloud infrastructure with game-design choices. An offline or local single-player mode may continue working if its files and authentication requirements permit it, while an online mode can fail. Some games require an online account check even when the player is not joining a multiplayer match. The exact result depends on the title’s design and vendor architecture.
Bottom line
The October 19–20, 2025 AWS incident was a Northern Virginia regional failure with worldwide consequences. AWS identified a DynamoDB DNS-management race condition as the initial trigger, followed by EC2, networking, load-balancing, Lambda and container-service problems that extended recovery. Fortnite, Roblox, the Epic Games Store, Wordle and Palworld had documented or strongly reported disruptions; Battlefield 6 experienced serious connection problems that EA said might be related, but AWS was not conclusively established as the cause of every Battlefield issue.
The practical lesson is to distinguish a provider outage from a local connection problem. Check AWS and vendor status pages first, avoid destructive troubleshooting during a confirmed incident, and reassess the cause if only one game remains broken after the infrastructure and vendor services return to normal.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Is the AWS outage affecting Fortnite, Roblox or Battlefield 6 now?
No. The incident covered by this article occurred on October 19–20, 2025. As of August 2026, a new connection problem should be checked against the relevant current status pages rather than automatically attributed to that historical outage.
What caused the October 2025 AWS outage?
AWS said a race condition in the automated DNS-management system for DynamoDB created an incorrect empty DNS record for dynamodb.us-east-1.amazonaws.com. The initial DynamoDB failure then contributed to EC2, networking, load-balancer, Lambda and container-service problems.
Did AWS take down the entire internet?
No. The incident centered on AWS US-EAST-1 in Northern Virginia, not every AWS region or service worldwide. It nevertheless caused global downstream disruption because many applications depended on that region or on services affected by the cascade.
Was Battlefield 6 definitely taken down by AWS?
Not conclusively. Battlefield 6 players reported disconnects, latency, server instability and wrong-region matchmaking, and EA said the issues might be connected to a wider outage outside EA’s control. EA did not state that AWS caused every Battlefield 6 problem.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Where can I check whether AWS is currently having an outage?
Use the public AWS Health Dashboard at https://health.aws.amazon.com/health/status. It does not require an AWS account. Also check the affected game, publisher and console or PC platform status pages.
The Bottom Line
Bottom line: the October 2025 AWS outage was resolved, but it was not a simple worldwide shutdown. A DynamoDB DNS race condition in US-EAST-1 triggered a broader cascade that disrupted login, matchmaking, storefronts and backend services at different times. If a game is still failing after the provider and vendor report recovery, investigate that game, platform or local connection separately.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
