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 (80%)
• Errors (20%)

Live Outage Map

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

City	Problem Type	Report Time
Iztacalco	Website Down	2 days ago
Boca da Mata	Errors	13 days ago
Township of Evan	Website Down	28 days ago
New York City	Website Down	1 month ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	3 months 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:

• 
  OneTradeWex (@OneTradeWex) reported 5 minutes ago

  $CBRS is trying to challenge $NVDA indirectly, here’s how: While $NVDA focuses on incredibly small and powerful chips, $CBRS has built a massive, highly specialized AI scaling semiconductor. This greatly decreases the amount of cloud tokens needed to process a large language model, effectively saving AI companies millions of dollars in the long run. Think of $NVDA racks as an industrial kitchen and $CBRS chips as a microwave, when all you need to do is cook a hot pocket you want the microwave for efficiency. $CBRS announced that core revenue more than doubled year-over-year to $210 million in its Q2 earnings report while its cloud business nearly quadrupled. The company also raised its 2026 revenue guidance to between $880 million and $890 million. If $CBRS can successfully fulfill their contracts with @OpenAI and @awscloud on time and at scale we will see even more growth, if not them only having two primary customers will be their down fall. Looking at the technical setup we see $CBRS is coming down into its months long support channel. If it holds the $180-$160 level I see no reason for it not to bounce back to $215 to $230.

• 
  Mahadev Vyavahare (@mahadevkv) reported 6 minutes ago

  @SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud

• 
  Siya (@reze_xqc) reported 7 minutes ago

  @AWSSupport @AWSSupport @awscloud Case 178653274100402, 4 days old. Got a copy-paste "noted for awareness" reply, no actual fix. Still locked out of AWS Builder ID, still can't access AWS Academy courses. This is blocking coursework. Fix it.

• 
  Synapse Brief (@Synapse_Brief) reported 7 minutes ago

  @yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.

• 
  Vinit Upadhyay (@vinitcodes) reported 10 minutes ago

  @AWSSupport @kirodotdev @awscloud I’ve already raised a case explaining the entire issue. Case ID: 178664512400070. Unfortunately, I still haven’t received any genuine help, which is really disappointing. I’m not the only one facing this issue-many others are experiencing the same problem. Please look into this.

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

  @QuinnyPig @awscloud Are they gonna fix logging me out and then redirecting to the root console login? Are they gonna fix having links shareable and login to the right account? **** is such a **** show idk why I even cope

• 
  X anonyn (@OmrX304) reported 14 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!

• 
  Christian Nonis (@christiannonis) reported 16 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  Quoc Huy (@q_huy_ngo) reported 18 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

• 
  Hannan (@truehannan) reported 21 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

• 
  Aqib Ansari (@Aqib_Ansari_) reported 22 minutes ago

  @AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience

• 
  Jacklyn Taylor (@Ronindrake2) reported 22 minutes ago

  @awscloud hey, got a simple question When your moderation refuses to post a review of a book, can you do everyone a favor and instead of saying "one of these things" Say "here is the specific part that violates our guidelines. Pls fix it" It would be, so much more helpful

• 
  Chris (@Mcatbeast) reported 22 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

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 23 minutes ago

  @MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).

• 
  Ohm Patel (@Techieohm) reported 28 minutes ago

  “Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”

• 
  Adel Bucetta (@adelbucetta) reported 34 minutes ago

  @Deeen_Codes @awscloud @devpost the real unlock here isn't just solving the hackathon prompt but figuring out what problems to automate first

• 
  Jaimin Vaghani (@jaiminvaghani) reported 35 minutes ago

  @AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.

• 
  Amanda (@AMyrick1989) reported 39 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.

• 
  Zenwatts 🇺🇸 (@BullCall101) reported 43 minutes ago

  @awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 45 minutes ago

  @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

• 
  Siddartha DevOps (@SiddarthaDevops) reported 47 minutes ago

  @AWSSupport link is not working

• 
  Alvaro Villalba (@alvarovillalbap) reported 48 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?

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

  @QuinnyPig @awscloud Are they gonna fix people needing to know what region their orgs IAM identity center is deployed in order to set up cli login? (How the heck would an employee know this??)

• 
  Mr Sage (@GreatSage_0x) reported 51 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

• 
  Ranbir Mahapatra (@ranbirnxt) reported 52 minutes ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  Sumedh More (@DroidBoyJr) reported 53 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

• 
  Ümit Kaan Usta (@umitkaanusta) reported 53 minutes ago

  @AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1

• 
  X anonyn (@OmrX304) reported 56 minutes ago

  @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

• 
  John Darin Holloway (@bofkentucky) reported 57 minutes ago

  @QuinnyPig @awscloud Hopefully better than the "new" broken elastic beanstalk console experience.

