Uptimy

Cloud & hosting

Is AWS down?

Live AWS status, measured independently. We probe 18 AWS endpoints from monitoring regions on every continent and record every outage we detect.

AWS is up

Our probes are reaching AWS normally from every region we check from.

Checked every minute from 6 regions on every continent.

24h uptime
7d uptime
30d uptime
  • Website
    100% uptime, 30 days
    5 regions, 103 to 484 ms
    Checking
    p50
    304 ms
    Median response
    p95
    619 ms
    Slowest 5% of checks
    500 ms2500
    24 h ago12 h agonow
  • Management Console
    100% uptime, 30 days
    5 regions, 325 to 2126 ms
    Checking
    p50
    1349 ms
    Median response
    p95
    1679 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • US East (N. Virginia) · us-east-1
    99.99% uptime, 30 days
    6 regions, 200 to 870 ms
    Checking
    p50
    558 ms
    Median response
    p95
    789 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • US East (Ohio) · us-east-2
    99.99% uptime, 30 days
    6 regions, 177 to 875 ms
    Checking
    p50
    570 ms
    Median response
    p95
    754 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • US West (Oregon) · us-west-2
    100% uptime, 30 days
    6 regions, 110 to 1092 ms
    Checking
    p50
    621 ms
    Median response
    p95
    831 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Canada (Central) · ca-central-1
    99.99% uptime, 30 days
    6 regions, 242 to 900 ms
    Checking
    p50
    600 ms
    Median response
    p95
    866 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • South America (São Paulo) · sa-east-1
    99.99% uptime, 30 days
    6 regions, 55 to 1258 ms
    Checking
    p50
    866 ms
    Median response
    p95
    1663 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Europe (Ireland) · eu-west-1
    99.99% uptime, 30 days
    6 regions, 79 to 1176 ms
    Checking
    p50
    610 ms
    Median response
    p95
    742 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Europe (London) · eu-west-2
    99.99% uptime, 30 days
    6 regions, 60 to 1161 ms
    Checking
    p50
    632 ms
    Median response
    p95
    857 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Europe (Frankfurt) · eu-central-1
    99.99% uptime, 30 days
    6 regions, 24 to 1149 ms
    Checking
    p50
    617 ms
    Median response
    p95
    828 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Europe (Stockholm) · eu-north-1
    99.98% uptime, 30 days
    6 regions, 89 to 1213 ms
    Checking
    p50
    701 ms
    Median response
    p95
    977 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Asia Pacific (Mumbai) · ap-south-1
    99.98% uptime, 30 days
    6 regions, 316 to 988 ms
    Checking
    p50
    709 ms
    Median response
    p95
    836 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Asia Pacific (Singapore) · ap-southeast-1
    100% uptime, 30 days
    6 regions, 145 to 1095 ms
    Checking
    p50
    664 ms
    Median response
    p95
    835 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Asia Pacific (Sydney) · ap-southeast-2
    99.91% uptime, 30 days
    6 regions, 72 to 1351 ms
    Checking
    p50
    783 ms
    Median response
    p95
    913 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Asia Pacific (Tokyo) · ap-northeast-1
    100% uptime, 30 days
    6 regions, 367 to 1298 ms
    Checking
    p50
    725 ms
    Median response
    p95
    982 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Documentation
    100% uptime, 30 days
    6 regions, 85 to 831 ms
    Checking
    p50
    477 ms
    Median response
    p95
    716 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Health Dashboard
    100% uptime, 30 days
    6 regions, 118 to 740 ms
    Checking
    p50
    508 ms
    Median response
    p95
    711 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • DNS
    100% uptime, 30 days
    6 regions, 0 to 0 ms
    Checking
    p50
    0 ms
    Median response
    p95
    6 ms
    Slowest 5% of checks
    2 ms10
    24 h ago12 h agonow

Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet

Get notified when AWS goes down

Follow these 18 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment AWS goes down. They don't count against your monitor quota. Free plan, no card required.

Notify me about AWS

About AWS outages

AWS runs a large share of the internet, so an AWS incident is rarely contained to AWS customers. Sites, APIs, payment flows, and SaaS tools that sit on it fail together, and the most common pattern is a single region, most often us-east-1, becoming impaired while the rest of the cloud is fine.

We probe each major region directly: the EC2 regional API endpoint in thirteen regions across North America, South America, Europe, and Asia Pacific, requested every minute from our regions on several continents. A red region means the control plane there is not answering, which is the earliest public sign that workloads in that region are affected.

Alongside the regions we probe the website, the Management Console, the documentation, that the AWS Health Dashboard itself is reachable, and that amazonaws.com resolves. Individual services such as S3, Lambda, or DynamoDB are not probed separately; the AWS Health Dashboard lists them per region.

What we check

Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.

