Amazon Web Services status: access issues and outage reports

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

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Website Down (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Township of Evan	Sign in	1 day ago
Pottstown	Website Down	6 days ago
Iztacalco	Website Down	9 days ago
Boca da Mata	Errors	21 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month ago

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:

• 
  Art Vandelay (@john15489) reported 2 minutes ago

  @amazon @awscloud @nvidia I need an actual customer service phone number so I can actually speak to a ******* rep regarding 4 orders now. Your email help system is broken.

• 
  Vinit Upadhyay (@vinitcodes) reported 4 minutes ago

  @kirodotdev @awscloud @AWSSupport issues still persist i didn't got any update

• 
  EJ Campbell (@ejc3) reported 6 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  mark seery (@140ismymax) reported 10 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI #AI

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 13 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Nandkishor (@devops_nk) reported 18 minutes ago

  Infosys DevOps Engineer L2 Round (Offline) My friend got these questions in the L2 interview: 1. What does the top command show in Linux, and what does load average represent? 2. What is the difference between Amazon S3 and EBS? 3. What is Amazon EC2, and can we use a custom OS/image with an EC2 instance? 4. What is the difference between self-managed PostgreSQL and Amazon RDS for PostgreSQL? 5. What are Primary Keys and Foreign Keys, and why are they used? 6. Can S3 data be automatically deleted based on a policy? How do S3 Lifecycle Policies work? 7. How would you install Nginx or Apache on Ubuntu? 8. What is sudo, and why do we use it in Linux? 9. What is the difference between Prometheus and Grafana? 10. How does Prometheus collect/scrape metrics? 11. How do you manage Docker images, containers, and running processes from the CLI? 12. Where is a Bearer Token normally passed in an HTTP request? 13. Do you use any third-party monitoring tools in your production environment? If yes, which one? 14. How would you design a standardized Jenkins pipeline for multiple teams? 15. How would you create reusable Jenkins templates and shared libraries? 16. How would you troubleshoot an intermittently failing Jenkins pipeline? 17. How would you integrate Maven into a CI/CD pipeline? 18. How would you manage builds involving Node.js, Python, or Go? 19. How would you troubleshoot a failed production deployment from Jenkins? 20. How would you investigate a Kubernetes workload with high CPU or memory usage? 21. How would you use cloud monitoring and logs to isolate an infrastructure issue? Save this if you're preparing for a DevOps Engineer interview.

• 
  Pixi Dust (@Bethco2257) reported 19 minutes ago

  @FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.

• 
  Stephen “The Yellow Dart” Schutt (@schuttsm) reported 22 minutes ago

  @QuinnyPig @awscloud I get charged $0.55 every month. Fix that

• 
  Arian van Putten (@ProgrammerDude) reported 23 minutes ago

  @QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?

• 
  Dhananjay (@DhananjayKhark2) reported 23 minutes ago

  @AWSSupport Case open since Aug 13 — 15 days, no fix! AWS Glue blocked with AccessDeniedException (account-level) in ap-south-1. NOT an IAM issue. Needs backend account verification sync. Case: 178661799100381 Please escalate! 🙏 #AWS #AWSGlue @awscloud @AWSCloudIndia

• 
  Haresh Kukkreja (@HandbrakeHarry) reported 29 minutes ago

  @amazonIN @awscloud Your app seems to be down. Unable to contact Customer Support

• 
  Rohit Dhawan (@rohitdhawan26) reported 29 minutes ago

  @AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.

• 
  Amanda (@AMyrick1989) reported 29 minutes ago

  @krassenstein @Tesla Be careful. All these at the same time makes me think they are hacked, I’m fairly certain Amazon AWS was hacked that day when everything when down, given my Grok we hacked and no one ever gave explanation. I’m no expert but ya know, all these signs are pointing to this. Also, the Obamas helped produce a movie where someone hacked our satellites and alluded to it being the Middle East and all the teslas went haywire and self drive themselves to pile up on all the freeways. I wish I remembered the name however I made note of this terrifying movie given Obama clearly knows things we don’t. Just sayin, these incidents aren’t scattered. I would not be driving that ***** if I were you.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 31 minutes ago

  @AWSSupport @AWSSupport Day 6. Production down. Same templated reply on Twitter, in the case, everywhere. If a multi-day production outage doesn't qualify for real escalation, what does? Asking someone with authority to review Case 178738643800497 and respond with an actual ETA.

• 
  kakafa.btc (@kakafa_btc) reported 32 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  Mr Sage (@GreatSage_0x) reported 34 minutes ago

  Custos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 38 minutes ago

  🚨 @AWSSupport I've been unable to create a Kiro subscription for 2+ weeks, getting error"account is not authorized to make this call." I have an active account, valid billing, and correct IAM Identity Center Organization instance setup. Case #178567212700620 escalate urgently.

• 
  Nicholas Griffin (@ngriffin_uk) reported 40 minutes ago

  @QuinnyPig @awscloud that’s real? it looks like someone who doesnt know how to prompt made a sign in screen and didnt look at it.

• 
  Kenton Parton (@kenton_parton) reported 41 minutes ago

  Anyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?

• 
  Alvaro Villalba (@alvarovillalbap) reported 41 minutes ago

  @philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?

• 
  X anonyn (@OmrX304) reported 44 minutes ago

  @AWSSupport @RahulMatta1994 @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks!

• 
  Sumedh More (@DroidBoyJr) reported 46 minutes ago

  Hey @awscloud @AWSSupport im trying Bedrock with root user and getting NOT_AUTHORISED error with 400. Tried support and the ai assistant couldn't find anything. Tried raising ticket, it asked me to upgrade support plan. Plan upgrade failing with error. Going nowhere #SOS

• 
  The Trading Guy (@thetradingguy_) reported 48 minutes ago

  @AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?

• 
  Quoc Huy (@q_huy_ngo) reported 49 minutes ago

  @Cloudflare @awscloud mine transacted with Cloudflare about 700M times because of a broken DO alarm 🥲 no users, just a dev app, then a $655.83 bill. i fixed it and opened case 02252354 a month ago. still no billing decision and now i’m downgraded. can someone pls help? i really can’t afford this

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 49 minutes ago

  @AWSSupport I tried every possible combination to get phone support. I think it either just doesn't exist or it is down. Someone did get back to me in chat in another ticket tho.

• 
  mail box (@mailbox28564784) reported 52 minutes ago

  @amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l

• 
  Brian Porter (@kbporter) reported 53 minutes ago

  @amazon @awscloud @AmazonHelp why do I have to continually contact you on social media for issues with your service? Why is your customer service online “help” so bad? $5 credits for delayed orders for a service we pay for is horrible!

• 
  Hannan (@truehannan) reported 55 minutes ago

  @AWSSupport Why AWS console is not opening? Its soo much slow even my internet and everything is fine. I used VPN too but nothing worked

• 
  Chris (@Mcatbeast) reported 55 minutes ago

  @awscloud has to have the worst sign-in page EVER. Every time I try to login as an IAM user it’s a complete headache and takes 30 minutes to figure out

• 
  Jaimin Vaghani (@jaiminvaghani) reported 56 minutes ago

  @AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.