Is AWS Batch down?
Current AWS Batch status is UP

We checked the official AWS Batch Status Page 2 min. 17 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent AWS Batch Outages and Issues

Follow the recent outages and downtime for AWS Batch in the table below.

Start Time

Type

Length

Message

Details

September 19, 2023 05:25 UTC

WARN

ongoing

Network Connectivity Issues

See more
Start Time

September 19, 2023 05:25 UTC

Type WARN
Affected Components

Oregon - AWS Elastic Beanstalk

Oregon - AWS Batch

Message

Network Connectivity Issues

Details

We continue to work towards resolving the increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. We have now seen network mapping propagation latencies return to normal levels in both usw2-az1 and usw2-az2 Availability Zones. At this stage, all EC2 instance launches and network configuration changes are operating normally. We’re continuing to monitor network mapping latencies and will provide a final update once all has been confirmed to be operating normally.

September 18, 2023 19:16 UTC

WARN

about 10 hours

Network Connectivity Issues

See more
Start Time

September 18, 2023 19:16 UTC

Type WARN
Affected Components

Oregon - AWS Batch

Oregon - Amazon Elastic MapReduce

Message

Network Connectivity Issues

Details

We can confirm increased networking latencies and errors affecting multiple Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. We have identified a potential root cause of the errors and are attempting mitigations. Early signs are this mitigation is reducing error rates and latencies. We continue to work towards a full root case and recovery.

December 08, 2021 04:36 UTC

WARN

almost 2 years

API Error Rates in US-EAST-1

See more
Start Time

December 08, 2021 04:36 UTC

Type WARN
Affected Components

N. Virginia - AWS Batch

Message

API Error Rates in US-EAST-1

Details

