Is Amazon Cognito Down? Check the current Amazon Cognito status

Amazon Cognito is operational

Updated

Amazon Cognito not working for you?

Monitoring AWS since May 2020. Learn more

1 incident in 2025

Current AWS official ongoing incidents

No incidents reported in AWS's status page

IsDown pulls data from AWS's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.

Amazon Cognito issues reported by users in the last 24 hours

This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.

Latest user comments about Amazon Cognito problems

  • F

    Frank

    3 months ago

    TooManyRequests error on us-east-1

  • S

    Shaya

    3 months ago

    Userpool in US-EAST-1 region is returning 400s

  • M

    MUKTA

    3 months ago

    Not abke to login in my all systems as we se cognito auth for login

  • C

    Charlie

    3 months ago

    Logging into any app with Cognito in us-east-1 is not possible - returning "TooManyRequestsException: Too many requests"

  • A

    Anshuman

    3 months ago

    Not able to sign in N Virginia Cognito

  • E

    Eric

    3 months ago

    Users can't access account - AWS East

  • T

    Tommy

    3 months ago

    429 across all of user pools. Pretty sure the world is ending. We're doomed

  • F

    Fred

    3 months ago

    Cognito is down and AWS is not reporting it.

  • M

    Manuel

    3 months ago

    Too many requests error. can't login

  • T

    TD

    3 months ago

    Can confirm the same issue of AWS Cognito returning "Too many requests" error in us-east-1

  • P

    Peter

    3 months ago

    We are unable to login. The error says 'Too many requests'.

  • E

    Edgar

    3 months ago

    User can't login on us-east-1

  • C

    Chris

    3 months ago

    Login requests are throttled on accounts having no changes. Dev/Test/Prod. All are having login issues.

  • S

    Shaun

    3 months ago

    All users logged out, cannot authenticate.

  • J

    JW

    3 months ago

    Throttling and giving errors

  • M

    Michael

    3 months ago

    Getting TooManyRequests errors in us-east-1. We are nowhere near any sort of limits

  • M

    Michael

    3 months ago

    Too Many Requests error logging in, us-east-1

  • U

    Ugur

    3 months ago

    cognito is getting too may requests and giving 400

  • D

    Dale

    3 months ago

    An error occurred (TooManyRequestsException) when calling the InitiateAuth operation

  • C

    Charlie

    3 months ago

    I am getting TooManyRequestsException on every cognito sdk call.

  • F

    fil

    3 months ago

    having 400 error when our client login to cognito

  • C

    Craig

    3 months ago

    This is down - can’t sign in.

  • J

    John

    3 months ago

    Trying to login gives "Too many requests" error

  • R

    Robert

    3 months ago

    Same issue as everyone else. 400 error TooManyRequestsException

  • L

    Leandro

    3 months ago

    SignIn api os gettinf throttled

  • A

    Alfonso

    3 months ago

    Users cannot login and 400 error happens with POST https://cognito-idp.us-east-1.amazonaws.com/,

  • J

    Jeff

    3 months ago

    Getting same issue as everyone

  • C

    Caitlin

    3 months ago

    Unable to access application and being logged out across all our users

  • D

    Dan

    3 months ago

    Service is not functioning. When accessing it returns an error: “Too many requests”

  • D

    Dmitry

    3 months ago

    The cognitive service seems to return 400

  • D

    Daniel

    3 months ago

    Getting TooManyRequestsException in all accounts

  • J

    João

    3 months ago

    Can't sign in, TooManyRequests exception

  • J

    Joe

    3 months ago

    TooManyRequestsException in all our regions and accounts.

  • I

    Ian

    3 months ago

    Cognito is showing "Too many request" and unable to login any users.

  • S

    Steven

    3 months ago

    Aws cognito login 400 bad requests

  • G

    Gabriel

    3 months ago

    Cognito showing error 400 when triying to login ( Too many requests)

  • M

    Matt

    3 months ago

    TooManyRequestsException on Cognito InitiateAuth in us-east-1 across several userpools.

  • S

    Shelton

    3 months ago

    Cognito login too many requests

  • E

    Eduard

    3 months ago

    Too Many Users Exception - Come on AWS... Why are your systems green for us-east-1

  • S

    Shelly

    3 months ago

    An error occurred (TooManyRequestsException) when calling the GetUser operation: Too many requests

  • K

    Katerina

    3 months ago

    shows bad request, users are not authorized now

  • J

    Josh

    3 months ago

    Getting a "too many requests" error when users try to sign in

  • J

    Jon

    3 months ago

    returning too many requests

  • W

    Warren

    3 months ago

    400 error, all auth services down. AWS Amplify app

  • B

    bob

    3 months ago

    unable to login. throwing too many requests exceptions.

  • A

    Arturo

    3 months ago

    Users unable to login in our region us-east-1

  • T

    Tadeo

    3 months ago

    AWS is returning "Too many requests" for several API requests, this is in us-east-1

  • A

    Annd

    3 months ago

    Our users are unable to login with Cognito hosted in us-east-1

  • B

    Brendan

    3 months ago

    user can't login and got 'Too many requests' error

  • B

    Brian

    8 months ago

    Can't access cognito hosted on northeast1

  • R

    Rodrigo

    8 months ago

    Cognito seemed to slow down for authentication and kicked users out of the app. It resolved in a couple of minutes.

