Skip to content

Outage tracker / AWS (Amazon Web Services)

Is AWS (Amazon Web Services) down?

I'm having a problem

Vendor lists an old incident, not shown as liveWhat AWS (Amazon Web Services) reports

AWS (Amazon Web Services) still lists an incident opened on 2026-03-02 with no update since 2026-09-15; we do not show it as live.

As of the last successful poll, 2026-11-05 15:38 UTC.

AWS (Amazon Web Services)'s status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of AWS (Amazon Web Services) pass from all 10 regions we check.

As of Nov 5, 2026, 3:42 PM UTC, RealUptime's checks of AWS (Amazon Web Services) passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:42 PM UTC
US-East1645 msChecks passing
US-West1785 msChecks passing
Europe1103 msChecks passing
Asia-Pacific2257 msChecks passing
US-Central918 msChecks passing
Canada1525 msChecks passing
UK1895 msChecks passing
Southeast Asia2112 msChecks passing
Australia3560 msChecks passing
South America3615 msChecks passing
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 Nov 5, 2026, 3:33 PM UTC
AWS (Amazon Web Services)'s status page reports Service disruption: Increased Error Rates. Our checks of AWS (Amazon Web Services) currently pass with normal latency. Our checks currently pass 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 the vendor's report and our check reading side by side. A check can miss problems that users see. 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
2.6sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 924ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 867ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
US-West
3.3sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 990ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 3.6s2026-10-22 UTC: p95 3.7s2026-10-23 UTC: p95 3.5s2026-10-24 UTC: p95 3.5s2026-10-25 UTC: p95 3.2s2026-10-26 UTC: p95 3.4s2026-10-27 UTC: p95 3.7s2026-10-28 UTC: p95 3.4s2026-10-29 UTC: p95 3.1s2026-10-30 UTC: p95 3.5s2026-10-31 UTC: p95 3.2s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5
Europe
2.4sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 920ms2026-10-09 UTC: p95 978ms2026-10-10 UTC: p95 951ms2026-10-11 UTC: p95 916ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 820ms2026-10-14 UTC: p95 967ms2026-10-15 UTC: p95 997ms2026-10-16 UTC: p95 843ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Asia-Pacific
4.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-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 2.2s2026-10-09 UTC: p95 2.3s2026-10-10 UTC: p95 2.7s2026-10-11 UTC: p95 2.6s2026-10-12 UTC: p95 2.3s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.4s2026-10-16 UTC: p95 2.3s2026-10-17 UTC: p95 4.3s2026-10-18 UTC: p95 4.8s2026-10-19 UTC: p95 4.8s2026-10-20 UTC: p95 4.7s2026-10-21 UTC: p95 4.6s2026-10-22 UTC: p95 4.2s2026-10-23 UTC: p95 4.5s2026-10-24 UTC: p95 4.2s2026-10-25 UTC: p95 3.8s2026-10-26 UTC: p95 4.6s2026-10-27 UTC: p95 4.4s2026-10-28 UTC: p95 4.5s2026-10-29 UTC: p95 4.2s2026-10-30 UTC: p95 4.1s2026-10-31 UTC: p95 4.2s2026-11-01 UTC: p95 4.3s2026-11-02 UTC: p95 4.5s2026-11-03 UTC: p95 4.3s2026-11-04 UTC: p95 4.1s2026-11-05 UTC: p95 4.2s
Oct 7Oct 21Nov 5
US-Central
3.4sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 2.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 3.3s2026-10-22 UTC: p95 3.5s2026-10-23 UTC: p95 3.7s2026-10-24 UTC: p95 3.5s2026-10-25 UTC: p95 3.3s2026-10-26 UTC: p95 3.3s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 3.6s2026-10-30 UTC: p95 2.9s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 4.9s2026-11-05 UTC: p95 3.4s
Oct 7Oct 21Nov 5
Canada
2.2sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 3.3s2026-10-24 UTC: p95 3.2s2026-10-25 UTC: p95 3.8s2026-10-26 UTC: p95 4.0s2026-10-27 UTC: p95 3.2s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 3.0s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
UK
1.6sp95 · latest
2.5s1.3s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 987ms2026-10-10 UTC: p95 862ms2026-10-11 UTC: p95 899ms2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 936ms2026-10-15 UTC: p95 981ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Southeast Asia
3.9sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.6s2026-10-08 UTC: p95 2.6s2026-10-09 UTC: p95 2.6s2026-10-10 UTC: p95 3.1s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 2.7s2026-10-13 UTC: p95 2.4s2026-10-14 UTC: p95 3.3s2026-10-15 UTC: p95 3.0s2026-10-16 UTC: p95 3.1s2026-10-17 UTC: p95 4.0s2026-10-18 UTC: p95 4.4s2026-10-19 UTC: p95 4.0s2026-10-20 UTC: p95 4.9s2026-10-21 UTC: p95 4.1s2026-10-22 UTC: p95 4.3s2026-10-23 UTC: p95 4.4s2026-10-24 UTC: p95 4.7s2026-10-25 UTC: p95 4.7s2026-10-26 UTC: p95 4.3s2026-10-27 UTC: p95 4.9s2026-10-28 UTC: p95 5.0s2026-10-29 UTC: p95 5.3s2026-10-30 UTC: p95 5.1s2026-10-31 UTC: p95 4.4s2026-11-01 UTC: p95 4.6s2026-11-02 UTC: p95 4.3s2026-11-03 UTC: p95 4.0s2026-11-04 UTC: p95 4.0s2026-11-05 UTC: p95 3.9s
Oct 7Oct 21Nov 5
Australia
5.1sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.9s2026-10-08 UTC: p95 2.8s2026-10-09 UTC: p95 2.7s2026-10-10 UTC: p95 2.7s2026-10-11 UTC: p95 2.3s2026-10-12 UTC: p95 2.3s2026-10-13 UTC: p95 2.7s2026-10-14 UTC: p95 3.0s2026-10-15 UTC: p95 3.2s2026-10-16 UTC: p95 2.4s2026-10-17 UTC: p95 5.5s2026-10-18 UTC: p95 6.6s2026-10-19 UTC: p95 6.2s2026-10-20 UTC: p95 5.9s2026-10-21 UTC: p95 6.4s2026-10-22 UTC: p95 7.1s2026-10-23 UTC: p95 7.4s2026-10-24 UTC: p95 6.6s2026-10-25 UTC: p95 5.6s2026-10-26 UTC: p95 5.0s2026-10-27 UTC: p95 6.0s2026-10-28 UTC: p95 6.4s2026-10-29 UTC: p95 5.9s2026-10-30 UTC: p95 6.0s2026-10-31 UTC: p95 5.9s2026-11-01 UTC: p95 6.1s2026-11-02 UTC: p95 5.2s2026-11-03 UTC: p95 4.9s2026-11-04 UTC: p95 4.4s2026-11-05 UTC: p95 5.1s
Oct 7Oct 21Nov 5
South America
3.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 2.3s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.4s2026-10-19 UTC: p95 4.4s2026-10-20 UTC: p95 4.6s2026-10-21 UTC: p95 5.1s2026-10-22 UTC: p95 4.8s2026-10-23 UTC: p95 7.1s2026-10-24 UTC: p95 4.7s2026-10-25 UTC: p95 4.8s2026-10-26 UTC: p95 4.3s2026-10-27 UTC: p95 4.1s2026-10-28 UTC: p95 4.9s2026-10-29 UTC: p95 5.2s2026-10-30 UTC: p95 5.0s2026-10-31 UTC: p95 4.6s2026-11-01 UTC: p95 5.1s2026-11-02 UTC: p95 4.2s2026-11-03 UTC: p95 4.0s2026-11-04 UTC: p95 4.1s2026-11-05 UTC: p95 3.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on AWS (Amazon Web Services)

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Console sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DynamoDBUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • LambdaUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when AWS (Amazon Web Services) reports an incident on its status page, and again when it reports it resolved.

