Is AWS Batch down?
Current AWS Batch status is UP

We checked the official AWS Batch Status Page 54 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

March 26, 2024 21:15 UTC

WARN

about 1 hour

Increased API Error Rates

See more
Start Time

March 26, 2024 21:15 UTC

Type WARN
Affected Components

N. Virginia - Amazon Elastic Container Service

N. Virginia - AWS Batch

Message

Increased API Error Rates

Details

We are investigating increased API error rates for the EC2 APIs in the US-EAST-1 Region. This is mainly affecting the DescribeInstanceTypes, DescribeInstanceTypeOfferings and DescribeReservedInstancesOfferings APIs. During this time, customers may receive an Internal Error displayed in the Management Console under the "Instance Types" section. We are actively working on identifying the root cause. We will provide another update by 2:30 PM PDT, or sooner if we have additional information to share.

December 10, 2023 03:50 UTC

WARN

40 minutes

Increased Error Rates

See more
Start Time

December 10, 2023 03:50 UTC

Type WARN
Affected Components

Oregon - AWS Batch

Oregon - AWS CodeBuild

Oregon - Amazon Elastic Container Registry

Oregon - Amazon CodeCatalyst

AWS Cloud WAN

Oregon - AWS CloudFormation

Oregon - AWS CodeDeploy

Oregon - Amazon AppStream 2.0

Message

Increased Error Rates

Details

We continue to investigate increased error rates and latencies for the DynamoDB APIs in the US-WEST-2 Region. We have seen some improvement in error rates over the last 15 minutes but customers may still be experiencing errors. We continue to work on resolving the issue and will keep you updated on our progress.

September 19, 2023 05:25 UTC

WARN

3 months

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.

2024-05-06 20:46:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-06 20:46:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-06 20:46:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-06 20:46:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-06 20:46:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More AWS Batch History

StatusGator has about 9 years of AWS Batch status history.

No outages or status changes in the last 24 hours

AWS Batch status, last 24 hours:

9:00 PM
3:00 AM
9:00 AM
3:00 PM
9:00 PM
9:00 PM
9:00 AM
9: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:

May 2024

April 2024

  • Up

  • Warn

  • Down

Instant enriched data from
3,590 status pages

About Our AWS Batch Status Page Integration

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

More than 3,900 StatusGator users monitor AWS Batch 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 763,000 notifications to our users about AWS Batch incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If AWS Batch 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 Batch 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 Batch does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need AWS Batch maintenance notifications, please email us.

AWS Batch 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 Batch maintenance events into your unified calendar.

When AWS Batch 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 Batch 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 Batch 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

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

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 3,590 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.