Amazon Web Services status: access issues and outage reports
Some problems detected
Users are reporting problems related to: website down, sign in and errors.
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.
August 2: Problems at Amazon Web Services
Amazon Web Services is having issues since 08:10 PM IST. Are you also affected? 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 |
|---|---|---|
 New York City
|
Website Down | 18 minutes ago |
 Ciudad Jardín
|
Website Down | 25 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 |
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:
-
Jayden L. (@Jwayy77) reported@awscloud Screw you aws. Not a joke, how many of us were pulled into the call to fix and understand the issue? How many of us init teardown scripts to stop all instances or remove the project? Clearly compensation is needed here. Look into it, else we’ll pack up and leave.
-
Corey Quinn (@QuinnyPig) reportedI want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”
-
Zyreon (@Zyreon_trading) reported@awscloud When i wake up i saw:there is another AWS Bug/Service Down. Lol cannot give up time of 24 hours/7 days/infinity uptime..
-
Joy | 🔥 (@JoyKingdomx) reportedAs 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.
-
Adam Peterson (@_adam_here_) reportedis @AWSSupport down?
-
DeeDee Armstrong (@deedeeafton) reported@t1097s @larunachalam @awscloud Tyler, are you an AWS actual customer, or just someone who thinks real people should “chill out” when a vendor causes actual business trouble and then jokes about it?
-
Ing. Mario Varón M.Sc (@ma_varon_col) reported@AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...
-
SwarmOne.ai (@swarmoneai) reportedOpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud
-
M (@mdw864) reported@googlecloud @GoogleCloudTech do you accommodate customers with disabilities? In case we have problems and need to speak to you? I think I may have to switch to you because @awscloud has not provided accommodations for people with disabilities.
-
CaptainAmericaTex (@CaptAmericaTx) reported@LayoffAI During the last 12 months Amazon AWS had outages directly caused by initiatives from the AI group (with associated revenue impact). No surprise they are down sizing the snake oil sales men group.
-
D (@D8118199174282) reported@AWSSupport Will the affected accounts be compensated for this issue?
-
D (@D8118199174282) reported@awscloud No, you still haven’t compensated users for the cost bug error
-
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
-
Santhosh (@santhoshv) reported@D8118199174282 @AWSSupport Many stopped services, also I never assumed health issues with billing itself
-
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.
-
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.
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)
-
Santhosh (@santhoshv) reported@PinokioSystem @AWSSupport But again health dashboard says forcast, but usage itself showing.. how come this is not explained correctly. Another point is it's the billing and money not any service down, so billing page itself could have add some alert
-
Slav (@slaviknowsbest) reportedAWS is currently showing wildly inaccurate billing data in Cost Explorer. My $20 budget suddenly jumped to $30k+ (153k% over). Official incident: 'Inaccurate Estimated Billing Data' (Global) - started yesterday. Don’t panic yet - these appear to be display errors, not actual charges. Spread the word so others don’t freak out. #AWS #AWSDown #Billing @awscloud
-
Gerzson (@Gerzsononline) reported@slap__tjips @awscloud Gosh ai haters are so ******* dumb they just assume and blame it on ai for a funny error that didn’t result in any wrong
-
Jim Osman (@EdgeCGroup) reported@awscloud Real innovation starts with people solving real problems.
-
Erin (@erinEncoded) reported@AWSSupport No follow up email sent to users to let us know not to panic after we got threshold emails. I was sick this morning and lost hours of productivity. Terrible, truly terrible, customer service. As soon as I see my account go back to 0, I’m moving to Azure.
-
Indrani Som (@indrani_som2004) reported@AWSSupport please look into this issue
-
Aaryan Bansal (@NotUnHackable) reported@awscloud that issue was happening since yesterday dude. why tf did it take so much time?
-
PositiveVibes (@KPTheFighter) reported@AWSSupport @AWS @awscloud I still did not receive any email communication which I was expecting as soon as you guys noticed the issue. Today I almost lost my life due to panic. My hands were shaking as I was told. I still can’t believe I went through this. First email - insane actual bill about Dashboard shows the same amount After panic attack, I see a note on your support page, but what would one go to your support page ? Shouldn’t it be on your billing console page ? Again, my issue is not about your mistake, it’s about how you handled the situation. And you didn’t do anything!! Not even one email to the users!! Sad and shocked at the same time!! I can’t forget what I went through today morning. 😞
-
Silksteele (@silksteele) reported@adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.
-
Har (@duckboy1909) reported@awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon
-
Ignacio Cassinelli (@igncass) reported@awscloud What a terrible response
-
Md Jaoyad (@JaoyadCode) reported@awscloud you should fix it otherwise people will become sick after watching the bill!
-
Clem ent (@clement___10) reportedSelf hosting your email server is something that Is very tricky and I still can't grasp till today. The craziest part is not the setup but managing the email server reputation. I rather pay @Cloudflare or @awscloud.