Skip to content

Outage tracker / AWS (Amazon Web Services)

Is AWS (Amazon Web Services) down?

I'm having a problem

Operationalchecked moments ago

We reached AWS (Amazon Web Services) from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, AWS (Amazon Web Services) answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 8 min on Sep 15, 2026 (API, from Southeast Asia and Canada).

AWS (Amazon Web Services)'s own status page reports "Service disruption: Increased Error Rates." That is their claim, not our measurement: our probes are currently reaching AWS (Amazon Web Services), and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East838 msOperational
US-West806 msOperational
Europe1005 msOperational
Asia-Pacific1230 msOperational
US-Central768 msOperational
Canada498 msOperational
UK635 msOperational
Southeast Asia2232 msOperational
Australia2183 msOperational
South America1537 msOperational
their status pagetheir claim, not our reading

AWS (Amazon Web Services) reports: Minor incident (“Service disruption: Increased Error Rates”)

from AWS (Amazon Web Services)'s own status page, checked Sep 23, 2026, 8:47 AM UTC
AWS (Amazon Web Services)'s status page reports Service disruption: Increased Error Rates. Our probes are currently reaching AWS (Amazon Web Services) successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

This is AWS (Amazon Web Services)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

AWS (Amazon Web Services) response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.5s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.4s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.6s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 940ms2026-09-06 UTC: p95 952ms2026-09-07 UTC: p95 959ms2026-09-08 UTC: p95 983ms2026-09-09 UTC: p95 859ms2026-09-10 UTC: p95 992ms2026-09-11 UTC: p95 973ms2026-09-12 UTC: p95 976ms2026-09-13 UTC: p95 958ms2026-09-14 UTC: p95 951ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 971ms2026-09-21 UTC: p95 963ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s
Aug 25Sep 8Sep 23
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 900ms2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 1.3s2026-09-06 UTC: p95 966ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 909ms2026-09-09 UTC: p95 709ms2026-09-10 UTC: p95 746ms2026-09-11 UTC: p95 707ms2026-09-12 UTC: p95 646ms2026-09-13 UTC: p95 680ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 960ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.0s
Aug 25Sep 8Sep 23
Europe
999msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 955ms2026-08-27 UTC: p95 1.0s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 947ms2026-08-30 UTC: p95 925ms2026-08-31 UTC: p95 930ms2026-09-01 UTC: p95 963ms2026-09-02 UTC: p95 945ms2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 981ms2026-09-06 UTC: p95 933ms2026-09-07 UTC: p95 966ms2026-09-08 UTC: p95 939ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 915ms2026-09-11 UTC: p95 965ms2026-09-12 UTC: p95 907ms2026-09-13 UTC: p95 876ms2026-09-14 UTC: p95 889ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 990ms2026-09-17 UTC: p95 983ms2026-09-18 UTC: p95 960ms2026-09-19 UTC: p95 924ms2026-09-20 UTC: p95 904ms2026-09-21 UTC: p95 956ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 999ms
Aug 25Sep 8Sep 23
Asia-Pacific
2.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 2.1s2026-08-26 UTC: p95 2.3s2026-08-27 UTC: p95 2.2s2026-08-28 UTC: p95 2.2s2026-08-29 UTC: p95 2.0s2026-08-30 UTC: p95 2.1s2026-08-31 UTC: p95 2.1s2026-09-01 UTC: p95 2.3s2026-09-02 UTC: p95 2.4s2026-09-03 UTC: p95 3.3s2026-09-04 UTC: p95 2.1s2026-09-05 UTC: p95 2.0s2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 2.0s2026-09-11 UTC: p95 2.1s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 2.2s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.0s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.1s2026-09-23 UTC: p95 2.2s
Aug 25Sep 8Sep 23
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.3s2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.0s
Aug 25Sep 8Sep 23
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.4s2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.2s
Aug 25Sep 8Sep 23
UK
986msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.0s2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 910ms2026-09-08 UTC: p95 958ms2026-09-09 UTC: p95 876ms2026-09-10 UTC: p95 900ms2026-09-11 UTC: p95 955ms2026-09-12 UTC: p95 913ms2026-09-13 UTC: p95 938ms2026-09-14 UTC: p95 818ms2026-09-15 UTC: p95 973ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 986ms
Aug 25Sep 8Sep 23
Southeast Asia
3.8sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 3.3s2026-09-04 UTC: p95 2.8s2026-09-05 UTC: p95 3.1s2026-09-06 UTC: p95 3.0s2026-09-07 UTC: p95 2.8s2026-09-08 UTC: p95 2.7s2026-09-09 UTC: p95 3.0s2026-09-10 UTC: p95 3.1s2026-09-11 UTC: p95 3.1s2026-09-12 UTC: p95 2.6s2026-09-13 UTC: p95 2.9s2026-09-14 UTC: p95 3.1s2026-09-15 UTC: p95 3.2s2026-09-16 UTC: p95 2.8s2026-09-17 UTC: p95 3.1s2026-09-18 UTC: p95 3.3s2026-09-19 UTC: p95 3.0s2026-09-20 UTC: p95 3.1s2026-09-21 UTC: p95 4.0s2026-09-22 UTC: p95 3.8s2026-09-23 UTC: p95 3.8s
Aug 25Sep 8Sep 23
Australia
2.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 3.1s2026-09-04 UTC: p95 3.0s2026-09-05 UTC: p95 2.7s2026-09-06 UTC: p95 3.0s2026-09-07 UTC: p95 3.0s2026-09-08 UTC: p95 2.8s2026-09-09 UTC: p95 2.7s2026-09-10 UTC: p95 2.8s2026-09-11 UTC: p95 2.8s2026-09-12 UTC: p95 3.0s2026-09-13 UTC: p95 2.8s2026-09-14 UTC: p95 2.6s2026-09-15 UTC: p95 3.2s2026-09-16 UTC: p95 2.7s2026-09-17 UTC: p95 2.7s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 2.7s2026-09-20 UTC: p95 2.7s2026-09-21 UTC: p95 3.0s2026-09-22 UTC: p95 3.0s2026-09-23 UTC: p95 2.8s
Aug 25Sep 8Sep 23
South America
2.0sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 2.3s2026-09-05 UTC: p95 1.9s2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 2.0s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 2.0s2026-09-15 UTC: p95 2.4s2026-09-16 UTC: p95 2.3s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.0s
Aug 25Sep 8Sep 23

