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 (78%)
- Sign in (11%)
- Errors (11%)
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 | 24 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:
-
Donna Paulsen (@donnapaulparody) reported@VeryCoolGuy6 @awscloud Check the issues that happened in last 6 months and diagnosis/cause of the issue.
-
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
-
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.
-
Master of Controversy (@THe0GAmer) reported@Pirat_Nation Amazon aws outage knocked psn offline for 8 hours while sony pushes an all digital future fans could not launch their purchased games
-
M Si (@1210meh) reported@AWSSupport When can be fully recovered? My aws server working very slow
-
Corey Quinn (@QuinnyPig) reportedKinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.
-
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
-
kakafa.btc (@kakafa_btc) reported@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
-
hansi flick enjoyer (@sambarvadaii) reported@santhoshv @AWSSupport @awscloud I had an s3 bucket with some data in worth 2-3 mb at max. At first I thought someone hacked into my account. I raised a billing inquiry, after which I realised that this was an ongoing issue.
-
JamilOmar ( 💉💉💉🦠 💉 💉💉) (@jamilomar) reported@chuanq @awscloud same issue !!!
-
Matt Teixeira (@matt_teeixeira) reported@priyansh_ptl18 @awscloud @AWSSupport Error I'm sure?
-
Arash Sadrieh (@ArashSadrieh) reported@AWSSupport Hi @mattsgarman our whole service is down for almost 3 hours, would appreciate some help here ,eta on fix would be great
-
Zenwatts 🇺🇸 (@BullCall101) reported@awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.
-
Maurizio Santamicone (@santamm) reported@awscloud And while you fix it, you can credit us for those amounts.
-
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.
-
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.
-
GettingMyGlitchOff (@GettingMyGlitch) reported@AWSSupport Again there is a mass wave of suspensions like in May I'm assuming in error as I've been on this platform for over 10 years and this seems to be happen more frequently. Emails from mturk-noreply havent worked in a long time,any updates on this situation @amazonmturk
-
Gabriel (@doktorgphd) reported@awscloud wow really??? i had to search x for the reason?? not even an email?? I saw the email sent yesterday about the cost alert and I spend the last hour trying to work out what is going on because it looks very legit and I only find out it was an error on x! Just had to send an email!!
-
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.
-
billy (@Billy17979063) reported@fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too
-
Matthew (@OneShotCaller) reported@CalebChamberla6 It’s an AWS billing error (see @awscloud)
-
Kish_lloyd (@kish_lloyd) reported@AWSSupport Why does this feel like a stage for subscriptions hikes on other hosting providers. Previously human error was deemed the highest risk for error but if humans made AI 🤔
-
Luke Skywalker (@LSF4Life1981) reported@RinoTheBouncer Just like you can't be bothered to Google anything PSN issue was @awscloud which doesn't say anything either
-
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.
-
M (@mdw864) reported@AWSSupport Either that or ask me to login, which I keep telling you I cannot login. It has nothing to do with 2FA. That is not the issue.
-
Marek Serafin (@stoprocent) reported@DerDerDaIst @AWSSupport After they fix it, I'm setting up deny all policy.
-
* (@BunnnyRAM18) reported@amazonIN @awscloud The same issue happened twice for these product
-
J Bret Edwards (@jbecompslns) reporteddid @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.
-
metis (@metis00001) reported@AWSSupport Looks like it has been resolved. But it definitely took like 5 days to resolve a payment configuration issue! Thanks for reaching out.