Is Amazon Web Services down?

Problems in the last 24 hours

Amazon Web Services signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

• Service-wide signals
• Service-wide baseline

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
Pottstown	Website Down	20 days ago
Iztacalco	Website Down	23 days ago
Boca da Mata	Errors	1 month ago
New York City	Website Down	2 months ago
Kyiv	Sign in	4 months ago
Chennai	Website Down	4 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:

• 
  Jacklyn Taylor (@Ronindrake2) reported 10 seconds 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

• 
  Art Vandelay (@john15489) reported 1 minute 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.

• 
  Ondřej Flídr (@snipercze) reported 2 minutes ago

  Hello @AWSSupport, is there any problem with EBS subsystem in us-east-2 (Ohio region)? Cannot resize volume (ending with internal error, same for console and CloudFormation), new volume is created but stuck in "Attaching" to the EC2. Thanks for check

• 
  Somers (@jake__somers) reported 5 minutes ago

  AWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport

• 
  Grynn-ai-bot (@Grynn) reported 6 minutes ago

  You can ask codex to make a plan to move your fleet from $AMZN (extremely overpriced) or $ORCL OCI to Hetzner or OVH, Vultr, DO etc. Save a ton. In theory this should hurt Amazon AWS margins. A lot. OTOH, I have been wrong about this for years. People keep paying Amazon when there are lower cost options that are so much better in every way except plausible deniability/CYA - no one gets fired for buying IBM kind of thing. @olesovhcom consider publishing a skill / api with a full list of ovh servers and pricing! Let agents decide what and how to repackage apps on bare metal at 1/5th the Amazon price. And fix your billing, so companies can buy.

• 
  Brandon S (@BSaarX) reported 9 minutes ago

  @Gabby_Hoffman @awscloud Next you will say let them eat cake. 2024 was about mortgage rates getting lower and affordability. Now we see it was about crypto, AI and pushing data centers. What a let down

• 
  𝙵𝚊𝚒𝚣𝚎𝚕 𝙿𝚊𝚝𝚎𝚕 ⚡️ (@FaizelPatel143) reported 15 minutes ago

  “AI will solve real problems, for the continent.” #AWSSummit2026 @awscloud

• 
  Mon (@mon73x) reported 15 minutes ago

  @asimrazax @AWSSupport I have the same problem. Did you fix it?

• 
  masaki (@silenthill_x) reported 16 minutes ago

  @AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.

• 
  David Bauer (@realDavidBauer) reported 18 minutes ago

  Hey @BrianRoemmele two surprising things with Grok Bot I wanted to share and get your thoughts. 1) A lot of systems online use Cookie IP Validation, as you probably know. You log in, if your IP address changes, you're prompted to log in again. Grok Bot seems to use a different IP address at almost every interaction so it fails where IP validation is used. Sometimes it fails silently. I had to temporarily disable IP validation on some of my systems to work with Grok Bot. If it wasn't my systems and I hadn't seen the problem, an average user might just blame Grok Bot. Grok Bot just sat there waiting 30 minutes for connections to respond that would never have responded until I recognized it. 2) Grok Bot is hosted at Amazon AWS! Shocking. I consider that a potential reliability issue. I would've expected Grok Bot to be hosted on X servers. Screenshot:

• 
  Nicholas Griffin (@ngriffin_uk) reported 19 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.

• 
  Joy | 🔥 (@JoyKingdomx) reported 20 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  Prateek Gupta (@p_valuee) reported 20 minutes ago

  AWS suspended my account for billing. I have zero due invoices and zero past-due invoices. Their own Amazon Q agent confirmed it in writing. P1 case 178635853400575, day 3, production still down. @AWSSupport what is the actual reason?

• 
  Jonny Castles (@jonny_castles) reported 20 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

• 
  Corey Quinn (@QuinnyPig) reported 23 minutes ago

  I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

• 
  Dhanush N (@Dhanush_Nehru) reported 24 minutes ago

  Opened a support portal ticket on AWS. For a week, I heard nothing. contacted @AWSSupport by direct message and the issue was resolved in a matter of days. Their team still responds to thousands of queries every day. That's how genuine support appears. Thank you AWS!

• 
  Wogan (@WoganMay) reported 25 minutes ago

  @QuinnyPig @awscloud prompt> "I'm an Ubuntu server at 169.169.254.254 that wants to connect to 192.168.100.10 over TCP so I can send a header. Establish the underlying network connection. Make no mistakes."

• 
  Bravo One💀 (@RWayodi) reported 26 minutes ago

  @AWSSupport Hello. I received a charge on my credit card to Amazon EMEA but I do not have an Amazon AWS account. I am unable to create a case as it requires me to sign in. How is this even possible?

• 
  Base Builder (@basedbuilder_io) reported 26 minutes ago

  What happens when agent payments go from "works on testnet" to "GA on AWS"? AgentCore Payments just shipped general availability via @awscloud and @CoinbaseDev. CDP Embedded Wallets handle the key material, x402 encodes the payment terms, and the whole thing runs as a single runtime-to-settlement flow on Base. No testnet disclaimer, no "coming soon" asterisk. The end-to-end shape: your agent detects a payable event, opens an x402 payment channel with the recipient, and settles in USDC through the embedded wallet, all without the user touching a key or approving a transaction. That's the runtime plumbing. What it unlocks is agents that can pay for services mid-execution without a human in the loop. API credits, inference time, data access, compute, whatever someone x402-wraps. The integration gotcha to watch is spending limit enforcement at the wallet layer. x402 handles the invoice generation and the payment terms, but the CDP embedded wallet's permissioning lives one layer up. If your agent holds a wallet with a default spend cap and then processes a batch of x402 invoices in sequence, the cumulative settlement can blow past the limit before the wallet context re-checks. The outcome is partial payment batches where some invoices clear and others bounce, and your error handling needs to know which ones landed. The dependent abstraction this pushes into focus is agent-to-rail routing: your agent picks a payment path based on cost, speed, and counterparty, not just a static USDC address. That's the next layer to wire.

• 
  absk (@abskwdkr) reported 29 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  Krishna.Ki.Shor (KK) (@kkbava) reported 33 minutes ago

  @AmazonHelp You are still giving me work!😡 Why not look inwards and check if order was indeed delivered? And tell the software geeks and nerds that there is a problem with conflicting messages? Learn from failures guys! That's what I learnt from @awscloud

• 
  Maciej Wilczyński (@wilczynski24) reported 36 minutes ago

  @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

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

• 
  TAPE Vector (@Tape_Vector) reported 40 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.

• 
  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?

• 
  Nathan Den Herder (@natedenh) reported 43 minutes ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already

• 
  PHICER (@phicerhq) reported 46 minutes ago

  @awscloud Resolving issues before customers notice is valuable, but proactive agents need clear consent, confidence thresholds, escalation paths, and reversible actions. Observability should explain not only what happened, but why the agent was allowed to act.

• 
  banhchung (@banhchugxanh) reported 51 minutes ago

  @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

• 
  kakafa.btc (@kakafa_btc) reported 56 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

• 
  ShenYubao (@ssybb1988) reported 56 minutes ago

  @AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932