Amazon Cognito outage history

IsDown has tracked 5 incidents for Amazon Cognito since started monitoring AWS status in May 2020.

  • Feb 13 2025

    23 days ago · lasted about 5 hours

    We are investigating increased error rates and latencies for AWS Services in the EU-NORTH-1 Region. More details

  • Dec 13 2024

    3 months ago · lasted about 2 hours

    We are investigating increased authentication errors in the US-EAST-1 Region. More details

  • Dec 10 2023

    about 1 year ago · lasted about 1 hour

    We investigating error rates and latencies for the DynamoDB APIs in the US-WEST-2 Region. Other AWS services may be experiencing elevated error rates and latencies as a result of this issue. We are working to resolve the issue and will keep you up... More details

  • May 2020 ...
    IsDown started monitoring AWS status

    We've tracked and collected 5 incidents for Amazon Cognito since started monitoring AWS status

Sign up and check all outage history

Amazon Cognito outages in the last 30 days

Number of Incidents

1 issues

Last incident

24 days ago

Having problems with Amazon Cognito? What can you do?

  1. First, stay calm.

    • We know it's stressful when Amazon Cognito is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did Amazon Cognito already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Amazon Cognito status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If Amazon Cognito is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Service has recovered?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.
Official Status Pages + User Reports

The best way to monitor AWS and other dependencies

Get instant alerts when your critical services go down. One dashboard to monitor all your vendors' status pages.

Start Your Free Trial
14-day free trial No credit card required Cancel anytime

Stay informed about AWS status changes

IsDown offers an easy way to monitor AWS with maximum flexibility

Major Outages Notifications

IsDown monitors Amazon Cognito for major outages. A major outage is when Amazon Cognito experiences a critical issue that severely affects one or more services/regions. When AWS marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors AWS status page for minor outages. A minor outage is when Amazon Cognito experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in AWS status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Component Filtering

IsDown monitors AWS and all their 5228 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

AWS and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.

Frequently Asked Questions

Is Amazon Cognito down today?

Amazon Cognito isn't down. You can check Amazon Cognito status and incident details on the top of the page. IsDown continuously monitors Amazon Cognito official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current Amazon Cognito status?

Amazon Cognito is currently operational. You can check Amazon Cognito status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a Amazon Cognito outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is Amazon Cognito slow today?

Currently there's no report of Amazon Cognito being slow. Check on the top of the page if there are any reported problems by other users.

How are Amazon Cognito outages detected?

IsDown monitors the Amazon Cognito official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last Amazon Cognito outage?

Amazon Cognito last outage was on February 13, 2025 with the title "Increased Error Rates and Latencies - Stockholm"

AWS not working for you? How do I know if AWS is down?
  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.
How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required