Get an email when AWS (Amazon Web Services) reports an incident

Email me when AWS (Amazon Web Services) reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is AWS (Amazon Web Services)'s own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1645msstatus code: 200checked: Nov 5, 2026, 3:40 PM 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
      Checks passinglatency: 1785msstatus code: 200checked: Nov 5, 2026, 3:41 PM 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
      Checks passinglatency: 918msstatus code: 200checked: Nov 5, 2026, 3:41 PM 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
      Checks passinglatency: 1525msstatus code: 200checked: Nov 5, 2026, 3:40 PM 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
    Checks passinglatency: 3615msstatus code: 200checked: Nov 5, 2026, 3:40 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1103msstatus code: 200checked: Nov 5, 2026, 3:41 PM 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
      Checks passinglatency: 1895msstatus code: 200checked: Nov 5, 2026, 3:42 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2257msstatus code: 200checked: Nov 5, 2026, 3:40 PM 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
      Checks passinglatency: 2112msstatus code: 200checked: Nov 5, 2026, 3:40 PM 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
      Checks passinglatency: 3560msstatus code: 200checked: Nov 5, 2026, 3:42 PM 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 probe events

Increased invoke error rates, 1mdeclared on their status page2026-10-30
Elevated packet loss, 2h 42mdeclared on their status page2026-10-04
Increased Error Rates, 58mdeclared on their status page2026-09-21
Increased API Error Rates, 2h 18mdeclared on their status page2026-09-03
Increased Error Rates, 38mdeclared on their status page2026-08-21
Increased Error Rates, 3h 32mdeclared on their status page2026-08-19
Increased Packet loss, 72h 18mdeclared on their status page2026-08-15
Elevated Packet Loss, 1h 21mdeclared on their status page2026-07-31

check 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 check readings and AWS (Amazon Web Services)'s own claim at the time, side by side.

Full check history for AWS (Amazon Web Services): 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

AWS (Amazon Web Services) uptime by RealUptime's checksLive, from this page's own readings.
[![AWS (Amazon Web Services) uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is AWS (Amazon Web Services) down?", https://realuptime.io/outages/aws. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://ec2.us-east-1.amazonaws.com/
secondary
https://health.aws.amazon.com/health/status
secondaryfunctional: live API
https://sts.us-east-1.amazonaws.com/
secondaryfunctional: live API
https://sts.eu-west-1.amazonaws.com/
secondaryfunctional: live API
https://sts.ap-southeast-1.amazonaws.com/
secondary
https://dynamodb.us-east-1.amazonaws.com/
secondary
https://lambda.us-east-1.amazonaws.com/
secondary
https://signin.aws.amazon.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: ec2.us-east-1.amazonaws.com

RealUptime is not affiliated with AWS (Amazon Web Services); the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.