API Error Rates in US-EAST-1
[9:37 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified the root cause and are actively working towards recovery.

[10:12 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified root cause of the issue causing service API and console issues in the US-EAST-1 Region, and are starting to see some signs of recovery. We do not have an ETA for full recovery at this time.

[11:26 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. Services impacted include: EC2, Connect, DynamoDB, Glue, Athena, Timestream, and Chime and other AWS Services in US-EAST-1. The root cause of this issue is an impairment of several network devices in the US-EAST-1 Region. We are pursuing multiple mitigation paths in parallel, and have seen some signs of recovery, but we do not have an ETA for full recovery at this time. Root logins for consoles in all AWS regions are affected by this issue, however customers can login to consoles other than US-EAST-1 by using an IAM role for authentication.

[12:34 PM PST] We continue to experience increased API error rates for multiple AWS Services in the US-EAST-1 Region. The root cause of this issue is an impairment of several network devices. We continue to work toward mitigation, and are actively working on a number of different mitigation and resolution actions. While we have observed some early signs of recovery, we do not have an ETA for full recovery. For customers experiencing issues signing-in to the AWS Management Console in US-EAST-1, we recommend retrying using a separate Management Console endpoint (such as https://us-west-2.console.aws.amazon.com/). Additionally, if you are attempting to login using root login credentials you may be unable to do so, even via console endpoints not in US-EAST-1. If you are impacted by this, we recommend using IAM Users or Roles for authentication. We will continue to provide updates here as we have more information to share.

[2:04 PM PST] We have executed a mitigation which is showing significant recovery in the US-EAST-1 Region. We are continuing to closely monitor the health of the network devices and we expect to continue to make progress towards full recovery. We still do not have an ETA for full recovery at this time.

[2:43 PM PST] We have mitigated the underlying issue that caused some network devices in the US-EAST-1 Region to be impaired. We are seeing improvement in availability across most AWS services. All services are now independently working through service-by-service recovery. We continue to work toward full recovery for all impacted AWS Services and API operations. In order to expedite overall recovery, we have temporarily disabled Event Deliveries for Amazon EventBridge in the US-EAST-1 Region. These events will still be received & accepted, and queued for later delivery.

[3:03 PM PST] Many services have already recovered, however we are working towards full recovery across services. Services like SSO, Connect, API Gateway, ECS/Fargate, and EventBridge are still experiencing impact. Engineers are actively working on resolving impact to these services.

[4:35 PM PST] With the network device issues resolved, we are now working towards recovery of any impaired services. We will provide additional updates for impaired services within the appropriate entry in the Service Health Dashboard.

December 08, 2021 00:11 UTC

WARN

about 4 hours

API Error Rates in US-EAST-1

See more
Start Time

December 08, 2021 00:11 UTC

Type WARN
Affected Components

N. Virginia - AWS Batch

Message

API Error Rates in US-EAST-1

Details

API Error Rates in US-EAST-1
[9:37 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified the root cause and are actively working towards recovery.

[10:12 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified root cause of the issue causing service API and console issues in the US-EAST-1 Region, and are starting to see some signs of recovery. We do not have an ETA for full recovery at this time.

[11:26 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. Services impacted include: EC2, Connect, DynamoDB, Glue, Athena, Timestream, and Chime and other AWS Services in US-EAST-1. The root cause of this issue is an impairment of several network devices in the US-EAST-1 Region. We are pursuing multiple mitigation paths in parallel, and have seen some signs of recovery, but we do not have an ETA for full recovery at this time. Root logins for consoles in all AWS regions are affected by this issue, however customers can login to consoles other than US-EAST-1 by using an IAM role for authentication.

[12:34 PM PST] We continue to experience increased API error rates for multiple AWS Services in the US-EAST-1 Region. The root cause of this issue is an impairment of several network devices. We continue to work toward mitigation, and are actively working on a number of different mitigation and resolution actions. While we have observed some early signs of recovery, we do not have an ETA for full recovery. For customers experiencing issues signing-in to the AWS Management Console in US-EAST-1, we recommend retrying using a separate Management Console endpoint (such as https://us-west-2.console.aws.amazon.com/). Additionally, if you are attempting to login using root login credentials you may be unable to do so, even via console endpoints not in US-EAST-1. If you are impacted by this, we recommend using IAM Users or Roles for authentication. We will continue to provide updates here as we have more information to share.

[2:04 PM PST] We have executed a mitigation which is showing significant recovery in the US-EAST-1 Region. We are continuing to closely monitor the health of the network devices and we expect to continue to make progress towards full recovery. We still do not have an ETA for full recovery at this time.

[2:43 PM PST] We have mitigated the underlying issue that caused some network devices in the US-EAST-1 Region to be impaired. We are seeing improvement in availability across most AWS services. All services are now independently working through service-by-service recovery. We continue to work toward full recovery for all impacted AWS Services and API operations. In order to expedite overall recovery, we have temporarily disabled Event Deliveries for Amazon EventBridge in the US-EAST-1 Region. These events will still be received & accepted, and queued for later delivery.

[3:03 PM PST] Many services have already recovered, however we are working towards full recovery across services. Services like SSO, Connect, API Gateway, ECS/Fargate, and EventBridge are still experiencing impact. Engineers are actively working on resolving impact to these services.

November 24, 2021 20:15 UTC

WARN

13 days

Increased API Error Rates Increased Error Rates

See more
Start Time

November 24, 2021 20:15 UTC

Type WARN
Affected Components

Ohio - AWS Lambda

Ohio - AWS Batch

Message

Increased API Error Rates Increased Error Rates

Details

11:24 AM PST We have confirmed that the elevated API error rate is restricted to control plane operations for API Gateway Version 2 API (WebSocket and HTTP APIs).
11:46 AM PST We are seeing some recovery in error rates and latencies for the AWS Management Console in the US-EAST-2 Region.

2023-11-11 22:11:37 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2023-11-11 22:11:37 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2023-11-11 22:11:37 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2023-11-11 22:11:37 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2023-11-11 22:11:37 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More AWS Batch History

StatusGator has over 8 years of AWS Batch status history.

No outages or status changes in the last 24 hours

AWS Batch status, last 24 hours:

11:00 PM
5:00 AM
11:00 AM
5:00 PM
11:00 PM
11:00 PM
11:00 AM
11:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

AWS Batch Outage and Status History

We've been monitoring AWS Batch outages since March 8, 2015.
Here's the history of service outages we've observed from the AWS Batch Status Page:

November 2023

October 2023

  • Up

  • Warn

  • Down

Instant enriched data from
2,890 status pages

About Our AWS Lambda Status Page Integration

AWS Lambda is a Cloud Infrastructure solution that StatusGator has been monitoring since March 2015. Over the past over 8 years, we have collected data on on more than 1,599 outages that affected AWS Lambda users. When AWS Lambda publishes downtime on their status page, they do so across 4,596 components and 30 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 3,700 StatusGator users monitor AWS Lambda to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 758,600 notifications to our users about AWS Lambda incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If AWS Lambda is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when AWS Lambda is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

AWS Lambda does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need AWS Lambda maintenance notifications, please email us.

AWS Lambda does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate AWS Lambda maintenance events into your unified calendar.

When AWS Lambda posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When AWS Lambda has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because AWS Lambda has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Is AWS Batch down today?

According to its status page AWS Batch is currently up. You can check the most recent events in the 'Recent Outages and Issues' section above.

How can I get notified when AWS Batch is not working or have outages?

StatusGator can send you instant alerts by email, SMS, Slack, and more. Sign up now, it's free!

How can I find out if AWS Batch is having issues?

There are two main options: You can check the AWS Batch status page or you can subscribe to StatusGator for free alerts and notifications when their status page changes.

AWS Batch status page says the service is up, but I'm having issues. What's wrong?

There may be several reasons for that:

  • An outage that hasn't been communicated yet via the AWS Batch status page.
  • Some local issues with a small group of accounts on the service side.
  • Technical issues on your side, or problems with your software or ISP.
  • A misconfiguration on your side.

We recommend contacting AWS Batch customer support while checking everything on your side. You can also try Tweeting at them via @awscloud on Twitter. Or visit their official status page or website:

Where do you get the official AWS Batch status?

We use the official AWS Batch status page. Here are links to their status page and other helpful links.

AWS Batch Down?

Are you experiencing issues with AWS Batch? Sign up to receive notifications when AWS Batch publishes outages.

AWS Batch Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 2,890 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of AWS Batch?

Sign up for StatusGator and see all historical information about AWS Batch outages and performance issues. Get free, instant notifications when AWS Batch goes down.