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.

• Errors (37%)
• Website Down (34%)
• Sign in (29%)

Live Outage Map

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

City	Problem Type	Report Time
Glendale	Website Down	2 days ago
Oakland	Sign in	3 days ago
Greater Noida	Errors	4 days ago
Alamogordo	Website Down	9 days ago
San Francisco	Website Down	11 days ago
Mercersburg	Sign in	12 days 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:

• 
  Ted (@Zuffnuff) reported 7 minutes ago

  @F1 @awscloud Keep trying to spin it but these cars have a physics problem. Fake race cars.

• 
  dani (@danisconverse) reported 11 minutes ago

  @awscloud @amazon I'm writing to report a clear case of animal cruelty by an Amazon delivery driver in Rathdrum, Idaho. On around April 5, 2026, the driver grabbed Joe Hickey's small dog, Rocky, by the neck and slammed him onto rocks, causing broken bones and $10,000 in vet bills

• 
  Arshad Ansari (@arshad_ans5268) reported 11 minutes ago

  @AmazonHelp @awscloud Please tell me when my problem will be solved. I have sent you all the details.

• 
  Neki (@NekiWeb3) reported 11 minutes ago

  @NBA @awscloud gravity broken as hell

• 
  Mohamed (@abusarah_tech) reported 12 minutes ago

  i’ve recently went down a rabbit hole to learn how hyperscalers / cloud providers like @awscloud, @Azure (or at least in theory) work a huge respect to all the engineers that built the abstraction behind the resource provisioning. i am still trying to wrap my head around it

• 
  Neal🅾️ (@BuddyPotts) reported 15 minutes ago

  @danorlovsky7 @awscloud @NextGenStats The defense was horrendous last year and all they added was Edmunds but lost Okereke and Flott. They cant stop the run at all, they should trade down and collect more picks and build the defense

• 
  Anoop Nair (@NairAnoopMG) reported 16 minutes ago

  @AWSSupport I understand. I have created a case and it has been unassigned and no response since 3 days. My production environment is down. Is there a way you can take this on priority and help respond on this case? Account id - 747327244951

• 
  JustAnotherEarthling *humorous/satirical* (@RobBoggs4) reported 16 minutes ago

  @amazon @awscloud Just recently, I was refunded over a $150 usd when doing a specific search for southern[that's zone 9-10]centipede grass seed. Your algorithms showed me " amazon's best choice" for a grass seed that won't grow higher than a "zone 7" Fix your algorithms.

• 
  Woods (@RyanRael16) reported 19 minutes ago

  @Midnight_Captl The irony is genuinely remarkable. Every hyperscaler on earth confirms they cannot build infrastructure fast enough. Azure supply constrained at 40% growth. Meta raising capex to $145B. Amazon AWS growing 28% with no signs of slowdown. Google Cloud up 63%. All four saying they need more chips faster than anyone can deliver them. And Nvidia is down 4%. The only rational explanation is the market is pricing in custom silicon risk. If Microsoft, Meta, and Google are all building their own chips to supplement GPU supply the fear is Nvidia's pricing power erodes over time even as demand grows. That is a legitimate long term concern dressed up as a short term sell. But in the near term supply constrained hyperscalers raising capex is the single most bullish data point for Nvidia that exists. The market will figure that out. It usually does. Just not on the same day.

• 
  Dhananjay Maurya (@dhananjaym182) reported 20 minutes ago

  @AWSSupport I have sent Aws case in private message please have look and fix the issue

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 20 minutes ago

  @HashiCorp @awscloud Unmanaged secrets in S3 is a real problem especially in fintech where you have long running services that accumulate config files, export artifacts, and database dumps over years. The hard part is not the scanning, it is what you do with the findings. Rotation pipelines and downstream dependency mapping are where most teams get stuck after discovery.

• 
  Saikumar Ade (@SaiPrinto) reported 21 minutes ago

  @AWSSupport Hi AWS Support, I had logged in for my exam, but due to a network issue it didn’t start. I was fully ready otherwise I would have rescheduled earlier. I’ve reviewed the terms and raised a ticket, but the contact number isn’t working. Please help me reschedule. This is urgent.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 25 minutes ago

  @awscloud Mean time to resolution in payments systems is where this matters most. An alert at 2am on a failed settlement run has very different urgency than a slow API endpoint. If the agent can distinguish context and prioritize accordingly, that changes what being on call actually means.

• 
  Mapharaphara🇷🇺🇷🇺 SR Tumel⭕ Elemch⭕s Makhudu (@ElemchosMaphara) reported 31 minutes ago

  @awscloud Is the rear seat killing issue fixed or Americans are liars?

• 
  Andrew Sam (@egy_pl_eagle) reported 34 minutes ago

  @WhoisNuel @awscloud that's scary cause banking are known to be stable and bug free ... also with AI we will still have a maintainability issue

• 
  Perfect Enemy (@PerfectEnemy376) reported 38 minutes ago

  @AWSSupport I sent support requests two weeks ago, but there is still no solution to my issue! My problem is being completely ignored!

• 
  Patriot, unpaid trying to save our country (@mktldr) reported 38 minutes ago

  @awscloud new gimmick 1 Their #customerservice has really gone down. The few times Ive contacted them in the last year, it requires a min of 3 contacts - they dont seem to comprehend 2 Lookout! Many agents promise $, then u give a 5/5 rating & NEVER SEE THE MONEY. FRAUD!!!

• 
  XXX (@MshenguMasia) reported 44 minutes ago

  @Mikedotcoza His offer is insulting to the RSA community. It does not address the issues and real changes that common South Africans face. Others invest, such as the Amazon AWS project and Microsoft. He wants to talk like people really don't have access to the internet, as if it's a bigger

• 
  ramar (@ramarxyz) reported 48 minutes ago

  @AWSSupport Case ID 177557061000414, production down, account on verification hold, 24h+ no response, please escalate

• 
  Mf91 (@Mf9166921324) reported 49 minutes ago

  @awscloud @thomsonreuters Is there any outage on kinesis services around 15.10 UTC in eu central 1?

• 
  Akintola Steve (@Akintola_steve) reported 50 minutes ago

  Where statelessness breaks at the infrastructure level, silently. File uploads written to local disk. The file lives on one instance. Others cannot see it. Fix, object storage like Amazon S3. In process caches with no sharing. One instance caches, another does not. Fix, centralized cache. Background jobs tied to instance memory. Jobs disappear on restart. Fix, external queue. WebSocket connections tied to one server. Broadcasts miss other clients. Fix, shared pub or sub.

• 
  Marcus V (@EudoraFenty) reported 51 minutes ago

  5. Let's start with the prediction: AMZN to $230 before June. Here's why.1. OpenAI ended Microsoft exclusivity. Moved models to Amazon AWS. That means AMZN cloud revenue gets a new AI pillar. MSFT Azure growth is now in question.2. SBUX beat estimates by 12%. Raised full-year outlook. Global demand up 4.2%. US same-store sales up 3.8%.3. KO beat estimates too. Raised earnings outlook. Revenue up 5.1%. The consumer stocks are quietly crushing it while tech sells off.4. GM raised 2026 guidance. $500 million tariff refund. Revenue beat by $1.2 billion. Auto demand is holding despite $109 oil.5. The data says: consumer is strong, cloud is shifting, and Mag 7 earnings this week will set the tone for Q2.6. My bet: Amazon earnings surprise to the upside. AWS growth accelerates with OpenAI. STX already showed AI storage demand is real. The AI infrastructure buildout is not slowing down.

• 
  Arthurite Integrated (@Arthurite_IX) reported 52 minutes ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  Sourabh Dhakad (@SourabhDhakadd) reported 52 minutes ago

  @amazon @awscloud Still not able to login due to passkey issue. Please remove passkey authentication.

• 
  Decentralized Dave (@ClassicDavid3) reported 53 minutes ago

  I'm also initiating short on $AMZN Amazon. Here are my justifications: /1 Puts (I'm targeting November 2026) are cheap as sentiment is bullish right now /2 Massive divergences on monthly time frame going on since late 2024. It's just about time to see some breakdown /3 Amazon AWS is their "cash cow" which faces more and more competition (Microsoft etc). Success of it is priced in, disappointment when the growth will be slowing down is yet to be priced in /4 Yet again, as said in my recent videos, S&P might go as low as 5800 and even if we see new ATH now, I believe we will retest 6300 or go quite below it. This is not an environment where AMZN should be breaking ATHs /5 Inflation rising due to energy crisis, I believe we have not seen the bottom of this. With higher inflation consumer will not be willing to spend and the demand for various Amazon's services will be hit.