Is it AWS (Amazon Web Services), or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not AWS (Amazon Web Services) -- it cannot diagnose AWS (Amazon Web Services)'s own systems.

What we measured, function by function

AWS (Amazon Web Services) answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 838msstatus code: 200checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach AWS (Amazon Web Services) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 806msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach AWS (Amazon Web Services) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 768msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach AWS (Amazon Web Services) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 498msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach AWS (Amazon Web Services) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1537msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach AWS (Amazon Web Services) normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 1005msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach AWS (Amazon Web Services) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 635msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach AWS (Amazon Web Services) normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1230msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach AWS (Amazon Web Services) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 2232msstatus code: 200checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach AWS (Amazon Web Services) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 2183msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach AWS (Amazon Web Services) normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using AWS (Amazon Web Services), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for AWS (Amazon Web Services) yet, which is not evidence that nothing is wrong.

Recent outages

Outage, 8mmeasured by our probes · Southeast Asia and Canada2026-09-15
Partial outage, 4mmeasured by our probes · US-West2026-09-12

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring AWS (Amazon Web Services) since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for AWS (Amazon Web Services) covering any window you pick, with our measurements and AWS (Amazon Web Services)'s own claim at the time, side by side.

Full availability history for AWS (Amazon Web Services): 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching AWS (Amazon Web Services), and again when they can reach it again. That is our own measurement from ten regions, not AWS (Amazon Web Services)'s status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

AWS (Amazon Web Services) uptime measured by RealUptimeLive, from this page's own readings.
[![AWS (Amazon Web Services) uptime measured by RealUptime](https://realuptime.io/outages/aws/badge.svg?days=30)](https://realuptime.io/outages/aws)
<a href="https://realuptime.io/outages/aws"><img src="https://realuptime.io/outages/aws/badge.svg?days=30" alt="AWS (Amazon Web Services) uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What AWS (Amazon Web Services)'s SLA implies, from our measurement

At or above your target

We measured 8 minutes of downtime for AWS (Amazon Web Services) over the last 30 days, which is 99.9811% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 3 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from AWS (Amazon Web Services)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://ec2.us-east-1.amazonaws.com/
secondary
https://health.aws.amazon.com/health/status
RealUptime is not affiliated with AWS (Amazon Web Services); the name identifies what we measured, and nothing here speaks for AWS (Amazon Web Services)'s own team. We send a single web request to AWS (Amazon Web Services) from 10 regions on our own schedule and time the response. We do not see inside AWS (Amazon Web Services)'s systems, do not use an account or real transaction, and are not the same signal AWS (Amazon Web Services)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for AWS (Amazon Web Services) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.