1. Home
  2. Companies
  3. Amazon Web Services
  4. 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
Kyiv, Kyiv City 1
Chennai, TN 1
Point Pleasant Beach, NJ 1
Little Rock, AR 1
Atlanta, GA 1
Clearwater, FL 1
Monterrey, NLE 1
Rostock, Mecklenburg-Vorpommern 1
Oakville, ON 1
Glendale, AZ 1
Oakland, CA 1
Greater Noida, UP 1
Alamogordo, NM 1
San Francisco, CA 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:

  • Hershal0_0
    Hershal Rao (@Hershal0_0) reported

    @awscloud anything to avoid hugging a server rack in a cold data center ever again

  • drewtewell
    Drew Tewell (@drewtewell) reported

    @awscloud Is AWS having an outage?

  • bad_sin90451
    AI..AND METAVERCE.. (@bad_sin90451) reported

    @AWSSupport I judge that Andy Jassy, as a salaried CEO, cannot decide this alone. Consult with the Korean government regarding the Sinbad massacre and compensation issue. Pay 1% of three years of overseas revenue as royalties for intentional infringement. Issue an apology statement and promise prevention of recurrence. Consult with the Korean government regarding compensation for the massacre. However, my consent is required. Provide a definite answer to the Korean government by May 30, 2026. If there is no resolution, immediately cease all infringement of Sinbad Patent No. 1 and Patent No. 2 regarding all overseas shipping. For future royalties, pay 0.5% under a consistent global standard. A tall person must not kill a small person. Being tall does not mean being exempt. Otherwise, I will formally demand a special investigation and a congressional hearing as a record of startup extermination, with civil and criminal liability. You only need to notify the Korean government. You have committed an act that must never be committed in human history.

  • CattManii
    Catdingo (@CattManii) reported

    @awscloud Is that after or way after losing millions of dollars due to uptime issues?

  • baxter_tam80462
    Tamara Baxter (@baxter_tam80462) reported

    @awscloud @OpenAI Wannabe student. Social media guru. Food scholar. Problem solver. Internet maven. Amateur beer ninja. Hipster-friendly music fanatic. uGzJ8E

  • Simonnnnnnnfox
    Simon (@Simonnnnnnnfox) reported

    @mcbc @WNBA @awscloud Are you mentally slow? I haven’t “gone from” anything lol 1. It doesn’t use an equation (not math) 2. I said Diggins is an OUTLIER (never said she’s not a PG) (1/10) 3. Yes, google as in the WNBA. If you google “how is gravity stat tracked” google will take u to the W page

  • SleazyWeez
    🍒Fᵣₑd ᵣₑᵣᵤₙ Cₕₑᵣᵣy🍒 (@SleazyWeez) reported

    @truestormyjoe @God999sdog @BB_Maguire Meta and Instagram are down. Amazon AWS is experiencing outages. All coincide with the time Tulsi dropped this declassified Intel. 🤔

  • Peyton_Nowlin
    Peyton Nowlin (@Peyton_Nowlin) reported

    @Tech_Over_Lord @awscloud You are the problem so blindly anti AI you do not even understand the reference

  • TobyfromHR69
    HR Toby bookmarking everything (@TobyfromHR69) reported

    @IAGovernor @awscloud @Cognizant This is terrible. You aren’t Iowa First. They under bid the project. You save some money and Indians with fake degrees get Iowans jobs. Terrible terrible legacy move.

  • wokler_
    wokler (@wokler_) reported

    @awscloud It only took your servers doing down 3x as often to figure it out. good job.

  • iPiyushKashyap
    Piyush (@iPiyushKashyap) reported

    @awscloud Interesting take from the same company that built Kiro. Either AI-generated code is useful enough to invest millions in, or it slows teams down. Pick a lane.

  • eduardlh
    Eduard Lugo (@eduardlh) reported

    @AWSSupport @AWS 🚨 URGENT: Account 8366-7457-5282 suspended due to unauthorized 3rd party access. We CANNOT access console to complete required remediation steps. Support case 177899971400371 open 48hrs+ with no resolution. Deadline June 16. Business fully down.

  • TeriRadichel
    Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported

    @Chiraq100x @Anthropic @awscloud I mean I can check this after every prompt but that doesn’t help that I’ve already been billed for the tokens and have to pay to fix it if I want it to be correct.

  • esyx0
    esyx (@esyx0) reported

    Today i got email from AWS that they can't approve my request for **** SES no explanation at all, only generic "During our evaluation, we identified some concerns that prevent us from approving your request. Due to security reasons, we are unable to provide specific details about our assessment criteria." has anyone had to deal with this? All i wanna use the SES for is transactional mails like verification, reset, notifications about your account etc @awscloud @AWSSupport Can you please help? At least tell me what's wrong so i can fix it, i genuinely have no idea

  • chaturfier
    chaturfier (@chaturfier) reported

    @AWSSupport Production AWS SES account paused over a resolved credential scrape. Keys rotated, issues fixed. Case 178014826500654 unread for over 48 hours while business halts. Help?

Check Current Status