Skip to content

Outage tracker / Amazon

Is Amazon down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Amazon from all 10 regions we check.

As of Sep 23, 2026, 9:07 AM UTC, Amazon answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Amazon (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:07 AM UTC
US-East923 msOperational
US-West477 msOperational
Europe293 msOperational
Asia-Pacific812 msOperational
US-Central510 msOperational
Canada481 msOperational
UK356 msOperational
Southeast Asia1057 msOperational
Australia1505 msOperational
South America700 msOperational
their status pagetheir claim, not our reading

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

Amazon response time, by region

US-East
637msp95 · 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 639ms2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 527ms2026-08-28 UTC: p95 579ms2026-08-29 UTC: p95 785ms2026-08-30 UTC: p95 682ms2026-08-31 UTC: p95 778ms2026-09-01 UTC: p95 781ms2026-09-02 UTC: p95 716ms2026-09-03 UTC: p95 580ms2026-09-04 UTC: p95 630ms2026-09-05 UTC: p95 560ms2026-09-06 UTC: p95 576ms2026-09-07 UTC: p95 522ms2026-09-08 UTC: p95 521ms2026-09-09 UTC: p95 616ms2026-09-10 UTC: p95 561ms2026-09-11 UTC: p95 603ms2026-09-12 UTC: p95 557ms2026-09-13 UTC: p95 740ms2026-09-14 UTC: p95 854ms2026-09-15 UTC: p95 555ms2026-09-16 UTC: p95 651ms2026-09-17 UTC: p95 643ms2026-09-18 UTC: p95 639ms2026-09-19 UTC: p95 686ms2026-09-20 UTC: p95 560ms2026-09-21 UTC: p95 513ms2026-09-22 UTC: p95 563ms2026-09-23 UTC: p95 637ms
Aug 25Sep 8Sep 23
US-West
850msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 593ms2026-08-26 UTC: p95 372ms2026-08-27 UTC: p95 474ms2026-08-28 UTC: p95 612ms2026-08-29 UTC: p95 848ms2026-08-30 UTC: p95 645ms2026-08-31 UTC: p95 508ms2026-09-01 UTC: p95 479ms2026-09-02 UTC: p95 690ms2026-09-03 UTC: p95 869ms2026-09-04 UTC: p95 575ms2026-09-05 UTC: p95 724ms2026-09-06 UTC: p95 508ms2026-09-07 UTC: p95 722ms2026-09-08 UTC: p95 610ms2026-09-09 UTC: p95 339ms2026-09-10 UTC: p95 384ms2026-09-11 UTC: p95 386ms2026-09-12 UTC: p95 398ms2026-09-13 UTC: p95 562ms2026-09-14 UTC: p95 609ms2026-09-15 UTC: p95 771ms2026-09-16 UTC: p95 624ms2026-09-17 UTC: p95 813ms2026-09-18 UTC: p95 592ms2026-09-19 UTC: p95 654ms2026-09-20 UTC: p95 629ms2026-09-21 UTC: p95 704ms2026-09-22 UTC: p95 831ms2026-09-23 UTC: p95 850ms
Aug 25Sep 8Sep 23
Europe
423msp95 · 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 317ms2026-08-26 UTC: p95 383ms2026-08-27 UTC: p95 335ms2026-08-28 UTC: p95 405ms2026-08-29 UTC: p95 348ms2026-08-30 UTC: p95 367ms2026-08-31 UTC: p95 512ms2026-09-01 UTC: p95 451ms2026-09-02 UTC: p95 421ms2026-09-03 UTC: p95 500ms2026-09-04 UTC: p95 488ms2026-09-05 UTC: p95 445ms2026-09-06 UTC: p95 357ms2026-09-07 UTC: p95 310ms2026-09-08 UTC: p95 361ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 984ms2026-09-14 UTC: p95 659ms2026-09-15 UTC: p95 503ms2026-09-16 UTC: p95 380ms2026-09-17 UTC: p95 336ms2026-09-18 UTC: p95 321ms2026-09-19 UTC: p95 358ms2026-09-20 UTC: p95 340ms2026-09-21 UTC: p95 387ms2026-09-22 UTC: p95 471ms2026-09-23 UTC: p95 423ms
Aug 25Sep 8Sep 23
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 957ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 997ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.1s2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 928ms2026-09-08 UTC: p95 857ms2026-09-09 UTC: p95 732ms2026-09-10 UTC: p95 766ms2026-09-11 UTC: p95 982ms2026-09-12 UTC: p95 830ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 793ms2026-09-16 UTC: p95 882ms2026-09-17 UTC: p95 903ms2026-09-18 UTC: p95 886ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 962ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.3s
Aug 25Sep 8Sep 23
US-Central
552msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 659ms2026-09-04 UTC: p95 700ms2026-09-05 UTC: p95 653ms2026-09-06 UTC: p95 548ms2026-09-07 UTC: p95 519ms2026-09-08 UTC: p95 507ms2026-09-09 UTC: p95 516ms2026-09-10 UTC: p95 453ms2026-09-11 UTC: p95 374ms2026-09-12 UTC: p95 441ms2026-09-13 UTC: p95 489ms2026-09-14 UTC: p95 370ms2026-09-15 UTC: p95 463ms2026-09-16 UTC: p95 531ms2026-09-17 UTC: p95 430ms2026-09-18 UTC: p95 465ms2026-09-19 UTC: p95 518ms2026-09-20 UTC: p95 472ms2026-09-21 UTC: p95 469ms2026-09-22 UTC: p95 463ms2026-09-23 UTC: p95 552ms
Aug 25Sep 8Sep 23
Canada
678msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 601ms2026-09-04 UTC: p95 857ms2026-09-05 UTC: p95 721ms2026-09-06 UTC: p95 573ms2026-09-07 UTC: p95 571ms2026-09-08 UTC: p95 651ms2026-09-09 UTC: p95 544ms2026-09-10 UTC: p95 748ms2026-09-11 UTC: p95 631ms2026-09-12 UTC: p95 602ms2026-09-13 UTC: p95 736ms2026-09-14 UTC: p95 698ms2026-09-15 UTC: p95 630ms2026-09-16 UTC: p95 626ms2026-09-17 UTC: p95 630ms2026-09-18 UTC: p95 671ms2026-09-19 UTC: p95 613ms2026-09-20 UTC: p95 583ms2026-09-21 UTC: p95 688ms2026-09-22 UTC: p95 697ms2026-09-23 UTC: p95 678ms
Aug 25Sep 8Sep 23
UK
606msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 413ms2026-09-04 UTC: p95 432ms2026-09-05 UTC: p95 367ms2026-09-06 UTC: p95 470ms2026-09-07 UTC: p95 389ms2026-09-08 UTC: p95 619ms2026-09-09 UTC: p95 322ms2026-09-10 UTC: p95 455ms2026-09-11 UTC: p95 336ms2026-09-12 UTC: p95 314ms2026-09-13 UTC: p95 332ms2026-09-14 UTC: p95 324ms2026-09-15 UTC: p95 314ms2026-09-16 UTC: p95 417ms2026-09-17 UTC: p95 380ms2026-09-18 UTC: p95 317ms2026-09-19 UTC: p95 335ms2026-09-20 UTC: p95 348ms2026-09-21 UTC: p95 349ms2026-09-22 UTC: p95 365ms2026-09-23 UTC: p95 606ms
Aug 25Sep 8Sep 23
Southeast Asia
1.5sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.6s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 981ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 988ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 927ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.5s
Aug 25Sep 8Sep 23
Australia
1.7sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.5s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.7s
Aug 25Sep 8Sep 23
South America
1.1sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, 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 651ms2026-09-05 UTC: p95 820ms2026-09-06 UTC: p95 819ms2026-09-07 UTC: p95 662ms2026-09-08 UTC: p95 647ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s
Aug 25Sep 8Sep 23

Is it Amazon, 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 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: 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: 923msstatus code: 200checked: Sep 23, 2026, 9:00 AM 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
      Operationallatency: 477msstatus code: 200checked: Sep 23, 2026, 9:05 AM 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
      Operationallatency: 510msstatus code: 200checked: Sep 23, 2026, 8:58 AM 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
      Operationallatency: 481msstatus code: 200checked: Sep 23, 2026, 8:49 AM 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
    Operationallatency: 700msstatus code: 200checked: Sep 23, 2026, 9:05 AM 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 293msstatus code: 200checked: Sep 23, 2026, 9:07 AM 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
      Operationallatency: 356msstatus code: 200checked: Sep 23, 2026, 9:04 AM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 812msstatus code: 200checked: Sep 23, 2026, 9:05 AM 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
      Operationallatency: 1057msstatus code: 200checked: Sep 23, 2026, 8:51 AM 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
      Operationallatency: 1505msstatus code: 200checked: Sep 23, 2026, 8:48 AM 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 outages

No outages on record yet for Amazon.

measured 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 measurements and Amazon's own claim at the time, side by side.

Full availability history for Amazon: 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 Amazon, and again when they can reach it again. That is our own measurement from ten regions, not Amazon'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

Amazon uptime measured by RealUptimeLive, from this page's own readings.
[![Amazon uptime measured by RealUptime](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 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 Amazon's SLA implies, from our measurement

At or above your target

We measured none of downtime for Amazon over the last 30 days, which is 100% 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.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Amazon; the name identifies what we measured, 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 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.