Skip to content

Outage tracker / Amazon

Is Amazon down?

I'm having a problem

Partially degradedchecked 1 minute ago

Amazon is answering our probes, but its web surface is running at least 4.1x its 7-day median from Europe, its API is running at least 4.9x its 7-day median from Europe, its Customer Service is running at least 3.3x its 7-day median from US-Central and its Images is running at least 3.6x its 7-day median from US-Central. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 2:34 PM UTC, RealUptime's checks of Amazon passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Amazon did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Amazon works for users.

Email me when our checks of Amazon fail from two or more distant regions

One email when our checks of Amazon fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Amazon's official status.

our check readinglive · checked Nov 5, 2026, 2:34 PM UTC
US-East3194 msChecks passing
US-West1828 msChecks passing
Europe1836 msDegraded
Asia-Pacific4201 msChecks passing
US-Central1903 msPartially degraded
Canada448 msChecks passing
UK1701 msChecks passing
Southeast Asia1632 msChecks passing
Australia1771 msChecks passing
South America1586 msChecks passing
their status pagetheir claim, not our reading

Amazon publishes no status feed we can read, so the only reading here is our check reading on the left.

Amazon response time, by region

US-East
3.5sp95 · 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.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 3.5s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5
US-West
4.1sp95 · 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 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 3.5s2026-11-03 UTC: p95 4.7s2026-11-04 UTC: p95 4.3s2026-11-05 UTC: p95 4.1s
Oct 7Oct 21Nov 5
Europe
2.4sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, 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.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 728ms2026-10-25 UTC: p95 733ms2026-10-26 UTC: p95 898ms2026-10-27 UTC: p95 788ms2026-10-28 UTC: p95 646ms2026-10-29 UTC: p95 700ms2026-10-30 UTC: p95 510ms2026-10-31 UTC: p95 535ms2026-11-01 UTC: p95 456ms2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 3.1s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Asia-Pacific
4.4sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.5s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.9s2026-10-27 UTC: p95 5.6s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 3.8s2026-11-03 UTC: p95 4.8s2026-11-04 UTC: p95 4.6s2026-11-05 UTC: p95 4.4s
Oct 7Oct 21Nov 5
US-Central
2.1sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 546ms2026-10-08 UTC: p95 616ms2026-10-09 UTC: p95 581ms2026-10-10 UTC: p95 542ms2026-10-11 UTC: p95 648ms2026-10-12 UTC: p95 550ms2026-10-13 UTC: p95 559ms2026-10-14 UTC: p95 436ms2026-10-15 UTC: p95 469ms2026-10-16 UTC: p95 555ms2026-10-17 UTC: p95 946ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 950ms2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Canada
925msp95 · 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.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 604ms2026-10-19 UTC: p95 573ms2026-10-20 UTC: p95 702ms2026-10-21 UTC: p95 723ms2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 925ms
Oct 7Oct 21Nov 5
UK
1.9sp95 · 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.1s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Southeast Asia
3.0sp95 · 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-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.8s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 3.8s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
Australia
2.4sp95 · 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-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 2.6s2026-10-13 UTC: p95 2.3s2026-10-14 UTC: p95 2.3s2026-10-15 UTC: p95 2.7s2026-10-16 UTC: p95 2.5s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
South America
1.7sp95 · 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 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 820ms2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 884ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 3.3s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 9.1s2026-10-24 UTC: p95 2.9s2026-10-25 UTC: p95 3.0s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Amazon

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 Amazon. It cannot diagnose Amazon's own systems.

What we measured, function by function

Amazon 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: Degraded Answering, but 4.1x slower than its 7-day median.Asia-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: Degraded Answering, but 4.9x slower than its 7-day median.Asia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Customer ServiceUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Degraded Answering, but 3.3x slower than its 7-day median.Canada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • ImagesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Degraded Answering, but 3.6x slower than its 7-day median.Canada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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
    Partially degradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 3194msstatus code: 200checked: Nov 5, 2026, 2:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Amazon normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1828msstatus code: 200checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Amazon normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Partially degradedlatency: 1903msstatus code: 200checked: Nov 5, 2026, 2:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Amazon normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 448msstatus code: 200checked: Nov 5, 2026, 2:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Amazon normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1586msstatus code: 200checked: Nov 5, 2026, 2:34 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Amazon normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Degradedlatency: 1836msstatus code: 200checked: Nov 5, 2026, 2:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Amazon normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1701msstatus code: 200checked: Nov 5, 2026, 2:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Amazon 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: 4201msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Amazon normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1632msstatus code: 200checked: Nov 5, 2026, 2:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Amazon normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1771msstatus code: 200checked: Nov 5, 2026, 2:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Amazon 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 Amazon, 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 Amazon yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Amazon.

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

We have been measuring Amazon 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 Amazon covering any window you pick, with our check readings and Amazon's own claim at the time, side by side.

Full check history for Amazon: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Amazon uptime by RealUptime's checksLive, from this page's own readings.
[![Amazon uptime by RealUptime's checks](https://realuptime.io/outages/amazon/badge.svg?days=30)](https://realuptime.io/outages/amazon)
<a href="https://realuptime.io/outages/amazon"><img src="https://realuptime.io/outages/amazon/badge.svg?days=30" alt="Amazon 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 Amazon down?", https://realuptime.io/outages/amazon. The readings change with every check, so give the date you read them.

How our checks compare with Amazon's stated SLA

At or above your target

Our checks of Amazon failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Amazon'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://completion.amazon.com/api/2017/suggestions?mid=ATVPDKIKX0DER&alias=aps&prefix=a
secondary
https://www.amazon.com/
secondary
https://www.amazon.com/gp/help/customer/display.html
secondary
https://images-na.ssl-images-amazon.com/images/G/01/gc/designs/livepreview/amazon_dkblue_noto_email_v2016_us-main._CB468775337_.png

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: completion.amazon.com

RealUptime is not affiliated with Amazon; the name identifies what we checked, and nothing here speaks for Amazon's own team. We send a single web request to Amazon from 10 regions on our own schedule and time the response. We do not see inside Amazon's systems, do not use an account or real transaction, and are not the same signal Amazon's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Amazon 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.