Skip to main content
Vendor reliability

Vendor record

Confluent

Vendor reports Operational

Checked

Front door check counts and Confluent’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 Confluent endpoint and count the checks that got the answer it is documented to give.

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

    Endpoint checked
    api.confluent.cloud
    Scope
    apiNo vendor region
    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 Confluent product, region or your app worked.

How we count front door checks

Confluent says

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

9

incidents Confluent posted, last 30 days

Median recorded duration: 7h 20m. From 9 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Delay in Kafka cluster provisioning

    Minor

    Started, per Confluent

    Closed in our record(7h 20m)

    Confluent’s post

  • Confluent Cloud Console (UI) degraded functionality

    Not specified

    Started, per Confluent

    Closed in our record(2h 48m)

    Confluent’s post

  • Possible outage in AWS us-east-1

    Major

    Started, per Confluent

    Closed in our record(57m)

    Confluent’s post

  • Experiencing high error rate in AZURE in West Europe region

    Major

    Started, per Confluent

    Closed in our record(20h 5m)

    Confluent’s post

  • Experiencing high error rate in AZURE in Germany West Central region

    Major

    Started, per Confluent

    Closed in our record(1h)

    Confluent’s post
15 older records

  • Elevated error rates in Azure East US

    Minor

    Started, per Confluent

    Closed in our record(13h 9m)

    Confluent’s post

  • Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

    Major

    Started, per Confluent

    Closed in our record(11h 32m)

    Confluent’s post

  • Elevated error rates in Azure Germany West Central region

    Major

    Started, per Confluent

    Closed in our record(4h 51m)

    Confluent’s post

  • Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

    Major

    Started, per Confluent

    Closed in our record(9h 35m)

    Confluent’s post

  • Multiple Confluent Cloud services are in a degraded state - All regions

    Major

    Started, per Confluent

    Closed in our record(1h 25m)

    Confluent’s post

  • Connectivity degradation - AWS us-east-1

    Major

    Started, per Confluent

    Closed in our record(17h 8m)

    Confluent’s post

  • Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1

    Minor

    Started, per Confluent

    Closed in our record(1d 5h)

    Confluent’s post

  • Investigating Elevated Errors in GCP us-central1

    Minor

    Started, per Confluent

    Closed in our record(48m)

    Confluent’s post

  • Elevated error rates and latencies in Azure Southeast Asia region

    Major

    Started, per Confluent

    Closed in our record(3h 12m)

    Confluent’s post

  • Elevated error rates and latency in GCP us-west1

    Major

    Started, per Confluent

    Closed in our record(3h 10m)

    Confluent’s post

  • Flink statements degraded in GCP us-central1 region

    Minor

    Started, per Confluent

    Closed in our record(3h)

    Confluent’s post

  • Kafka cluster performance degradation for clusters in AWS region eu-central-1

    Minor

    Started, per Confluent

    Closed in our record(13h 46m)

    Confluent’s post

  • Confluent Cloud Metrics API is currently experiencing elevated latency and error rates.

    Not specified

    Started, per Confluent

    Closed in our record(1h 44m)

    Confluent’s post

  • Kafka consumer and producer degradation in Azure spaincentral

    Minor

    Started, per Confluent

    Closed in our record(2h 55m)

    Confluent’s post

  • Confluent Cloud Metrics API is currently experiencing elevated error rates

    Minor

    Started, per Confluent

    Closed in our record(1h 2m)

    Confluent’s post

Your code, your dependencies

See which of your code paths call Confluent

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

Connect a repository

Free to start. No credit card.

Use this record on your site

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

Frequently Asked Questions

Is Confluent currently down?

Confluent's latest recorded status is Operational. 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 Confluent last have an outage?

The most recent closed incident record began earlier today and spans 7h 20m. 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 Confluent?

No. CheckUpstream checks Confluent’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 Confluent 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 Confluent do?

Confluent provides a managed cloud platform for Apache Kafka and related streaming data services. It is used by developers and platform teams to build, move, and process real-time event data between applications and infrastructure. The main product surfaces are a hosted web console, cloud APIs, and managed service endpoints for Kafka clusters, connectors, and stream processing.

How does CheckUpstream track Confluent?

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.

Related vendors