Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
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".
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.
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 section!
Most Reported Problems
The following are the most recent problems reported by Amazon Web Services users through our website.
- Website Down (80%)
- Sign in (10%)
- Errors (10%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Ciudad Jardín
|
Website Down | 21 days ago |
 Kyiv
|
Sign in | 2 months ago |
 Chennai
|
Website Down | 2 months ago |
 Point Pleasant Beach
|
Website Down | 2 months ago |
|
Little Rock
|
Errors | 2 months ago |
|
Atlanta
|
Website Down | 2 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:
-
Kishan (@Kishan200615) reported@AWSSupport I have filled this form and it's been a month and In between I tried to contact to support and no use , Please Resolve this issue ASAP.
-
Adam Peterson (@_adam_here_) reportedis @AWSSupport down?
-
Pratik Khasnabis ☁ (@softveda) reportedHey @AWSSupport your AWS Free Sandbox Environments launched with great hype doesn't actually start. Always gives an error code. Raised a ticket from builder support without any response so far. So much for the announcement.
-
Adam Peterson (@_adam_here_) reported@AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.
-
AntDracula (@ant_dracula) reported@BohemiaTech @awscloud Google just randomly shuts down services for no clear reason. That’s why they’re not trusted
-
Santhosh (@santhoshv) reported@D8118199174282 @AWSSupport Many stopped services, also I never assumed health issues with billing itself
-
Jack Stone (@c0XhHxvylL) reported@AWSSupport be honest, how much of this problem was due to ai and/or vibecoding
-
AntDracula (@ant_dracula) reported@kankerhoerrrrrr @marcelocantos @awscloud "skill issue" is a term only unironically used by losers and AI bots. I can take a guess at which one you are.
-
AntDracula (@ant_dracula) reported@kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.
-
Matthew (@OneShotCaller) reported@CalebChamberla6 It’s an AWS billing error (see @awscloud)
-
𝘋𝘳. 𝙈𝙞𝙘𝙝𝙖𝙚𝙡 𝙅. 𝙋𝙚𝙩͛𝙚𝙧𝙨𝙤𝙣 (@WeatherArchive) reportedSomehow, GOES19 going down wasn’t the craziest thing to happen this week. Happy bankruptcy day to those who celebrate (I.e., have an @awscloud account)
-
Ashutosh Dubey (@_virusbug_) reported@AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue.
-
Jim Osman (@EdgeCGroup) reported@awscloud Real innovation starts with people solving real problems.
-
M (@mdw864) reported@awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged
-
Sam (@samraysap) reported@awscloud @Ankushk73325131 Not surprised that H1-B Amazon is highlighting a Non-American. And they wonder why a multi trillion dollar company is having errors like charging quadrillions of dollars to their users. Hire American
-
billy (@Billy17979063) reported@fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too
-
GettingMyGlitchOff (@GettingMyGlitch) reported@AWSSupport Yeah its just getting automated responses to everyone saying "Your account will not be re-opened. We regret that we have not been able to address your concerns to your satisfaction." so can you send the mturk team a message to review the error since its more then just me its
-
J (@kankerhoerrrrrr) reported@marcelocantos @awscloud you're a moron. it was a known, and widespread issue, and they even had a notice in the health dashboard. this is a skill issue.
-
PositiveVibes (@KPTheFighter) reported@awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws
-
Ritesh Roushan (@devXritesh) reportedA good architecture starts by separating document storage, signing, identity verification, and notifications into independent services. 1. API Gateway All requests (upload, sign, download, share) pass through the API Gateway. It handles authentication, rate limiting, request validation, and routing. 2. Document Service Contracts are uploaded directly to object storage (Amazon S3/GCS/Azure Blob). Metadata such as owner, participants, document status, and version history is stored in PostgreSQL. Large files never pass through application servers. 3. Identity Verification Service Before signing, users verify their identity using email OTP, SMS OTP, OAuth, or KYC providers depending on compliance requirements. A verified identity token is issued before allowing signatures. 4. Signing Service Each signature request creates an immutable signing event. Documents are locked while applying a signature to prevent conflicts when multiple users sign simultaneously. Optimistic locking or version numbers help resolve concurrent updates. 5. Audit Log Service Every action upload, view, download, sign, reject, revoke is published to Kafka. Events are stored in an append-only audit database with timestamps, signer identity, IP address, and device information, creating a tamper-resistant audit trail. 6. Notification Service Kafka events trigger email, SMS, and push notifications asynchronously so users are notified instantly without slowing down API responses. 7. Security • Encrypt files at rest (AES-256) • TLS for data in transit • Short-lived signed URLs for downloads • RBAC for document access • Hash every signed document (SHA-256) to detect tampering • Store digital certificates securely using a KMS/HSM 8. Scalability Deploy services independently behind load balancers. Use Redis for caching document metadata and sessions. Object storage handles millions of documents, while Kafka decouples services and absorbs traffic spikes. Read replicas improve download performance, and multi-region replication ensures disaster recovery. This architecture provides secure storage, concurrent signing, legal compliance, high availability, and scales to millions of contracts worldwide.
-
Abhijit Tripathy (@AbhijitTripat13) reported@awscloud @awscloud still no response. You guys are so slow
-
Certified AI Dev (@MisterPrashant) reportedThis solution to this problem is AI traffic monetization. If you are an owner of a platform that provides some valuable data, you can put the data behind a paywall for the AI traffic by charging the bot fraction of a penny for using your content. x402 Payment Required protocol tells the bot that the content requires payment and the bot settles the transaction quickly on a stable coin at which point the content becomes accessible. This way,people running their search bots does not require subscription to 10 different services and can easily access data from anywhere at a very minimal cost and the owners of the sites also win as the traffic count to their paywalled site will generate income. This is not a concept. The framework to build this is already available in @awscloud today.
-
₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported@yellow_fellowz @awscloud @emm3122 AWS replied to me saying they’re aware of this issue
-
Aaron Spiel 📣 (@SpielAaron) reported@AWSSupport It's not estimated. To quote the horrific emails you're sending people: "The month actual cost associated with this...". And yes, maybe it's easier to laugh and realise it's an error when you're potentially being billed $1,000,000,000. But when it's $80K, it feels scarily real.
-
Toastie (@hightoastie) reported@marcelocantos @awscloud How would forfieting a chess tournament fix the problem though?
-
HijriGuessr.com (@jesusmusulmanfr) reported@AWSSupport You better fix that **** now
-
Jack Stone (@c0XhHxvylL) reported@stoprocent @AWSSupport when you owe aws 10k that's your problem when its 1 trillion it's their problem
-
Mike Webb (@themikebwebb) reported@awscloud You should be the first cloud provider to issue a billing usage reset.
-
AntDracula (@ant_dracula) reported@_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error
-
Mr. Honkitude (@Mr_Honkitude) reported@St0ner1995 @AWSSupport When you owe someone $10k, you have a serious problem. When you owe someone $110 billion, they are the one with a serious problem.