outages.live
Live

AWS

AWS is reporting major outage

Checked 3 min ago Major outage

Major outage in UAE, Bahrain

Region Availability (Bahrain)

AWS services do not work in the Middle East (Bahrain) me-south-1 Region. The affected components include Amazon Simple Storage Service, Amazon API Gateway, AWS WAF, Amazon Redshift, and other services in this Region. AWS reports that it cannot restore access to resources and data hosted only in this Region.

Major outageupdated 48 d ago

Region Availability (UAE)

AWS services do not work in the Middle East (UAE) Region (me-central-1). This affects many components, including Amazon S3 Replication Time Control, Amazon Relational Database Service, AWS Sign-In, and AWS Direct Connect. AWS reports that resources in the mec1-az2 Availability Zone cannot be restored. AWS continues to recover other regional and zonal resources. The incident is active.

Major outageupdated 48 d ago

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

90

Median duration

No data

Longest incident

No data

Components

279

UAE

Amazon CloudWatch Synthetics Major outage
90 days agoNo incidentsToday
Amazon S3 Replication Time Control Major outage
90 days agoNo incidentsToday
Amazon VPC Lattice Major outage
90 days agoNo incidentsToday
AWS IAM Identity Center Major outage
90 days agoNo incidentsToday
Amazon Relational Database Service Major outage
90 days agoNo incidentsToday
Amazon CloudWatch Major outage
90 days agoNo incidentsToday
AWS Sign-In Major outage
90 days agoNo incidentsToday
AWS End User Messaging Major outage
90 days agoNo incidentsToday
Amazon Managed Workflows for Apache Airflow Major outage
90 days agoNo incidentsToday
AWS Firewall Manager Major outage
90 days agoNo incidentsToday
Amazon Simple Workflow Service Major outage
90 days agoNo incidentsToday
AWS IoT Device Defender Major outage
90 days agoNo incidentsToday
Traffic Mirroring Major outage
90 days agoNo incidentsToday
AWS NAT Gateway Major outage
90 days agoNo incidentsToday
Amazon Managed Service for Prometheus Major outage
90 days ago90 days with an incidentToday
AWS Batch Major outage
90 days agoNo incidentsToday
AWS DataSync Major outage
90 days agoNo incidentsToday
AWS Direct Connect Major outage
90 days agoNo incidentsToday
AWS Secrets Manager Major outage
90 days agoNo incidentsToday
AWS Launch Wizard Major outage
90 days agoNo incidentsToday
Amazon Elastic MapReduce Major outage
90 days agoNo incidentsToday
Amazon FSx Major outage
90 days agoNo incidentsToday
AWS CloudTrail Major outage
90 days agoNo incidentsToday
Amazon Managed Grafana Major outage
90 days ago90 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Affected components

100
  • Amazon CloudWatch SyntheticsUAEMajor outage
  • Amazon S3 Replication Time ControlUAEMajor outage
  • Amazon VPC LatticeUAEMajor outage
  • AWS IAM Identity CenterUAEMajor outage
  • Amazon Relational Database ServiceUAEMajor outage
  • Amazon CloudWatchUAEMajor outage
  • AWS Sign-InUAEMajor outage
  • AWS End User MessagingUAEMajor outage
  • Amazon Managed Workflows for Apache AirflowUAEMajor outage
  • AWS Firewall ManagerUAEMajor outage
  • Amazon Simple Workflow ServiceUAEMajor outage
  • AWS IoT Device DefenderUAEMajor outage

Follow AWS

Your coding agent knows when AWS is down, and tells you when a failure is theirs, not yours. You can also get AWS incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "aws" and tell me if AWS has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=aws
Slack
/feed subscribe https://outages.live/feed.xml?providers=aws

Go from tracking outages to fixing production issues with Polylane.

Try Polylane