Refresh
Are things getting better? For most site, it seems the Amazon Web Services issues are being resolved, but a few standouts remain troubled. Netflix users are still reporting massive outages, and the situation is improving slowly. We’re also seeing reports from Twitch users that the streaming service is having problems, and those could also be related to AWS woes (isn’t everything?).
To see the extent of the problem with the AWS outtage, you only need to look at the Down Detector reports for Netflix, which hosts a good bit of its infrastructure on AWS, and it’s down report graph looks nearly identical to that of AWS itself.
A new AWS update from Amazon:
“We have continued to reduce throttles for EC2 instance launches in the US-EAST-1 Region and we continue to make progress toward pre-event levels in all Availability Zones (AZs). AWS services such as ECS and Glue, which rely on EC2 instance launches will recover as the successful instance launch rate improves. We see full recovery for Lambda invocations and are working through the backlog of queued events which we expect to be full processed in approximately in the next two hours. We will provide another update by 2:30 PM PDT.”
As you can see above, there are still a massive number of reports of service outages across AWS, though the situation is slowly improving.
So far, the last update from Amazon on its services reads as follows:
“Service recovery across all AWS services continues to improve. We continue to reduce throttles for new EC2 Instance launches in the US-EAST-1 Region that were put in place to help mitigate impact. Lambda invocation errors have fully recovered and function errors continue to improve. We have scaled up the rate of polling SQS queues via Lambda Event Source Mappings to pre-event levels. We will provide another update by 1:45 PM PDT.”
All of which is to say, they’re working on it, and things are progressing slowly but surely.
Amazon’s own site is still showing a banner at the top of the page that reads:
“We’re sorry if you’re currently experiencing issues using the Amazon site. We’re working to fix this as quickly as possible.“
Though all of the typical functionality such as searching, adding to cart, checking out, and video previews all seem to be working properly for me at this time. My colleague Jacob Krol mentioned his Orders page was loading slowly, though this is still an improvement over not loading at all as was the case earlier.
Many services appear fully restored, others are still down
Important players like Snapchat, Amazon, Reddit, and Netflix appear to be working properly at this time, though some users may still be partially affected on a few outliers like Ring, and Ancestry.com is still fully unavailable at this time.
We’re expecting another AWS service health update shortly – hopefully we see a full restoration sooner rather than later.
Latest update from Amazon Web Services dashboard
Hi everyone, Marcus Mears III (TechRadar’s Computing Reviews and Buying Guides Editor) here to keep coverage rolling on the AWS outage that continues to impact countless users.
Now, a new update from the Amazon Web Services dashboard about 15 minutes ago states: “We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT.”
In other words, the situation is improving but some of us will still be affected by bogged down performance and connection issues at this time. Another update is expected in under an hour from now – we’ll keep you posted.
Reports on DownDetector appear to be dropping steadily from the highest peak of 9,666 at 1:15PM EST, and the severity tag on the AWS dashboard now shows “Impacted” rather than “Degraded” with 30 AWS services fully resolved and 107 still impacted.
Reddit users know how this dog feels
Reddit is no longer having as many problems as during its peak earlier today, but thousands are still reporting buggy behavior in the app on Downdetector – and we’re finding it to be temperamental, too.
While the app works fine sometimes, at others it won’t reload fresh stories – and pelts us with the “sorry, please try again later” error message above. Fittingly, on this occasion, it also coincided with a photo of a very sad dog.
As you can see below, Reddit is aware that it isn’t yet fully fixed, with its status dashboard reporting “elevated errors”, despite a fix being rolled out earlier. So we can expect to see more error messages (and sad dogs) on Reddit for a few more hours at least…
A quiet Monday for Hinge fans
Dozens of apps and websites have been hit by today’s AWS nightmare – you can read full list here – but the latest to adds its name to that list is Hinge.
Yes, it’s going to be a very quiet day on the popular dating app, if more people get the error message above. Right now on Downdetector, over 600 people are reporting issues with the app in the US, with over 350 people in the UK also unable start matching.
Still, at least you can blame Amazon Web Services for the tumbleweed this time rather than worrying about your profile…
Will there be compensation?
Today’s AWS outage has hit over 1,000 businesses – and the impacts are going to be felt for days, even if it does look like a recovery is (slowly) materializing.
So will those businesses get fully compensated? Legal experts aren’t so sure. Ryan Gracey, technology lawyer and partner at law firm Gordons, told us: “AWS customers typically operate under standardized service level agreements, which define uptime commitments and remedies for service failures like today’s outage. While AWS offers service credits for downtime, these are often nominal and do not compensate for losses such as reputational harm or lost revenue. Ultimately, customers will be left with limited recourse,” he said.
Commenting on the UK impact, Henna Elahi (Senior Associate at Grosvenor Law) agreed that getting compensation will be complex, particularly when it comes to impacts like reputational damage. “The impacts on Lloyds Bank, for example, could have very serious implications for the end user. Key payments and transfers that are being made may fail and this could lead to far reaching issues for a user such as causing breaches of contracts, failure to complete purchases and failure to provide security information,” she said.
“This may very well lead to customer complaints and attempts to recover any loss caused by the outage from the business,” she added.
A fix on the horizon?
The Amazon Web Services dashboard isn’t exactly written for the layman, but we’ve at least got another promising-sounding update.
At 10.38am PT / 1.38pm ET / 6.38pm BST, a new post stated that “our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region”.
Translation: AWS servers are now slightly less broken and there are some positive signs inside the epicenter of today’s internet earthquake, the US-EAST-1 Region. The post goes on to say that AWS is applying fixes to the rest of the data centers, after which “we expect launch errors and network connectivity issues to subside”.
There’s no estimate for a timescale, but we might just have a light at the end of this very long tunnel…
AWS issues have hit a new peak
Earlier today, it looked like the AWS issues had hit their peak when a post on its status dashboard said the “underlying DNS issue has been fully mitigated and most AWS Service operations are succeeding normally now”.
Unfortunately, that wasn’t the case. Amazon hasn’t yet revealed a full cause of the issues, though it has released a fairly vague statement saying that “some customers still continue to experience increased error rates with AWS services”.
That’s a slight understatement, looking at Downdetector. With over 9,300 reports in the US at the time of writing, the ripples are going to be felt for many hours yet. Still, at least Wordle’s back…
How much is this costing?
It’s hard to comprehend exactly how much money an outage like today’s can cost global businesses, but Tenscope has had a crack at putting it into hard numbers.
The headline guesstimate is that $75 million per hour is being lost every hour that major websites remain offline, with Amazon accounting for much (around $72 million) of those losses. That will particularly be the case right now, with reports of issues with Amazon.com spiking.
The analysis goes on to break down much it might be costing for each of the major sites hit today:
- Amazon: $72,831,050 per hour
- Snapchat: $611,986 per hour
- Zoom: $532,580 per hour
- Roblox: $411,187 per hour
- Fortnite: $399,543 per hour
- Canva: $342,466 per hour
- Slack: $194,064 per hour
- Reddit: $148,402 per hour
Naturally, insurance will likely kick in for many cases – but, as always, that isn’t always straightforward.
Ryan Griffin, US cyber practice leader at McGill and Partners told us: “For major businesses, hours of cloud downtime translate to millions in lost productivity and revenue. Yet many policies don’t trigger unless an outage lasts eight hours or more,” he said.
“We’re seeing a gap between operational exposure and insurance response and it’s the same pattern that emerged after CrowdStrike. The market is experimenting with parametric options, but adoption remains low,” he added.
Amazon’s own store hasn’t escaped from The Great AWS Outage of 2025, of course – and a big spike in reports on Downdetector shows that the shopping giant is now one of the worst hit by the problems.
Over on Downdetector, the reports are currently at over 12,000 in the SS – not far off its earlier peak at 3.50am ET / 8.50am BST. The outages are intermittent, but are but still pretty serious and also affecting Alexa.
On the plus side, Amazon.com is showing many people a photo of various dogs, including Hunter (above), on its “something went wrong” error page. While dog photos are always welcome in any crisis, many shoppers would likely still prefer the option on continuing with their impulse buys…
Students and schools have been hit, too
While today’s AWS nightmare has largely been an inconvenience for many, it’s had more serious impacts elsewhere – notably on businesses, but also schools and students.
Many college and K-12 students use Canvas by Instructure(above) to access their course materials and assignments, but the learning platform has been seriously hit by the AWS outage – as you can see below at its status page.
The Canvas outage first spiked at around 2.30am ET / 7.30am BST, before hitting a more sustained peak in reports at 10am ET / 3pm BST. TechRadar staff know students affected by the issues, which are continuing to be reported by thousands on Downdetector.
At 12.31pm ET / 5.31pm BST, Canvas engineers said they were “still working to resolve the ongoing outage affecting Canvas, Mastery Connect, and other Instructure products”, though there’s currently no estimated time for the fix.
Venmo, Alexa and Reddit are now spiking
In today’s not particularly fun merry-go-round of AWS-related outages, the latest spikes in the US are with Venmo, Reddit, Alexa and Pinterest – with Snapchat rumbling away in the background, as it has been for over nine hours now.
The grid above from Downdetector shows you the reason why. In between all of those services, AWS (Amazon Web Services) is spiking higher than at any point in the day so far. It’s the foundation for all of those services and countless others – so when it catches a cold, much of the internet sneezes.
It looked like Reddit had largely recovered earlier and both the homepage and app are working okay for us. But the Reddit Status pageis still showing “elevated errors” and over 4,000 people are now reporting problems with the app (56% of reports) and website (33% of people).
Strap in, folks – this one is going to run a while yet…
Pinterest is completely down
It’s been an apocalyptic day on the internet – just as one app or service seemingly recovers from the AWS flu, another one goes down to replace it.
This time’s Pinterest, which is completely down right now – go to the homepage and you’ll be greeted by an error message reading “upstream connect error or disconnect/reset before headers. reset reason: overflow”. Not quite as appealing as it’s usual homepage.
Strangely, the Pinterest Status dashboard hasn’t got the memo, and is currently not reporting any issues. Either a quick recovery is coming, or that will change very soon…
This doesn’t look good…
After some promising updates earlier, it seems that Amazon Web Services has taken a turn for the worse – and that’s continuing to cause knock-on effects for several services, with Venmo and Pinterest the latest to join the party.
As you can see above, reports of AWS issues are spiking again on Downdetector – in fact, those numbers are now higher than the peak earlier today at 3.52am ET / 8.52am BST. At the time of writing, the number of reports stands at over 6,700 in the US, a long way above its typical weekday baseline.
Those issues are hinted at in a number of updates on the AWS dashboard. The latest one, at 8.43am PDT / 11.43am ET / 4.43am BST, says “we have narrowed down the source of the network connectivity issues that impacted AWS Services. The root cause is an underlying internal subystem responsible for monitoring the health of our network load balancers. We are throttling requests for new EC2 instance launches to aid recovery and actively working on mitigations”.
While “narrowed down” is promising language, the throttling of requests for new EC2 instances (in other words, new virtual servers to to take the place of troubled ones) probably explains the rise in issues we’re seeing on AWS, and anything that uses its cloud computing services. Which, as we’ve seen today, is much of the internet…
Now Venmo is down
It’s only been a few days since Venmo and Paypal were both down in a fairly sizable outage, and now the former is again seeing a huge spike on Downdetector – presumably again due to the AWS outage.
At the time of writing, over 5,700 people have reported problems with the payment platform on Downdetector. A significant number (42%) are saying they can’t log into the app, while 52% have reported app problems in general.
The Venmo Support account on X is responding to users having issues, but is simply asking them to contact the support team on the Venmo site. Let’s hope this one is resolved as quickly as the outage on October 16, which only lasted a couple of hours…
Tidal is back – or is it?
Tidal appeared to be back in business earlier, but we’re now seeing another big spike in issues.
Many on social media are reporting problems with the app, and that’s been reflected on Downdetector. Over 1,000 people in the US are saying they have streaming and login issues with the Spotify rival, which is bad news for those who were looking for a nice soundtrack to get them through this very turbulent Monday.
This could be related to a rather worrying spike for Amazon Web Services on Downdetector, which has been joined by an update about “significant API errors” on the AWS dashboard.
How rare is today’s outage?
While the scale of today’s AWS-related issues are unusual, with over 1,000 businesses hit by the knock-on effects, it certainly isn’t unprecedented.
Steve Sandford (Partner – Digital Forensics and Incident Response at data protection consultants CyXcel), told us: “While AWS outages are relatively rare, they are not unprecedented. Historical data shows that major outages occur several times a year, often concentrated in high-traffic regions like US-EAST-1”.
“There is no clear evidence that the frequency is increasing, but the impact is growing due to the expanding reliance on cloud infrastructure. This vulnerability is compounded by the fact that the cloud market is dominated by a select few players – with AWS and Microsoft Azure commanding the largest share across the world outside China,” he added.
Questions about this over-reliance on a few players will be asked after today, but easy answers won’t be forthcoming – after all, only a handful of companies can provide this infrastructure on this kind of global scale.
AWS is making slow progress
The latest update from the AWS dashboard is that the engineers have “applied multiple mitigations across multiple Availability Zones (AZs) in US-EAST-1”, which is the region hit by the problems.
While that sounds good, the update adds that AWS is “still experiencing elevated errors for new EC2 instance launches” and that it is “rate limiting new instance launches to aid recovery”.
In other words, the ‘instances’ (or virtual servers) that have been spun up to replace the problematic ones are still hitting problems, so Amazon is throttling them to prevent its platform from being overwhelmed.
We’ll have to see what impact this has, but it’s likely to mean further issues for many apps and websites that rely on AWS – and as we’ve seen today, there’s a lot of those. AWS says it’ll provide another update at 7.30am PDT / 10.30am ET / 3.30pm BST.
Wordle has log-in issues
We may have spoken too soon about Wordle being fixed earlier – some fresh issues with the New York Times’ gaming site are causing problems for some, and those are being reflected on Downdetector.
As some users (below) have reported, logins for NYT Games appear to be impacted – and that’s backed up on Downdetector, where 73% of the reported issues are about logins.
There’s been no official update from the New York Times yet, but those with lengthy streaks to protect will be hoping it gets fixed soon.
@NYTGames are your servers down? I have a games subscription but am not able to login and view my wordle/connections/strands streaks or even the archiveOctober 20, 2025
Chime and Starbucks on the rise
Two services that have gone a little under the radar during today’s AWS outage, but are now spiking considerably, are Chime and Starbucks.
The good news if you use Chime’s mobile banking is that it’s now marked as “all systems operational” on its status page, despite previously reporting a “third party outage”. The dashboard now says, “this incident has been resolved”, so that Downdetector graph should (in theory) start coming down soon.
Equally serious for coffee lovers, though, is that the Starbucks app has also been, shall we say, burnt by today’s AWS issues. Right now on Downdetector, over 1,500 people are reporting that they can’t use the app to pre-order their drinks or get reward points – and that’s something we’ve also discovered (below).
For a Monday morning, that’s incredibly harsh news – but that Downdetector graph is now at least moving in the right direction…
Ouch – more than 1,000 companies hit today
Time for a little context on the enormous scale of today’s AWS outage. Downdetector has told the BBC that the total number of reports on issues has risen to over 6.5 million, with more than 1,000 companies hit. That will have some serious financial repercussions.
In the UK, where reports have been particularly high due to timezones, the site has apparently received over 800,000 reports, which is five times the number it usually sees on the average weekday.
In terms of scale, the closest thing I can remember to this AWS earthquake is the great Crowdstrike outage of 2024, which was estimated to have caused upwards of $5 billion in damages. Let’s hope those AWS engineers can work through that backlog of issues sharpish…
Snapchat is still struggling
Snapchat has been, in pure numbers on Downdetector, one of the worst hit by today’s big AWS outage. At 3.44am ET / 8.44am BST, it hit over 22,000 reports in the US on Downdetector (and over 7,000 reports in the UK).
Thousands of users were hit by the error message “Due to repeated failed attempts or other unusual activity, your access to Snapchat is temporarily disabled. Please try again.”
While it’s now working fine for some of us on TechRadar, others are reporting that they can’t even log into the app. There also appears to have been another spike in problems according to Downdetector (below).
It’s now back up to over 8,000 reports in the US, suggesting the issues could run for a little while yet. There’s been no official comment from Snapchat, but I’ll update this liveblog as soon as there is.
Ring problems are spiking again
Now that Reddit is fixed, Ring appears to have taken the baton and started spiking again on Downdetector – it’s now at almost 4,000 reports in the US and 2,600 in the UK, one of its biggest outages this year.
There’s been no official response or update from Ring on social media, but it’s probably fair to say the Amazon-owned security company has caught the same AWS flu as dozens of other services today.
The app still isn’t working for us, showing a “connection error” with a message saying it “couldn’t load our locations”. That’s a problem for the many who now rely on Ring doorbells and security cameras for safety. AWS, meanwhile, says it’s continuing “to work to fully restore” the services that much of the internet relies on…
All is well again – Reddit is back
Monitoring: A fix has been implemented and we are monitoring the results. https://t.co/5frljn4BPMOctober 20, 2025
It’s been a hard enough morning for us all without Reddit also going down, but fortunately the self-style “heart of the internet” appears to be back to full health.
It’s now working for us in web browsers and the app has spring back into life. This is also reflected on Downdetector where reports have dropped to well under 1,000 in the US and UK, from a peak of 12,000 in the US at 6.12am ET / 11.12am BST (a time which will henceforth be marked with a minute’s silence).
The Reddit Status account on X (below) has also said that “a fix has been implemented and we are monitoring the results”. Now we just need engineers to fix the likes of Ring, which is spiking again – alongside (gasp) the Starbucks app…
An update from AWS
There’s been a slightly less confident-sounding update from the AWS dashboard on today’s outage.
At 4.08am PDT / 7.08am ET / 12.08pm BST, a new post says “we are continuing to work towards full recovery for EC2 launch errors, which may manifest as an Insufficient Capacity Error”. It adds that “additionally, we continue to work toward mitigation for elevated polling delays for Lambda”.
EC2 is short for Elastic Compute Cloud, which provides virtual servers (otherwise known as ‘instances’) in the cloud for running apps and hosting data. That’ll explain why so many apps, like Snapchat, are continuing to report issues. Similarly, Lambda hosts a service’s source code, only running it when there’s a request made for it.
In short, we can expect the impact of this to run for a little while longer…
Reddit is behaving very strangely
Reddit is turning into one of the major casualties of the big AWS outage – not only is the website down, the app is also doing some very strange things (in between not working for us at all).
TechRadar Managing Editor Matt Bolton says the most unusual part is that that it keeps popping up messages saying it’s rate-limiting him for increasingly long periods. Rate-limiting is something services do if they think they’re being DDoS attacked – they see an abnormally high number of requests coming from one device or IP address, so they create a big delay in how often that device is allowed to access their servers.
We’re guessing this means the Reddit app is struggling to connect to the service due to the outage, and is making lots of calls to the service in an attempts to fix it, and Reddit is viewing its own app as malicious actor. That would also explain why the app is struggling to find subreddits like Sonos (above).
Still, white the homepage is down for us, we have been able to get to posts by Googling a term with Reddit results, which at least means the website is still working behind the error messages…
Investigating: We’re experiencing an elevated level of errors and are currently looking into the issue. https://t.co/6IyHu46clbOctober 20, 2025
Duolingo streaks are at risk
Among the apps hit by the AWS outage is Duolingo, and Senior Staff Writer Hamish Hector is worried this outage could end his longrunning streak if it goes on for too long.
The slight silver lining is he can continue his lessons with offline mode, and if the outage does end soon his offline learning should count towards his once-a-day target to keep growing his lessons counter.
With possible causes being investigated, it sounds like the outage might not last too much longer – and unlike Reddit, Duolingo’s outage graph is fortunately now trending in the right direction on Downdetector…
One of the worst Reddit outages for a while
So, what’s the state of play in The Great AWS Outage of 2025?
While many services appear to be recovering, with Downdetector graphs moving in the right direction (including Snapchat, Ring and AWS itself), Reddit is bucking the trend by continuing to spike upwards.
The homepage is now completely down for me in the web browsers (showing a “too many requests” error) and the mobile app similarly borked showing a “your request has been rate limited”.
A Reddit post on X says “we’re experiencing an elevated level of errors and are currently looking into the issue”. There’s no comment on a cause, but it must be AWS-related surely…
Any signs of a cyber attack?
Internet outages on the scale of today’s AWS one usually spark concerns about cyber attacks. But once again, a more boring, infrastructure-related issue appears to be to blame.
The Amazon Web Services dashboard says that “the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1”, which in simpler terms means a problem between the ‘domain name servers’ (which translate IP addresses) and the interface that sits between clients and servers (APIs).
As Rafe Pilling (Director of Threat Intelligence, Sophos) commented: “When anything like this happens the concern that it’s a cyber incident is understandable. AWS has a far reaching and intricate footprint, so any issue can cause a major upset. In this case it looks like it is an IT issue on the database side and they will be working to remedy it as an absolute priority.”
That appears to be the case, with the AWS dashboard stating “we continue to observe recovery across most of the affected AWS Services”. Many sites and services, like Reddit and Ring, do continue to experience major issues.
Good news, everyone – Wordle is back!
If you’ve been worrying about getting your daily Wordle fix, then fret no more – because the mega-popular online word game is back.
The site, which lives on the New York Times‘ gaming site, was hit by the AWS outage earlier today, with users unable to log in. So, while they could complete the day’s game, it wouldn’t count towards their streak – a feature which is of vital importance to many Wordlers.
Everything appears to be working normally again now, though, so you can go ahead and attempt today’s puzzle. Just be sure to you check out our Wordle today page for hints and discussion of the game first.
Disaster, now Reddit’s down
The place we all go for refuge when there’s a big internet blackout is sadly also been hit by the AWS storm – now Reddit is showing large spikes on Downdetector.
I’m getting a “too many requests” error on the homepage and so are thousands of others, with over 6,000 reports in the US and over 3,000 in the UK.
In fact, the Reddit graph is bucking the trend of other services, which are showing a downturn in problems, whereas Reddit’s continues to spike upwards. Signs of a different problem? It’s more likely to be Reddit’s core audience waking up to today’s bad news…
The worst may be behind us…
That promising update from AWS (below) is reflected on the Downdetector graph for Amazon Web Services, which is the epicenter of today’s internet earthquake.
At is peak in the US at 3.52am ET / 8.52am BST, the AWS graph had almost 6,000 reports in the US and 4,000 in the UK. But that’s now down to around 2,000 and 1,500 reports respectively, suggesting that those “significant signs of recovery” are being felt in the real world.
Similarly, Downdetector graphs for other services are also showing a dip, which means the end of this major outage could be in sight…
Strava hits the AWS wall
Fitness app Strava is also experiencing server issues. Strava users might be seeing the following message: “The Strava server has encountered an error. Please contact support if the problem persists.” Unfortunately, as Strava runs on AWS servers, contacting support won’t do very much at all.
Matt Evans, TechRadar’s Senior Fitness & Wearables editor, says: “I can still look through my timeline, view my profile, and interact with friends’ posts, but the app is a little sluggish: 500 errors frequently occur when refreshing pages, and my latest activity, logged on my Garmin watch, hasn’t uploaded to Strava.
“Coincidentally, Garmin Connect also runs on AWS servers, but loading and navigating the app, I haven’t seen any problems so far. It’s hardly critical infrastructure like banks, but concerned athletes should rest assured that this isn’t an issue on Strava’s end.”
‘Significant signs of recovery’
Some good news, potentially – Amazon Web Services has just provided another promising update.
Its latest post, from 2.27am PT / 5.27am ET / 10.27am BST, says: “We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information”.
My takeaway from that (and the evidence on Downdetector) is that we’re past the worst of the earthquake, but aftershocks and problems could still continue for a while yet…
Tidal is out – Monday morning playlists ruined
Ugh, when your favorite music streaming service is out for the count any way you want it (that’s the way you need it) on a Monday morning.
Becky Scarrott, TechRadar’s audio editor, reports: “I’m TechRadar’s audio editor and the time of writing, Downdetector‘s list of Tidal outage reports has tipped 337 entries, with 63% listing app issues (which makes sense, because that’s how most people access music on the fly – ie. their commute), 15% noting the website isn’t letting them in (it isn’t for me) and 22% mentioning the server connection.
“I initially got the wheel of death on the app, then a crash. And when I tried to click back into the Tidal app, a ‘504 Gateway Time-out’ message appeared, after I was prompted to log in.
This is of course related to AWS’s “operational issues”, and let me tell you, my operational issues are also affected when I can’t get my Monday morning playlist going…”
We may have a cause
An update on the AWS Dashboard at 2.01am PDT / 5.01am ET / 10.01am BST may have given us some good news.
It says “we have identified a potential root cause for error rates for the DynamoDB APIs in the US-EAST-1 Region”.
Leaving the technical details aside, the most important part is that AWS says it’s “working on multiple parallel paths to accelerate recovery”.
AWS has promised another update by 2:45am PDT / 5.45am ET / 10.45am BST. Until then, expect to see a lot more error messages on your favorite services…
Ring owners are very confused right now
The AWS outage has rippled far and wide across the internet, but some of the biggest hit have been Amazon’s own services like Alexa and Ring.
For many, Ring cameras have become intertwined with their daily schedule – and that’s now been massively disrupted today, as TechRadar’s Senior Writer AI told me.
“Every morning I go for a coffee before work, taking the dog a walk around the block before sitting at my desk for the day. Normally, my smartphone gets bombarded with Ring doorbell notifications from the busy neighbors moving in and out, as I pay close attention to the app waiting for the postman.
“Today, however, until I realized that AWS services were down I just sat confused as to why the normal morning ruckus of the school run wasn’t happening. I work with headphones on and rely on Ring to know when to open the door for the postie before my dog gets alerted by their presence.
“With Ring struggling this morning, I’m going to have to stay ultra aware as I wait for the knock on my door, fully accepting that my tiny French Bulldog is going to go crazy at the thought of an intruder.
“Millions of people rely on Ring for security and safety concerns, while others just need the video doorbell for simplifying life and knowing when mail has been delivered. My Ring doorbell is one of the best tech purchases I’ve ever made, and that’s only emphasized when it stops working and I can’t go about my day the way I usually would”, he said.
Who is affected?
The easier question for today’s AWS outage might be ‘who hasn’t been hit’?
Right now on Downdetector, we’re seeing large spikes on dozens of services. On the more serious side, this includes Zoom, Slack, Blink Security, Venmo and, in the UK, Lloyds Bank, Halifax, HM Revenue & Customs, Bank of Scotland and more.
But the AWS earthquake is also rippling through Snapchat, Roblox, Fortnite, Duolingo, PlayStations Network and yes, even Wordle.
Even Downdetector is showing a rare red banner showing the severity of the Amazon Web Services outage in the US-East-1 region. We should get another update on the AWS Dashboard soon…
Your bank may also be hit
While the problems with our Echo devices this morning are annoying, a more serious repercussion from the AWS outage for many will be that multiple banks have been hit.
In the UK, Downdetector is showing large spikes on Lloyds, Halifasx Bank of Scotland and even HM Revenue & Customs. It just shows how deep and wide the Amazon Web Services infrastructure is, and how badly the internet is affected when it runs into rare problems.
The latest from the AWS dashboard at 1.26am PDT / 9.26am BST is that “significant error rates” are happening in the ‘US-EAST-1 Region’ and that “engineers were immediately engaged and are actively working on both mitigating the issue, and fully understanding the root cause”. Let’s hope they do that sooner rather than later…
This explains those Alexa issues
While it’s unlikely to be the most serious issue today, the first time many saw the impact of the Amazon Web Services outage was with its Alexa voice assistant.
This Reddit thread shows many were recently reporting problems with the assistant, with some saying they “had to turn the lights off manually” and couldn’t set their alarms.
Well, AWS is the root cause – and Alexa is far from the only service experiencing problems. Alongside Ring, Snapchat and Zoom, we’re also seeing banking apps like Lloyds and Halifax in the UK and Robinhood in the US showing large spikes on Downdetector…
This is an online earthquake
The Amazon Web Services (AWS) outage started at around 7.40am BST, according to Downdetector – and the ripple effect has taken out much of the internet.
Right now, Alexa, Snapchat, Ring, Roblox, Fortnite, Zero, Signal, Canva and countless others are showing huge spikes in reports on Downdetector.
The problems show just how many services rely on Amazon’s cloud computing services. The AWS Health Dashboard is showing an “operational issue” in North Virginia that’s producing “increased error rates and latencies”. This is going to have serious repercussions today for millions…