• 
  TAPE Vector (@Tape_Vector) reported 59 minutes ago

  JPP-KY $5284.TW is not an AI chip company. It makes the precision metal infrastructure that surrounds the chips, power systems and cooling hardware inside modern AI servers. That distinction matters. JPP Holding designs and manufactures precision metal mechanical parts, enclosures, cabinets and structural components. Its products are used across: AI server racks Server chassis Power supply housings Battery backup unit enclosures Liquid cooling components CDU and manifold structures Telecom equipment Aerospace avionics Aircraft structural and cabin parts Medical equipment Industrial systems The company is headquartered through a Cayman holding structure and listed in Taiwan, but much of the manufacturing engine sits in Thailand through Jinpao Precision Industry. That Thailand base is important. JPP is positioning itself between Taiwanese and global technology customers that increasingly want manufacturing capacity outside China. The operating model is high mix precision manufacturing rather than mass production of one standardized component. A customer brings JPP a mechanical design or performance requirement. JPP can then handle several steps internally: Engineering and design support Metal cutting Stamping CNC machining Sheet metal forming Welding Surface treatment Painting Assembly Inspection Final integration That means the company can take a customer from drawing to finished enclosure instead of supplying only one small step. For AI servers, this can include the physical rack or chassis holding compute hardware, power equipment and cooling systems. For aerospace, it can include avionics housings, structural parts and cabin components that require much tighter certification and process control. This combination is unusual. AI infrastructure gives JPP growth. Aerospace gives it another technically demanding end market with different cycles. The company describes this model as a mix of European engineering capability and Thai manufacturing. The phrase used by management has been: French brain. Thai heart. That comes from the European aerospace companies JPP acquired and integrated with its Thailand manufacturing base. The aerospace side matters because the qualification barriers are much higher than ordinary sheet metal fabrication. JPP has Nadcap certified processes and has worked within the European aerospace supply chain. Company materials and industry reporting have referenced customers and programs connected to Airbus, Thales and Safran. Those relationships do not automatically mean every JPP aerospace product goes directly into those companies. But they show that the manufacturing system has passed qualification standards far above normal commodity metal fabrication. Then AI arrived. This has changed the financial profile of the company very quickly. FY2024 revenue was approximately NT$2.39 billion. FY2025 revenue jumped to about NT$3.73 billion. That is roughly 56% growth. Net income reached approximately NT$618 million. EPS reached NT$12.05. Gross margin stayed around 37.8%. That margin is one of the numbers I find most interesting. JPP did not double its business by becoming a low margin commodity manufacturer. The company expanded rapidly while keeping gross margin in the high 30% range. That suggests the current product mix still carries meaningful engineering and manufacturing value. Q1 2026 continued the trend. Revenue reached approximately NT$1.17 billion. That was about 45% higher year over year. Gross margin remained around 37.5%. So the 2025 acceleration did not immediately reverse once the calendar changed. This is now a real operating ramp. The AI server side has become the main growth engine. JPP manufactures server racks, chassis, power enclosures and increasingly components associated with liquid cooling. That last category matters. AI servers are becoming more difficult to cool. Higher power GPUs produce more heat. More compute density means more thermal load inside each rack. That is pushing the data center industry toward larger cooling distribution systems, manifolds, cold plates and liquid cooling infrastructure. JPP does not manufacture the GPU or the cooling technology itself. It manufactures some of the metal structures and precision components that allow those systems to be installed inside the rack. That places the company several layers beneath the visible AI names. $NVDA and $AMD create demand for increasingly powerful accelerators. Those accelerators require more complex server systems. $DELL and $SMCI integrate servers and racks around those accelerators. $VRT and $ETN operate in the power and cooling infrastructure around the data center. JPP sits further inside the physical manufacturing chain. It produces some of the metal cabinets, chassis, housings and structural components required by this infrastructure. These are ecosystem comparisons. They are not all disclosed customer relationships. The most interesting potential US connection is the company's major cloud customer. Management commentary and Taiwan reporting have repeatedly described a major US cloud service provider as one of JPP's largest AI customers. That customer has widely been reported as Amazon AWS. If correct, that creates an indirect connection to $AMZN. But I would keep the wording disciplined. JPP has not provided enough English primary disclosure for me to treat the identity and exact revenue contribution as completely settled. The important hard fact is that a major US CSP has become a very large customer. Recent commentary has indicated that this customer may account for roughly 30% of revenue during parts of the AI ramp. That is both the opportunity and the risk. A customer that large can transform a small supplier. It can also transform the income statement in the opposite direction if orders slow. Another major relationship is in Thailand. JPP has been expanding production around a large power and server customer widely identified as Delta Electronics Thailand. That customer makes power supplies, thermal systems, data center equipment and related electronics. The geographical relationship matters because both companies operate major production facilities in Thailand. Shorter logistics. Faster delivery. Closer engineering cooperation. Just in time production. Dedicated manufacturing capacity. Those factors can make a supplier harder to replace once a large program is running. But they also deepen customer concentration. JPP is effectively investing ahead of these customers. The company has been adding production capacity in Thailand. One important bottleneck has been painting and surface treatment. JPP is expanding automated paint capacity. It is also investing in larger stamping capacity and dedicated production areas for AI server and power related products. The logic is simple. More AI server racks require more metal structures. More power density requires more sophisticated power housings. Liquid cooling adds additional structural parts. If JPP remains qualified inside those programs, each generation of AI infrastructure can increase the content opportunity per rack. That is the bull side. The risk is that the company adds capacity for demand that later slows. AI infrastructure spending is strong now. It will not grow in a straight line forever. A hyperscaler can change server architecture. An ODM can move a program. A customer can dual source. A competitor can cut price. If one large customer represents 25% to 30% or more of revenue, those decisions matter immediately. That is why I want the exact customer concentration table from the latest annual report. The aerospace business gives JPP some diversification. Before the AI acceleration, aerospace represented a much larger part of the company. That business went through a difficult period around the pandemic and the following aerospace supply chain disruption. It has been recovering. The company has continued obtaining certifications and expanding its European aerospace capabilities. That creates a useful second engine. AI server demand is fast and capital intensive. Aerospace is slower, qualification heavy and built around longer product cycles. The two businesses have different risks. Together they can potentially produce a more balanced manufacturing platform. But right now AI is clearly driving the growth rate. The financial question from here is not whether revenue can grow. It already has. The question is whether the current margins survive the next stage of scale. High 30% gross margins are strong for a precision metal manufacturer. I want to know how much of that comes from: AI server racks Power enclosures Liquid cooling components Aerospace Specialty low volume work New customer programs I also want the operating cash flow behind the reported earnings. Fast manufacturing growth consumes working capital. More orders require more raw material. More capacity requires more equipment. More inventory sits between production and customer delivery. Receivables rise. So a company can report excellent earnings while cash is being absorbed into expansion. That is not automatically bad. But the return on that capital has to remain high. JPP ended 2025 with roughly NT$7.4 billion in assets and around NT$3.7 billion in equity. The balance sheet does not currently look distressed. There is no obvious heavy dilution story. The primary capital allocation issue is expansion. Paint lines. Stamping equipment. Factory capacity. Dedicated customer production. Those investments are being made because demand already exists. Now they need to earn acceptable returns. For US market context, I see several useful layers. $NVDA and $AMD are demand drivers. More accelerator shipments can mean more server racks, more power density and more cooling hardware. $DELL and $SMCI represent the server integration layer. They assemble computing systems around GPUs, networking, storage and power. $VRT and $ETN represent the data center power and thermal infrastructure layer. $ANET sits in the networking layer connecting increasingly large AI clusters. $AMZN is relevant because AWS is widely reported as the major US CSP associated with JPP's AI server business. Again, I would treat that specific customer identity as reported rather than fully disclosed until the primary customer note confirms it. The aerospace familiarity is different. $BA is the obvious US listed aerospace reference. JPP is not primarily a Boeing supplier story. Its known aerospace footprint is more European. But the same qualification logic applies. Aircraft components require traceability, process control and long certification cycles. That experience can strengthen the overall manufacturing discipline of the company even when the fastest growth is coming from AI infrastructure. This is what makes $5284.TW more interesting than a generic sheet metal company. The metal itself is not scarce. The capability stack can be. A customer needs a supplier that can: Meet tolerances. Pass qualification. Build tooling. Handle design changes. Scale capacity. Deliver consistently. Maintain surface quality. Control welding and assembly. Locate production close to the customer. And do it without disrupting a multibillion dollar server or aerospace program. That creates switching friction. It does not create an unbreakable moat. Large customers still have enormous negotiating power. The company remains small relative to the customers it serves. That means the power relationship still favors the customer. The current strengths are clear. 2025 revenue grew about 56%. EPS reached NT$12.05. Gross margin remained near 38%. Q1 2026 revenue grew another 45%. AI server exposure is already producing real revenue. Liquid cooling adds another content opportunity. Thailand capacity is expanding. Aerospace is recovering. The balance sheet is supporting expansion without obvious distressed financing. The risks are also clear. Customer concentration is high. The largest AI programs are project driven. Formal long term volume commitments are not well disclosed. The company is investing heavily into capacity during an AI spending boom. Margins could compress as volume rises. Aerospace recovery could stall. And the current growth rate depends heavily on continued data center capital spending. For me, the next proof is not another monthly revenue record. I want to see: Exact top customer concentration. How much revenue now comes from AI server products. How much comes from liquid cooling. Whether the major CSP relationship is widening into additional products. Whether the large Thai power customer is gaining share of revenue. Utilization of the new painting and stamping capacity. Operating cash flow after expansion capex. Return on invested capital from the Thailand buildout. Aerospace revenue and margin recovery. Whether gross margin can remain above the mid 30% range as the company scales. Real manufacturing. Real AI infrastructure exposure. Real earnings growth. Real high margin execution so far. But also real concentration risk. jpp-KY $5284.TW does not need to invent the next GPU. It needs to remain the qualified company manufacturing the physical structures around the companies that do. If AI racks become larger, hotter and more complex while JPP keeps winning more content per system, the opportunity can grow much faster than the underlying server unit count. The question now is whether that position is durable enough to survive the inevitable cooling of the AI capital spending cycle. That is what I want to understand next. My investing journal, not financial advice.