Is Amazon Web Services down?
No problems detected
If you are having issues, please submit a report below.
Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".
Full Outage Map
Sign inProblems in the last 24 hours
The graph below depicts the number of Amazon Web Services reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Amazon Web Services users through our website.
-
Errors (43%)
-
Website Down (43%)
-
Sign in (14%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Los Angeles |
Website Down | |
 Greater Noida |
Errors | |
 Hamburg |
Sign in | |
| Uniontown |
Errors | |
 Birmingham |
Errors | |
| New York City |
Website Down |
Full Outage Map
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Amazon Web Services Issues Reports
Latest outage, problems and issue reports in social media:
-
Richard Barrell
(@0x2ba22e11) reported
@somecloudguy @QuinnyPig @awscloud fwiw IME DNS server (data plane) outages are pretty rare - I've used some very not-top-tier DNS services in production for years and never saw them cause an outage
-
Lohith K.S. Chalam #wearmask #fully 💉
(@lohithchalam) reported
Not good time for one more @awscloud outage
-
kgregory-chariot
(@ChariotKgregory) reported
@QuinnyPig @awscloud I think the only way this works is if your registrar is outside AWS (but with a provider that never does down) and you point your NS records into Route53. Otherwise, as others have mentioned, you can't uses aliases or any of the other tightly-integrated features of R53.
-
CAASSOO
(@CAASSOO1) reported
@21pumpstreak @CryptoSenorita @scramble_nft POW runs through the same amazon AWS like POS. Yes the job done outside centralised servers but it's rely on it just as much. There was an Internet server problem in Ukraine few months ago when majority of the country ended up without Internet for days. No one was able to use BTC
-
Matt Leib / #BLM / He/Him
(@MBLeib) reported
@CTOAdvisor @awscloud Said with the true consultancy perspective: It depends. Did the customer build their solution for Fault Tolerance? Did the provider fail? I think the issue is never quite so clear cut.
-
Look up Knuffelberen
(@poiThePoi) reported
@AWS_Snarkitect @QuinnyPig @awscloud Having worked there, I grant the SAs as a class credit for a discovery problem and was this a.... known... problem? "We're spending 8 Million/year on cross-region replication and if IAD falls over..." They're *fairly* aligned with your interests, and not totally.
-
Mark Tomlin
(@Dygear) reported
With each @awscloud outage this month (alone) @oxidecomputer becomes much more valuable as the obvious choice.
-
Jakub Kozłowski λ❄
(@kubukoz) reported
@awscloud @velvetbaldmime The whole thing is so universal I was able to implement an @akkateam HTTP server in a couple hours. Then double that to pass all tests because I had a typo I took forever to notice. I made a POC of Decline interop in 2 hours. A simple "playground" in 30 minutes.
-
LK
(@louisnk) reported
Hey @awscloud how does a single AZ going down make #lambda or #sns time out for all of us-east-1? That's 3+ hours of #failed processing from s3 uploads that we seem to have to re-trigger processing for based on logs. Thanks for the xmas gift.
-
Shawn Douglas
(@writediteach) reported
Yup, @Fidelity is down. Can log into my account, but my portfolio won't update. Meanwhile we're already 12 minutes into trading. Is this related to @awscloud being down AGAIN? Or some other issue? Not cool, Fidelity, not cool.
-
Patrick Brown
(@pb2k1) reported
I'm seeing tweets that an @awscloud data center went down. So if your web service isn't working, that's probably why. More than likely why @Fidelity's platform is down. Amazon seriously needs to fix mission critical services.
-
Teamwork
(@teamwork) reported
@GillCNiemisto @awscloud @SlackHQ Hey Gillian, this message was wrongly displaying to some customers due to the issues we've been having mitigating from the AWS outage. Apologies for the confusion there, it should be no longer visible now! - Laura.
-
Mike D
(@MikeD21003026) reported
@awscloud @WSJ 3rd outage in a week. My business with AWS will be coming to a swift end next year.
-
TrainingPeaks
(@TrainingPeaks) reported
The @awscloud server is experiencing issues that affect our site & integrations. Please do not disconnect & reconnect devices as that will not resolve the issue. Wait before taking any further action as workout files are likely still processing. We will continue to update here.
-
Alex (agh)
(@nixgeek) reported
@QuinnyPig @awscloud What’s a bit terrifying with DNS is the failure mode where Route53 keeps serving records but you can’t change. Even running on 2-3 providers, normally a good thing, if any are in this zombie state it’s a huge issue should you need to redirect traffic.
-
Market is ******
(@marketisfucked) reported
hey guys @Fidelity are you guys down? i can login and see my portfolio but trading window runs error. hope you are not on @awscloud for that **** goes down every now and then
-
Steve Mushero
(@stevemushero) reported
@ChariotKgregory @QuinnyPig @awscloud Yeah, that's the key issue; if I use APIs, dynamic features, and lots of good R53 goodies, this does not seem reasonable (though how to failover externally is also hard; maybe a mirror script/function that pushes R53 to 3rd party). Better for AWS to fix this.
-
Macher Gaming
(@Macher_Gaming) reported
@awscloud #AWS is down again?! In 2022 we’re renaming the Cloud to Fog
-
Cristob
(@cristtobal_127) reported
@QuinnyPig @AWS_Snarkitect @awscloud AWS announces OaaS: Outage as a Service
-
Rob 🍗
(@foodguyrob) reported
@McD_Truth @awscloud I work for a major distributor and every time it shuts down our entire ordering platform. Such a pain
-
Matt
(@livinginthe330) reported
@awscloud @WSJ Fix your ****!
-
David Chayer
(@david_chayer) reported
@QuinnyPig @sebastianrako @awscloud The incident today is…strange at best. It’s 2021, what Datacenter power outage isn’t mitigated by ups, generators, n+2 redundancy and a/b power feeds?
-
Matthew Phillips
(@matthewatyou) reported
from
Seattle, Washington
Currently in line to get a COVID test and @awscloud is down so now everything is manual. Three times in one month??? #awsdown
-
McD Truth
(@McD_Truth) reported
@Trubrit66 @awscloud I’m not sure, typically these outages last for half a day until a resolution is found or fixed. If it’s over a course of multiple days I assume it’s a different issue.
-
Colm MacCárthaigh
(@colmmacc) reported
@t3rabytes @QuinnyPig @awscloud I'm gonna have to re-do that whole session due to the audio clipping issues :( But that'll give me a chance to make it shorter and better.
-
Chris McKee
(@chrismckee) reported
@nixgeek @QuinnyPig @awscloud A very good point as r53 wasn't down it just wasn't modifiable. So even dual hosted DNS isn't solving that and your 86400 ttl
-
Thomas Curry
(@GlidingDev) reported
@QuinnyPig @AWS_Snarkitect @awscloud But isn't the point that since AWS internally uses R53 for everything, even if you repoint your external provider, provided the target's in AWS it'll still be down?
-
Corey Quinn
(@QuinnyPig) reported
@AWS_Snarkitect @awscloud If I can’t repoint something during an outage I may as well toss my DR plan in the trash and wait it out at the bar.
-
Mike Bolitho 📶🏜️
(@NetEngMike) reported
@CTOAdvisor @awscloud The AWS outage is a bigger deal not because of individual services or applications being impacted but because of the nature of how it breaks everything. It's more of a fundamental question of "Is this what we should be doing as an industry" vs "Is it OK that AWS had an issue".
-
Jimmy
(@RandomIgnorance) reported
You know @awscloud @amazon You'd better get things together because you are responsible for a lot of companies' servers when you have issues. Figure out what your problem is and fix it!