• 
  Jordan Golson (@jlgolson) reported 54 minutes ago

  @AWSSupport This is ******* ridiculous at this point. After a half dozen back and forth emails, the guy finally says "Also, after reviewing this request, I noticed a few things were not addressed and would like to clarify these. First, I see you mentioned that you're having trouble with an AWS Builder ID and not the account management console. Please note that an AWS Builder ID complements an AWS account, but it is separate from the AWS account and its sign in credentials." NO KIDDING, THAT IS WHY I SPECIFICALLY SAID IT WAS AN AWS BUILDER ID AND WAS SEPARATE FROM MY AWS ACCOUNT AND I COULD LOG INTO MY AWS CONSOLE JUST FINE. Explain to me what to do, because it seems like you are failing to THINK BIG and that you have zero BIAS FOR ACTION, so INVENT AND SIMPLIFY so that you can EARN TRUST and if you DIVE DEEP and do better, I'll DISAGREE AND COMMIT, got it?

• 
  Manik Sharma (@manikgem37) reported 54 minutes ago

  @AWS @awscloud @amazonIN Hi, I am not able to use Marketplace models on Amazon bedrock even after having Activate Founders credit and payment methods added. Getting the 'Invalid_payment_instrument' error. Raised case too. Here is the latest one id 177678551600643. Please help!

• 
  Ibraheem Tuffaha 🥛 (@IbraheemTuffaha) reported 59 minutes ago

  when you try to buy Savings Plans yourself 🫠 @awscloud gives you Savings Plans and Reserved Instances Different types, different terms, different quantities They even give you recommendations Those recommendations go stale in days Usage shifts, workloads change, and suddenly you're either underutilized or short Under-buy and you miss the savings Over-buy and you're locked into years of commitment you don't need We've watched companies spend months on this and still get it wrong @MilkStrawAI does it automatically Scans the AWS account, figures out exactly how much commitment is needed, and buys it gradually over a week If usage shifts up or down, the system adjusts on its own Zero intervention from the client They just see the bill drop at the end of the month

• 
  Trevor Skinner (@PrometheusAIsec) reported 1 hour ago

  I’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.

• 
  CodieEditor (@CodieEditor) reported 1 hour ago

  @AWSSupport Already sent, please take a look. This problem is with only the use of Claude Opus 4.7 via Bedrock; billing of other services are working totally fine.