CheckTargetExpectsInterval
Website
aws.amazon.com is unreachable.
httpaws.amazon.comHTTP 2001 min
Management Console
The AWS Management Console is unreachable.
httpconsole.aws.amazon.comHTTP 2001 min
US East (N. Virginia) · us-east-1
The EC2 API in us-east-1 is not answering. Workloads in US East (N. Virginia) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.us-east-1.amazonaws.com/pingHTTP 2001 min
US East (Ohio) · us-east-2
The EC2 API in us-east-2 is not answering. Workloads in US East (Ohio) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.us-east-2.amazonaws.com/pingHTTP 2001 min
US West (Oregon) · us-west-2
The EC2 API in us-west-2 is not answering. Workloads in US West (Oregon) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.us-west-2.amazonaws.com/pingHTTP 2001 min
Canada (Central) · ca-central-1
The EC2 API in ca-central-1 is not answering. Workloads in Canada (Central) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.ca-central-1.amazonaws.com/pingHTTP 2001 min
South America (São Paulo) · sa-east-1
The EC2 API in sa-east-1 is not answering. Workloads in South America (São Paulo) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.sa-east-1.amazonaws.com/pingHTTP 2001 min
Europe (Ireland) · eu-west-1
The EC2 API in eu-west-1 is not answering. Workloads in Europe (Ireland) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.eu-west-1.amazonaws.com/pingHTTP 2001 min
Europe (London) · eu-west-2
The EC2 API in eu-west-2 is not answering. Workloads in Europe (London) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.eu-west-2.amazonaws.com/pingHTTP 2001 min
Europe (Frankfurt) · eu-central-1
The EC2 API in eu-central-1 is not answering. Workloads in Europe (Frankfurt) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.eu-central-1.amazonaws.com/pingHTTP 2001 min
Europe (Stockholm) · eu-north-1
The EC2 API in eu-north-1 is not answering. Workloads in Europe (Stockholm) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.eu-north-1.amazonaws.com/pingHTTP 2001 min
Asia Pacific (Mumbai) · ap-south-1
The EC2 API in ap-south-1 is not answering. Workloads in Asia Pacific (Mumbai) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.ap-south-1.amazonaws.com/pingHTTP 2001 min
Asia Pacific (Singapore) · ap-southeast-1
The EC2 API in ap-southeast-1 is not answering. Workloads in Asia Pacific (Singapore) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.ap-southeast-1.amazonaws.com/pingHTTP 2001 min
Asia Pacific (Sydney) · ap-southeast-2
The EC2 API in ap-southeast-2 is not answering. Workloads in Asia Pacific (Sydney) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.ap-southeast-2.amazonaws.com/pingHTTP 2001 min
Asia Pacific (Tokyo) · ap-northeast-1
The EC2 API in ap-northeast-1 is not answering. Workloads in Asia Pacific (Tokyo) cannot be launched, scaled or managed, and the region itself may be impaired.
httpec2.ap-northeast-1.amazonaws.com/pingHTTP 2001 min
Documentation
AWS documentation is unreachable.
httpdocs.aws.amazon.comHTTP 2005 min
Health Dashboard
The AWS Health Dashboard itself is unreachable.
httphealth.aws.amazon.com/health/statusHTTP 2005 min
DNS
amazonaws.com is not resolving. Every AWS API endpoint depends on it.
dnsamazonaws.comA record resolves1 min

For component-level detail and incident write-ups from the vendor, see AWS Health Dashboard.

Embed a live AWS badge

A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.

Preview

AWS status

Markdown

[![AWS status](https://www.upti.my/status/aws/badge.svg)](https://www.upti.my/status/aws?utm_source=badge)

HTML

<a href="https://www.upti.my/status/aws?utm_source=badge"><img src="https://www.upti.my/status/aws/badge.svg" alt="AWS status"></a>

Recent AWS outages we detected

An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.

AWS is up. Is your AWS integration?

The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on AWS and fail quietly. Here is what teams that rely on AWS monitor on their side.

Workloads you run on AWS

AWS reports on its infrastructure, not on whether your application inside it is healthy. Probe every public endpoint from outside AWS, and put heartbeats on EventBridge schedules, Lambda crons, and ECS scheduled tasks.

HTTP and TCP monitoring

Scheduled jobs on EventBridge and Lambda

A scheduled Lambda that errors or never fires leaves no trace unless you look for it. A heartbeat per schedule tells you when a run did not complete.

Heartbeat monitoring for scheduled jobs

Single-region deployments

If everything you run sits in one region, that region is your single point of failure. Follow the probe for your region so an AWS regional incident reaches your own incident timeline.

Multi-region uptime monitoring

AWS status: frequently asked questions

Look at the probe for your region. AWS regions are isolated by design, so an incident in us-east-1 usually leaves eu-central-1 or ap-southeast-1 untouched. If your region is red from every one of our probing regions, the control plane there is impaired and the AWS Health Dashboard will normally list affected services shortly after. If your region is green, the problem is likely in your own account, application, or network configuration.

Several global AWS services, including IAM, the console sign-in, CloudFront and Route 53 control planes, and parts of S3, are anchored in us-east-1. A us-east-1 incident can therefore break sign-in, DNS changes, or deployments for customers in other regions while their running workloads continue to serve.

AWS tends to acknowledge incidents minutes to hours after customers notice them, and the public dashboard only reflects incidents AWS has declared. Our probe is a direct measurement of the regional EC2 API from outside AWS. When the two disagree, treat our measurement as the early signal and the dashboard as the confirmation.

Look at the per-region results above. If our probes fail from every region, AWS has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, AWS may have a regional incident that does not affect you.

Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.

Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.

Yes. Use "Notify me about AWS" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on AWS: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.

Related

Uptimy is not affiliated with AWS. AWS and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.

23:00 · goodnight

All systems operational

Stop wondering if production is okay.

Tonight, if something breaks, you will know first — with the context to fix it and a status page that keeps customers informed. And if nothing breaks, you get to sleep.

Free plan available · No credit card required · Cancel anytime