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 |
|---|---|---|
 New York City
|
Website Down | 1 day ago |
 Ciudad Jardín
|
Website Down | 26 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:
-
Nil (@slowalgorithm) reported@awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.
-
DeeDee Armstrong (@deedeeafton) reported@Gozieuk @awscloud You felt they were transparent? I got the anomaly detection email from AWS last night. Dashboard had an outrageous $$ number. Spun up devs to find out problem. And- then AWS posted a joke here on X, and still no email as a follow up to their first one. Doesn’t seem transparent
-
deibeat (@deibeat_13) reported@AWSSupport I did the same exactly, and really panicked when I saw that, thought someone got access or something. Tried to contact billing support, removed s3 bucket, turned off a personal website using it, asked Claude for guidance until I finally found it was a global issue…
-
Aramis Official (@AramisToken) reported@NoaSanderskyo7 @F1 @awscloud He was slow af, actually
-
AntDracula (@ant_dracula) reported@_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error
-
Tseng (@TsengSR) reported@marcelocantos @awscloud I'm 100% certain you'd also crying a river when hard caps are added and the same happens again, because then your services will be shut down immediately until they resolve it and you'll cry too, how they'd dare to take your services offline when reaching the cap due to an error.
-
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. 😞
-
Ben Newton ベン (@BenENewton) reported@awscloud Somewhere there's an IT guy lying on the ground next to his desk after opening the page with this error on it.
-
Ayush Awasthi (@Ayush_awa) reported@AWSSupport Its the third day today. The only mail I received from aws was all about “We are getting someone to investigate this” Since then I havent received any update. My only issue is that these things are time sensitive and you cant just take days after days with no real status updates
-
Jaden Fix (@jadenfixxx) reportedAnyone at @googlecloud or @awscloud (or a neocloud) wanting to slide into my DMs and help me rip some free credits? Possibly leading to larger contracts down the road .. I just tried signing up for an @Azure free trial, and the experience felt like what I imagine the elders went through with dial-up internet. Solutions Architects or Account Managers HMU
-
Abhi Bavishi (@abhibavishi) reportedSeems like a major glitch with @awscloud
-
David G (@MohandesDavid) reported@thewebbie @awscloud Rounding error, obviously....
-
Gabe Fletcher (@gabefletcher) reported@marcelocantos @awscloud bro... touch some ******* grass. OF COURSE IT WAS AN ERROR. WHO REALLY THINKS THEY LOOK AT THEIR AWS BILL FOR A TRILLION DOLLARS AND SAYS "OH THATS DEFINITELY REAL" stop. go **** off to some VPS's or some ****.
-
D (@D8118199174282) reported@awscloud No, you still haven’t compensated users for the cost bug error
-
Harikrishna KP (@harikp2002) reported@AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!
-
Md Jaoyad (@JaoyadCode) reported@awscloud you should fix it otherwise people will become sick after watching the bill!
-
Drate Berry (@drateberry) reportedIs anyone else experiencing issues with the @awscloud Billing system? I’m trying to add a new card and both the physical and virtual versions are throwing a verification issue. Bank is saying they don’t see anything on their end. Waiting to hear back from AWS Support.
-
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.
-
Ironluca (@Ironlucaaa) reportedHeyo again @AWSSupport, thanks for fixing the issue! My bill is only $503 now. That's much better, it's okay now!
-
Aaryan Bansal (@NotUnHackable) reported@awscloud that issue was happening since yesterday dude. why tf did it take so much time?
-
Jim Osman (@EdgeCGroup) reported@awscloud Real innovation starts with people solving real problems.
-
Nicholas Griffin (@ngriffin_uk) reported@deedeeafton @awscloud you should have enhanced your calm and raised a support issue instead.
-
Ayush Sanj (@AyushSanj) reported@taashuu_ @TeamShiksha @awscloud Looks like internal aws issue, big issue tho. Millions 🥲
-
(au)stin (@stin_reece) reported@awscloud $50,000,000,000 says this was a vibe code error
-
GiveHateAChance (@HelpingHate) reported@awscloud It's cute how the ***** indians who caused all of this are never at fault and how you dismiss what a huge error this was with an emoji.
-
devastatindave.eth (@NftCelestials) reported@awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually
-
paige s. (@PaigeSully88) reported@BenENewton @awscloud This isn’t human error. This is failed automation
-
Nikhil Raj (@nrworld121) reported@AWSSupport So you can send an alert email saying we owe you millions and create panic, but can't send a follow up that billing issues are going on. What a way to vibe code
-
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.
-
Fikri Firdaus (@fikrfird) reported@awscloud This really isn’t something to joke about. A false billing alert at this scale can cause genuine panic and even serious health consequences. Some users may have rotated credentials, shut down workloads, or deleted services because they feared their accounts had been compromised.