Amazon Web Services status: access issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Errors (41%)
• Website Down (32%)
• Sign in (27%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Benito Juarez	Errors	2 days ago
Paris 01 Louvre	Website Down	6 days ago
Neuemühle	Errors	6 days ago
Rouen	Website Down	6 days ago
Noida	Errors	7 days ago
Noida	Sign in	9 days 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:

• 
  Jake El Rey (@Jake_El_Rey) reported 5 minutes ago

  @TheNext_Step_ @NextGenStats @awscloud Don’t know but thats not the issue. If the analytics say run, then run. It doesn’t matter if you got stuffed on a sample size of one or even 10. These are probabilities, they arent guarantees. Doing things which contradict “conventional wisdom” actually makes the game better

• 
  Oceans Seven ⚓🇺🇸 (@M_Yates_Az) reported 6 minutes ago

  @Zeyroxxs @NextGenStats @awscloud No they don't. Those stats weren't based on Pitt. vs Balt. They just use the previous instances of those down/distance, etc. Therefore they include Tenn and Derrick Henry vs Jacksonville (for example).

• 
  Aaron Watershow (@TopKaiki) reported 7 minutes ago

  @ljajoo86 @awscloud You get your account shut down or you just ignoring?

• 
  Brian's Book Blog - Honest Audiobook Reviews (@brians_books) reported 10 minutes ago

  @AWSSupport Thanks! I’ve noticed it in 2-3 different sites. Figured it might be related. Will report in if I continue to have issues

• 
  Ram G (@rambabugorre) reported 10 minutes ago

  @awscloud i am having an issue. am using liggtsail, around 12 instances. i am ending up rebooting everytime bcos am not able to ssh thru ur browser terminal. happening across locations. am i missing anything?

• 
  J.C. ➐ (@rock_climber02) reported 11 minutes ago

  @NetsSzn01 @NextGenStats @awscloud The problem was they should have punted. Smart coaches would have

• 
  xXx (@NetsSzn01) reported 11 minutes ago

  @rock_climber02 @NextGenStats @awscloud Problem was they didn’t pass

• 
  just emily || re:connect (@ailim__) reported 14 minutes ago

  @AWSSupport Hey Amazon, I'm having trouble loging into my account, it asks me to reset the password using a code sent to my mail, which is totally fine, but then it asks me for the expiration date of a credit card i no longer have, some help please?

• 
  Vinicius caixista fds (@ViniciusonK) reported 19 minutes ago

  @laiaum Hostear server de minecraft na amazon aws

• 
  NFL Data Analyst | Harrison P. Kent IV (@harrisonpkent) reported 22 minutes ago

  @JerryJokeman @NextGenStats @awscloud Jivan, here is how you can tell what the Kent Analytics models suggested for any given 4th down conversion attempt: If the team successfully converted, it was recommended. If the team fails to convert, it was not recommended.

• 
  Itsmeawrestlingfan (@ThomasACriswell) reported 25 minutes ago

  @SNFonNBC @Raiders @awscloud If There was not a PI call 5 yards away from the ball with no chance to catch it. This would not have been an issue.

• 
  Harris Nghiem (@HarrisNghiem) reported 26 minutes ago

  @AWSSupport Please help! Unauthorized access to my account got us shut down! Please help immediately!!!

• 
  Kurt_from_SoCal (@Kurt_from_SoCal) reported 27 minutes ago

  @NextGenStats @awscloud Instead of running into a crowded box again, play action, slant pass to #81, 1st down.

• 
  Wayne Anderson (@DigitalSecArch) reported 31 minutes ago

  @CTOAdvisor For a counterpoint, while I think the rate of new services SHOULD slow - with @awscloud revenue growth and the internal alignment of incentives, the incentives are for continued productization of new features and entirely new services. 6+3

• 
  sergio torres (@sergiot87915231) reported 36 minutes ago

  @AWSSupport @amazon why would you allow your drivers to make @tiktok_us videos with his pants down on a Amazon van during his work schedule.? 👿👿👿

• 
  a bag of sweetness🍫🇨🇦🇺🇸🇬🇧 (@neenye_) reported 36 minutes ago

  @ossnipe @awscloud Once a year is the problem

• 
  THE NIИ LIVE ARCHIVE (@ninlive) reported 37 minutes ago

  @b_mccarthy For most of the downloads, yes. But this source is on my Amazon S3 server. Should not have a problem downloading.

• 
  Antoine Dejonckheere 💉💉💉 (@amdj90) reported 46 minutes ago

  @mcreenan @awscloud @AWSSupport I have the same a few months later ... did you figure out what was the issue? 🤔

• 
  Dan C 🇬🇧 (@DanDorsetUK) reported 46 minutes ago

  @investing_lo145 Unfortunately I have to agree, I run servers myself and when issues arise you should give out constant information and updates to users from official sources. Its not doing them any favours! It will be a problem with Amazon AWS Shield probably.

• 
  Ali Demirci (@Demireon) reported 47 minutes ago

  İt's pretty interesting that even though tech is for the most part deflationary, @awscloud costs haven't moved down as much as I thought they would have over the years. There must be other forces at play here that I am not seeing.

• 
  Binh (@binh) reported 48 minutes ago

  @RailsQuest @rails @awscloud The documentation is decent; my primary issue is that it's scattered all over the place. Once you have your environment configured how you like, ELB is nice to use. You just have to be aware that their next platform update could break a few things.

• 
  DY (@youngd241) reported 51 minutes ago

  @GummoXXX @awscloud But our mainframe never goes down. How many times do we have to watch folks who have no idea what they’re doing centralize things and watch it have issues.

• 
  Ewan Leith (@EwanToo) reported 52 minutes ago

  @AWSSupport shouldn't really charge a minimum of 3% of total spend to fix a bug in their software, e.g. "UPDATE_ROLLBACK_IN_PROGRESS" getting stuck for days. I don't know what the solution is, but paying for the product should be enough to be able to file bug reports

• 
  J.C. ➐ (@rock_climber02) reported 54 minutes ago

  @NextGenStats @awscloud @NetsSzn01 TERRIBLE decesion.....ANALytics....

• 
  Janani (@Sinceriouslyjan) reported 59 minutes ago

  Great work @AWSSupport, you have restricted my account again today without any notifications. This is the 2nd time in 10days. We have faced enough financial and client loss for a year in just 10days into this year. Your support team's response is not helpful and very slow action.

• 
  DanielSong39 (@DanielSong39) reported 60 minutes ago

  @NextGenStats @awscloud They need to fix the computer because this is clearly broken

• 
  Arpit Rajpurohit (@arpraj) reported 60 minutes ago

  @AWSSupport Hi Guys, Still nothing has happened on the issues till now. Please help in resolving this asap.

• 
  Kent Anntleemeaux (@KAnntleemeaux) reported 1 hour ago

  @NextGenStats @awscloud if 81 runs runs z out they had easy first down the defender was commited to inside **** decision to go more **** the play ran never put man motion on 4th 2 not fooling anyone

• 
  Rob Williams (@codeslubber) reported 1 hour ago

  It really was a terrible misfortune that no one competed with @awscloud cause as stewards of software development frameworks and tools they SUCK. Idiot Chime SDK doesn't work on M1, first ticket was in May, someone came on a month ago and said not a priority.

• 
  Keith Townsend (@CTOAdvisor) reported 1 hour ago

  @2Canadians @awscloud That first cup went down too quickly for me.