Skip to main content
Vendor reliability

Vendor record

AWS

Vendor reports Major Outage

Checked

Front door check counts and AWS’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against AWS in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every AWS product, region or your app worked.

How we count front door checks

AWS says

Incident posts from AWS’s status page, with its titles, impact levels and times. They say what AWS chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

30

incidents AWS posted, last 1 year

Median recorded duration: 2h 15m. From 25 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Increased Connectivity issues in US-EAST-1

    Minor

    Started, per AWS

    Closed in our record(2h 15m)

    AWS’s post
  • Elevated API issues and Launch Failures

    Minor

    Started, per AWS

    Closed in our record(5h 30m)

    AWS’s post
  • Elevated Launch Failures

    Minor

    Started, per AWS

    Closed in our record(2h 21m)

    AWS’s post
  • Increased invoke error rates

    Not specified

    Started, per AWS

    Closed in our record

    AWS’s post
  • Elevated packet loss

    Minor

    Started, per AWS

    Closed in our record(2h 41m)

    AWS’s post
15 older records
  • Increased Error Rates

    Minor

    Started, per AWS

    Closed in our record(57m)

    AWS’s post
  • Increased API Error Rates

    Minor

    Started, per AWS

    Closed in our record(2h 17m)

    AWS’s post
  • Increased Error Rates

    Minor

    Started, per AWS

    Closed in our record(37m)

    AWS’s post
  • Increased Error Rates

    Minor

    Started, per AWS

    Closed in our record(3h 32m)

    AWS’s post
  • Increased Packet loss

    Minor

    Started, per AWS

    Closed in our record(3d)

    AWS’s post
  • Elevated Packet Loss

    Minor

    Started, per AWS

    Closed in our record(1h 21m)

    AWS’s post
  • Connectivity Issues

    Minor

    Started, per AWS

    Closed in our record(1h 21m)

    AWS’s post
  • Inaccurate Estimated Billing Data

    Minor

    Started, per AWS

    Closed in our record(1d 5h)

    AWS’s post
  • Increased 5xx Errors

    Major

    Started, per AWS

    Closed in our record(3h 37m)

    AWS’s post
  • Elevated connectivity issues with a single Avalability zone

    Minor

    Started, per AWS

    Closed in our record(2h 13m)

    AWS’s post
  • Increased Launch Template API Error Rates

    Minor

    Started, per AWS

    Closed in our record(2h 7m)

    AWS’s post
  • Increased Error Rates and Latencies

    Minor

    Started, per AWS

    Closed in our record(51m)

    AWS’s post
  • Fable 5 and Mythos 5 Access

    Minor

    Started, per AWS

    Closed in our record(2d 16h)

    AWS’s post
  • Internet Connectivity Issues

    Minor

    Started, per AWS

    Closed in our record

    AWS’s post
  • Increased API Error Rates

    Minor

    Started, per AWS

    Closed in our record(34m)

    AWS’s post

Your code, your dependencies

See which of your code paths call AWS

Connect GitHub or GitLab to find where your public or private repository uses AWS. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add AWS status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · AWSStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/aws?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="AWS status badge"></iframe>

Frequently Asked Questions

Is AWS currently down?

AWS's latest recorded status is Major Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did AWS last have an outage?

The most recent closed incident record began 1 day ago and spans 2h 15m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for AWS?

No. CheckUpstream does not run front door checks against AWS. The incident history on this page is what AWS reported, not a measure of how often it was available.

How do I monitor AWS in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

What does AWS do?

AWS, or Amazon Web Services, is a cloud computing platform that provides on-demand infrastructure and managed services for building, deploying, and operating software. It is used by developers, operations teams, and enterprises to run applications, store data, and manage networking and security. Its main product surfaces are web-based consoles, APIs, and command-line tools across a large catalog of cloud services.

How does CheckUpstream track AWS?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.