But it seems the problems have been resolved now
If you tried to hop on your favorite fighting game earlier today only to find you couldn’t play online, you were not alone.
A multitude of online services including some fighting games were seemingly impacted by an Amazon outage.
Arc System Works and SNK were among those hit with the issues, but thankfully, they appear to be resolved now.
Guilty Gear Strive was confirmed as a title specifically impacted that prevented the use of network features in the game with ArcSys confirming earlier that these had been fixed.
Notice: Network Features Restored
We have confirmed that all network features of GUILTY GEAR -STRIVE- are now functioning normally.
We sincerely apologize for the inconvenience this issue has caused.#GGST #GuiltyGearStrive https://t.co/MVV74g1qKZ
— GUILTY GEAR OFFICIAL (@GUILTYGEAR_PR) October 20, 2025
SNK didn’t state which games were taken down by the outage, but it sounds like there were multiple likely including Fatal Fury: City of the Wolves.
Although the developers didn’t say the Amazon Web Services outage was the cause, the timing appears to match up perfectly.
Other fighting games that use their own servers and services like Street Fighter 6 were seemingly fine.
【Notice】
We have confirmed that the restrictions to our online services caused by a network issue earlier today have been resolved, and services are now operating normally.
We sincerely apologize for any inconvenience caused and appreciate your patience. Please continue… https://t.co/JWnbq4cGKr
— SNK GLOBAL (@SNKPofficial) October 21, 2025
The Amazon outage reached far beyond just fighting games as well with multiple other games, apps and services reporting problems today too.
Those included the likes of Fortnite, Roblox, Snapchap, Ring, Amazon, Zoom, Signal and more.
According to Amazon, these issues were ultimately resolved by 3:53 p.m. PT today, so everything should be back to normal now.
This just goes to show how brittle our online infrastructure can be when just one major provider has problems like this.
You can find the final update from Amazon below.
“Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary.”