1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Amazon Web Services
  6. ❯
  7. Outage Map
Amazon Web Services

Amazon Web Services Outage Map

The map below depicts the most recent cities worldwide where Amazon Web Services users have reported problems and outages. If you are having an issue with Amazon Web Services, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Amazon Web Services users affected:

Less
More
Check Current Status

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

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Alamogordo, NM 1
San Francisco, CA 2
Mercersburg, PA 1
Palm Coast, FL 1
West Babylon, NY 1
Massy, Île-de-France 2
Benito Juarez, CDMX 1
Paris 01 Louvre, Île-de-France 1
Neuemühle, Hesse 1
Rouen, Normandy 1
Noida, UP 2
Sydney, NSW 1
North Liberty, IA 1
Laguna Woods, CA 1
Boca Raton, FL 1
Evansville, IN 1
Bengaluru, KA 1
Dover, NH 1
Daytona Beach, FL 1
Oklahoma City, OK 1
Hudson, NH 1
Maricopa, AZ 1
Reston, VA 1
Phoenix, AZ 1
Wheaton, IL 1
Santa Maria, CA 1
Trenton, NJ 1
Jonesboro, GA 1
Fortín de las Flores, VER 1
Seneca Falls, NY 1
Check Current Status

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:

  • distributeai
    distribute.ai (@distributeai) reported

    aws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.

  • DecentCloud_org
    Decent Cloud (@DecentCloud_org) reported

    @AWSSupport @Mn9or_ User: cannot create a support case. AWS: create a support case. Problem solved - for AWS.

  • manikgem37
    Manik Sharma (@manikgem37) reported

    @AWS @awscloud @amazonIN Hi, I am not able to use Marketplace models on Amazon bedrock even after having Activate Founders credit and payment methods added. Getting the 'Invalid_payment_instrument' error. Raised case too. Here is the latest one id 177678551600643. Please help!

  • JLSports24
    Joe Sutphin (@JLSports24) reported

    @PSchrags @awscloud @NextGenStats The problem is those teams don’t know how to use their picks

  • mohdemraan
    Mohammad Imran (@mohdemraan) reported

    @AWSSupport This is not about account suspension. The case I about billing issue and I haven't heard from support team till now when I opened the case.

  • ar_sanmiguel
    Adrian SanMiguel (@ar_sanmiguel) reported

    @ranman @QuinnyPig @awscloud Yeah, well. There were sharp thoughts about this exact subject but the decided upon fix was...double down on moar official engagement. It ain't exactly working.

  • namzylll
    N (@namzylll) reported

    Ignoring the Middle East when it comes to servers is a huge oversight. ALOT of players are stuck with 130+ ping. FIX THEM!!!! @FortniteStatus @awscloud @FortniteME #fortniteriyadh

  • eldar737394
    eldar (@eldar737394) reported

    @AWSSupport I need urgent help with Case ID: 177378404200042. I have been waiting for 3 days for a refund request ($67.90) but no human response yet. I am a student and this charge is a huge issue for me. Please escalate this. #AWSSupport #AWS

  • canadabreaches
    canadianbreaches (@canadabreaches) reported

    BREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.

  • PsudoMike
    PsudoMike 🇨🇦 (@PsudoMike) reported

    @HashiCorp @awscloud Unmanaged secrets in S3 is a real problem especially in fintech where you have long running services that accumulate config files, export artifacts, and database dumps over years. The hard part is not the scanning, it is what you do with the findings. Rotation pipelines and downstream dependency mapping are where most teams get stuck after discovery.

  • Petielvr
    Queen of hearts (@Petielvr) reported

    @AWSSupport Hello, this is acct. #26672735262. I cannot pay my bill because I get a 404 error. I have been trying to escalate this issue since Friday the 17th. Please have a human call Donna @ 3148223232

  • kag_land
    dr_land (@kag_land) reported

    I remember getting a write up at @awscloud for warning the African immigrants I was working with that there are still street lamp towns in rural areas of West Virginia. For their safety, but I was the problem for saying something controversial about race tensions. Oh well.

  • rehanahmediam
    Rehan Ahmed (@rehanahmediam) reported

    @awscloud one of our client is facing critical business impacting issue from the past 16 hours and tried their best to reach out to AWS support however we were not able yo receive any response yet, they have their account suspended and no support has been offered yet. Kindly chat

  • MRTECHFIXES
    MetroTec Incorporated (@MRTECHFIXES) reported

    The schema for AWS host names needs greater device. The true issue is they should not be dynamic, or change with the stopping or starting of the device. Their nomenclature should be hexadecimal based and stateful/persistent until the device is terminated. @awscloud @AWS_Gov

  • DjTimbao
    Ronny A. (@DjTimbao) reported

    @AWSSupport The issue is that the team is NOT responding via the case. It’s been 3 days for this one and 8 days for the previous one. I am totally blocked. Can you at least escalate Case ID 177654556500245 to the Billing and account team? 'Working via the case' is currently impossible Thanks

Check Current Status