Is Amazon Web Services down?

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".

 No problems detected at Amazon Web Services

Amazon Web Services problems in the last 24 hours

Amazon Web Services Outage Chart

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.

Most Reported Problems:

Website Down
(65.00%)
Errors
(35.00%)

Amazon Web Services Outage Map

The most recent outage reports and issues originated from:
Fort Worth Website Down
Granada Website Down
Sydney Errors
Santiago Errors
Hermosillo Errors
Cuautitlán Izcalli Errors

Amazon Web Services Comments

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Amazon Web Services Issues Reports

Latest outage, problems and issue reports in social media:
  • sridharparida0 Sridhar Parida (@sridharparida0) reported

    @awscloud @AWSSupport @AWSCloudSEAsia Monthly payment made which is not reflecting in system and with many followup, the issue not resolved yet. Shared the transaction reference, amount of transaction, but still the issue is not resolved. Request for resolution at earliest. .

  • PaulaDPoole Paula Poole (@PaulaDPoole) reported

    @AWSSupport Please investigate it I’m glad it’s fix. I dealt with this before because of this web developer whom is a hacker. I hope this wasn’t his handy work every since I moved to @awscloud he’s been crazy angry 😒 @FBIhelpME

  • BonniBlack10 Bonni10 (@BonniBlack10) reported

    @AWSSupport Ummm no. There are still issues between AWS & @CenturyLink. Students at universities are paying for both the schools' use of AWS & their personal use of @CenturyLink but neither company is doing shit about fixing it & restoring access.

  • BonniBlack10 Bonni10 (@BonniBlack10) reported

    @awscloud @coursera Except if you have @CenturyLinkHelp @CenturyLink bc @AWSSupport refuses to fix the issue between CenturyLink ISP & AWS thereby screwing students across the country out of accessing the services they pay for.

  • zOxta zOxta ✨ (@zOxta) reported

    @themsaid @awscloud We have seen intermittent DNS resolution issues for AWS RDS endpoints yesterday as well.

  • mkennedy Michael Kennedy (@mkennedy) reported

    @ericchou @AWSSupport @AWSUpdates Thanks Eric! Yep, DNS errors were the issue for us. I bet this was it.

  • GADadOfThree Dad Of Three (@GADadOfThree) reported

    @AWSSupport Still not working in GA - can't get to either of my RDS instances. Even pinging them - works, then fails, then works, then fails...

  • rebeccac206 Rebecca Cunningham (@rebeccac206) reported

    @AWSSupport Still issues for end users at 7 AM pacific on 10/23

  • MichaelMotam Michael Mota (@MichaelMotam) reported

    @PGrandstaff @awscloud I started having problems with my S3 bucket yesterday until a few minutes ago that I was able to access it again... It seems like aws had some sort of attack, or at least that's what I see here on twitter.

  • JeroenJacobs79 Jeroen Jacobs (@JeroenJacobs79) reported

    @awscloud However, now my raid device seems to be renamed from /dev/md0 to /dev/md127. Not a big issue, since we put the block UUID in the fstab file, and not the device name.

  • JeroenJacobs79 Jeroen Jacobs (@JeroenJacobs79) reported

    @awscloud I could not replicate the issue on a CentOS machine I was running on VirtualBox. However, when I replaced "sudo mdadm --detail --scan | sudo tee -a /etc/mdadm.conf" with "sudo mdadm --detail --scan --verbose | sudo tee -a /etc/mdadm.conf", the issue disappeared.

  • hailhailclub Hail Hail (@hailhailclub) reported

    @AWSSupport Not able to login to the console either

  • hailhailclub Hail Hail (@hailhailclub) reported

    @PeterCharles_ @AWSSupport I'm also still having issues

  • hailhailclub Hail Hail (@hailhailclub) reported

    DNS still not working for me @AWSSupport

  • msplaykate MsPlaykate (@msplaykate) reported

    @AWSSupport Good morning. Not working in Oregon. Worked for an hour last night and I can login right now, but am back to seeing "cannot read bucket versioning status" when I try to open any bucket and "error loading media: file could not be played" when referencing MP3s stored on the server.

  • profitseobrizzy Profit SEO (@profitseobrizzy) reported

    @AWSSupport Not working here in Australia. DNS issues.

  • dvassallo Daniel Vassallo (@dvassallo) reported

    @themsaid @awscloud That's bizarre. I don't think SQS uses Route 53 at all. It might be an unrelated problem.

  • Spark_Spartan Sandy May (@Spark_Spartan) reported

    So two thoughts on two weeks as a @awscloud developer after three years of @Azure. YAML as deployment for infrastructure is amazing, MSFT fix this now. AWS Console is trash, not being able to resources makes 0 sense its exceptionally hard to navigate

  • zurped James Freeman (@zurped) reported

    @AWSSupport Still getting end point errors.

  • denisaugsburger Denis Augsburger (@denisaugsburger) reported

    @AWSSupport Not working yet. It can't resolve cloudfront from the aws cli. Located in Switzerland

  • LC464915667 LC4 (@LC464915667) reported

    @AWSSupport Still not working for me on 2 RDS instances

  • bay_area_res1 Craig P. (@bay_area_res1) reported

    @awscloud your s3 issues started at 10:30am PST. There was not a single post about this until 4pm. This not how a cloud provider like your should work. We are moving to @googlecloud

  • jovica jovica (@jovica) reported

    "Between 10:30 AM and 6:30 PM PDT, we experienced intermittent errors with resolution of some AWS DNS names..." @AWSSupport it's annoying that AWS doesn't use UTC.

  • EliaContini Elia Contini (@EliaContini) reported

    @AWSSupport Still not working in Switzerland

  • amrtnshu Amritanshu Kumar (@amrtnshu) reported

    Woke up this morning to #aws had a DNS outage 😲 whaat! #Amazon

  • HSchwartzberg Hanan Schwartzberg (@HSchwartzberg) reported

    @AWSSupport still not working in Greece

  • minglini Guilherme Barbosa (@minglini) reported

    @AWSSupport still not working

  • CampusSuiteHelp Campus Suite Status (@CampusSuiteHelp) reported

    Problems with Amazon AWS S3 services causing issues with Campus Suite services

  • kowlgi Sunil K. Srinivasan (@kowlgi) reported

    AWS DNS came under some kind of DDoS attack today, resulting in DNS resolution errors. 5-6 hour outage. The AWS status webpage displayed an alert, but confusingly, health indicators were green. Would help to pinpoint services affected by outage, @AWSSupport.

  • Penelopekayart Penelope Benavidez (@Penelopekayart) reported

    So @awscloud is STILL having issues so I haven't been able to get into my @Instructure @CanvasLMS all afternoon and YA'LL I GOT HOMEWORK TO DO. They aren't accurately sharing information about the outages or their possible resolutions so I'm left panicking over here

  • IvoRoperto Ivo Roperto (@IvoRoperto) reported from Grapevine, Texas

    @AWSSupport @alansbrown I have an issue. I’m trying to have my MFA remove from my AWS account without success. You guys keep asking me to provide my old address but I moved. However, I had provided passport, DL front/back with affidavit and still you guys won’t use logic and reason.

  • ESLlibrary ESL Library (@ESLlibrary) reported

    @homestarrunner_ @ItsTeacherMike Hi Matthew. I sent you a DM about this issue related to Amazon's AWS service. Please let us know if we can email you a file until they resolve the issue. We're so sorry for this inconvenience.

  • Suave_Pirate Alex Dunn 🔜 #SDC19 (@Suave_Pirate) reported

    Seems related to the @awscloud Route53/DNS issue - direct link access to S3 files seems busted. @AWSSupport

  • walidmrealtor Walid Muhammad (@walidmrealtor) reported

    Getting tons of aws errors from amazon #awsoutage

  • thescotthull spooky 👻🎃 hull (@thescotthull) reported

    @AWSSupport Must be a serious issue if downtime has been nearly 10 hours so far. Keep us posted please.

  • roblane09 ShinyLane (@roblane09) reported

    These @awscloud DNS issues are killing me!

  • matthewokeefe1 Matthew O'Keefe (@matthewokeefe1) reported

    @QuinnyPig @awscloud Every public cloud is going to have these kinds of problems at one point or the other. This is not a knock against @awscloud, it's an acknowledgement they are the big dog the dorks are targeting.

  • NerdsPwn Nerd or Die (@NerdsPwn) reported

    We're aware of an issue with certain users not being able to download some of their products. This is being caused by a rare issue with @awscloud, which they are working to resolve.

  • QuinnyPig Corey Quinn (@QuinnyPig) reported

    The current DDoS against Route 53 shores up my thesis that using multiple DNS providers for redundancy is kinda pointless. Route 53’s 100% SLA means @awscloud services build to it; thus when it goes down, all manner of their services go wonky.

  • LordoftheFrogs9 Lord of the Frogs 9000 (@LordoftheFrogs9) reported

    @MikePStreetWear Amazon Web Services (AWS) is currently experiencing a DNS outage. All services are severely impacted! ETA for fix: unknown That’s why you can’t download the episode.

  • abdielou Abdiel Aviles (@abdielou) reported

    @AWSSupport For those having issues accessing assets through direct URL, if possible, try specifying the region. Same applies if you are using the SDK.

  • python_force Radek (@python_force) reported

    This AWS outage is so bad - all the sites are down #aws #s3 #awss3 @AWSSupport

  • Awxsome Preston Allen (@Awxsome) reported

    @AWSSupport having issues hitting items in bucket using direct URL as well

  • dubey4201 Vijay Prakash dubey (@dubey4201) reported

    Aws route 53 dns issue seems to lethal. Hosted zone on route53 and S3 seems be affected the most. We have seen error on cloudfront distribution @awscloud any update on time to resolution.

  • the_databae Rachel Wigell | Databae (@the_databae) reported

    I broke production. And then the @awscloud R53 outage broke our CI in such a way that I could not release my fix for the **** issue. It's been a special day. 🙃

  • reallyunlikely (Λα:*.λx:α.x) : Πα:*.α→α (@reallyunlikely) reported

    @cchukudebelu @samlogic_ 1. I don't think sub-Saharan "Africa" is a target market for Amazon, at least until ~2030. And, AWS would come before retail. 2. Not sure Amazon has an India problem to "crack", as they've already established a $20B a year operation there.

  • alliemims alliemims (@alliemims) reported

    @awscloud going down for me at a very unfortunate time...

  • DivvyHQ DivvyHQ (@DivvyHQ) reported

    Hey Divvy-ers! Some users are experiencing issues with adding and retrieving attachments. Upon troubleshooting, we’ve been informed that Amazon S3 (where we store attachments) is having intermittent outages. Hopefully they resolve that soon. We’ll keep you posted.

  • schoonerlabs schooner labs (@schoonerlabs) reported

    @nounproject Looks like maybe an Amazon AWS issue. Tried to download the app and says site cannot be reached.

  • cdtoad cdtoad (@cdtoad) reported

    @fchristant @satish_shetty @awscloud last time S3 had an outage those green checks never changed to X... cuz the X was on S3

  • andrejacqdebeer André-Jacques de Beer (@andrejacqdebeer) reported

    @awscloud your forking shirt's broken please fix

  • enyorap Locker (@enyorap) reported

    @AWSSupport Hi, i had problem with RDS - could not translate host name "<name>" to address: Temporary failure in name resolution

  • itsdapoleece IT’S DA POLEECE (@itsdapoleece) reported

    'Amazon S3 Outage' is not an email I like to get at work

  • TheNickmaster21 Nick Main (@TheNickmaster21) reported

    Hey @AWSSupport, we are experiencing errors on S3 for some customers. Users are getting DNS errors on files in some buckets and others online are reporting issues. #AWS

  • edwinfmesa Edwin Mesa (@edwinfmesa) reported

    @awscloud please help me! RDS problem - could not translate host name "<name>" to address: Temporary failure in name resolution

  • edwinfmesa Edwin Mesa (@edwinfmesa) reported

    @AWSSupport help please, problem with RDS - could not translate host name "<name>" to address: Temporary failure in name resolution

  • StitchIsMyPatro Squeaky Kitty (@StitchIsMyPatro) reported

    @0xKruzr Lol. I'm all for cloud services, but it should be done with continuity and security in mind. A lot of companies ran to cloud without knowing implications and it's causing security issues (see customer data in unencrypted / insecure Amazon S3 buckets)

  • panodk PK (@panodk) reported

    @lucasnad27 @AWSSupport @cwrichardson @awscloud Same here, us-east-1 buckets issue and DNS timeout similar to the original poster. It's manifesting in intermittently in Lambdas as well.

  • maslowbeer Sean Stoner (@maslowbeer) reported

    @AWSSupport having issues resolving <bucket>.s3.amazonaws.com hostnames - never seen this happen before

  • IntellyvestFund Intellyvest (@IntellyvestFund) reported

    Amazon S3 seems to be having issues. All our requests are failing @Everipedia