Skip to main content
Vendor reliability

Vendor record

AWS Kinesis

Vendor reports Major Outage

Checked

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

Front door checks

We send a request to a documented AWS Kinesis endpoint and count the checks that got the answer it is documented to give.

  • No clear answer in 24 hours. These counts are from before this check went quiet.

    Front door reachable in 2,620 of 2,620 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    Endpoint checked
    kinesis.ap-southeast-2.amazonaws.com
    Scope
    kinesisap-southeast-2
    First check in this window
    Latest clear answer
  • No clear answer in 24 hours. These counts are from before this check went quiet.

    Front door reachable in 2,620 of 2,620 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    Endpoint checked
    kinesis.eu-west-1.amazonaws.com
    Scope
    kinesiseu-west-1
    First check in this window
    Latest clear answer
  • No clear answer in 24 hours. These counts are from before this check went quiet.

    Front door reachable in 2,619 of 2,619 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    2 more checks gave no clear answer and are not counted.

    Endpoint checked
    kinesis.us-east-1.amazonaws.com
    Scope
    kinesisus-east-1
    First check in this window
    Latest clear answer

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

How we count front door checks

Shorter disruptions

Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.

Independent outage detection for AWS Kinesis: Datadog’s Updog(opens in a new tab)

CheckUpstream is not affiliated with Datadog.

AWS Kinesis says

Incident posts from AWS Kinesis’s status page, with its titles, impact levels and times. They say what AWS Kinesis 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.

AWS does not publish a component catalog for this feed. This page includes an incident only when AWS names this product in the event. A quiet record does not mean the product was available.

0

incidents AWS Kinesis posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • Increased Connectivity Issues

    Minor

    Started, per AWS Kinesis

    Closed in our record(38m)

    AWS Kinesis’s post
  • Increased Error Rates

    Minor

    Started, per AWS Kinesis

    Closed in our record(1h 10m)

    AWS Kinesis’s post
  • Region Availability

    Critical

    Started, per AWS Kinesis

    Latest status AWS Kinesis postedInvestigating. No resolution posted.

    AWS Kinesis’s post
  • Region Availability

    Critical

    Started, per AWS Kinesis

    Latest status AWS Kinesis postedInvestigating. No resolution posted.

    AWS Kinesis’s post
  • Increased Error Rates and Latencies

    Minor

    Started, per AWS Kinesis

    Closed in our record(15h 42m)

    AWS Kinesis’s post

Your code, your dependencies

See which of your code paths call AWS Kinesis

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

Connect a repository

Free to start. No credit card.

Use this record on your site

Add AWS Kinesis 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 · AWS KinesisStatus 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-kinesis?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="AWS Kinesis status badge"></iframe>

Frequently Asked Questions

Is AWS Kinesis currently down?

AWS Kinesis'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 Kinesis last have an outage?

The most recent closed incident record began 204 days ago and spans 38 minutes. 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 Kinesis?

No. CheckUpstream checks AWS Kinesis’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor AWS Kinesis 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.

How does CheckUpstream track AWS Kinesis?

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.