Skip to content

Outage tracker / Confluent Cloud

Is Confluent Cloud down?

Short linkrlup.io/down/confluent

I'm having a problem

Vendor reports no incidentWhat Confluent Cloud reports

Confluent Cloud reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:11 UTC.

Confluent Cloud's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Confluent Cloud pass from all 4 regions we check.

As of Nov 5, 2026, 3:27 PM UTC, RealUptime's checks of Confluent Cloud passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:27 PM UTC
US-East2234 msChecks passing
US-West1739 msChecks passing
Europe2697 msChecks passing
Asia-Pacific1910 msChecks passing
their status pagetheir claim, not our reading

Confluent Cloud reports: Partial outage (“Partial System Outage”)

from Confluent Cloud's own status page, checked Nov 5, 2026, 2:26 PM UTC
Confluent Cloud's status page reports Partial System Outage. Our checks of Confluent Cloud currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Confluent Cloud's own component breakdown, as they publish it

  • Confluent CloudPartial outage

These are Confluent Cloud's components, named and scored by Confluent Cloud. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Confluent Cloud's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Confluent Cloud response time, by region

US-East
3.9sp95 · 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-11-02 UTC: p95 4.3s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 4.1s2026-11-05 UTC: p95 3.9s
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-11-02 UTC: p95 4.2s2026-11-03 UTC: p95 4.5s2026-11-04 UTC: p95 4.2s2026-11-05 UTC: p95 4.1s
Oct 7Oct 21Nov 5
Europe
3.5sp95 · 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-11-02 UTC: p95 3.7s2026-11-03 UTC: p95 4.1s2026-11-04 UTC: p95 2.9s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5
Asia-Pacific
6.2sp95 · 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-11-02 UTC: p95 7.8s2026-11-03 UTC: p95 5.6s2026-11-04 UTC: p95 7.2s2026-11-05 UTC: p95 6.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on Confluent Cloud

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

What we measured, function by function

Confluent Cloud 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: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when Confluent Cloud reports an incident on its status page, and again when it reports it resolved.

Get an email when Confluent Cloud reports an incident

Email me when Confluent Cloud reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Confluent Cloud's own statement from its status page, with our regional reading beside it.

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
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 2234msstatus code: 200checked: Nov 5, 2026, 3:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Confluent Cloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1739msstatus code: 200checked: Nov 5, 2026, 3:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Confluent Cloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionConfluent Cloud is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionConfluent Cloud is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionConfluent Cloud is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 2697msstatus code: 200checked: Nov 5, 2026, 3:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Confluent Cloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionConfluent Cloud is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1910msstatus code: 200checked: Nov 5, 2026, 3:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Confluent Cloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionConfluent Cloud is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionConfluent Cloud is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Confluent Cloud, 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 Confluent Cloud yet, which is not evidence that nothing is wrong.

Recent probe events

Kafka - Increased latency and connectivity issues - Azure - brazilsouth, 2h 9mdeclared on their status page2026-11-05
Multiple Confluent Cloud services are in a degraded state - GCP EU-West2, 3h 41mdeclared on their status page2026-10-20
Delay in Kafka cluster provisioning, 3h 49mdeclared on their status page2026-10-16
Confluent Cloud Console (UI) degraded functionality, 2h 45mdeclared on their status page2026-10-15
Possible outage in AWS us-east-1, 56mdeclared on their status page2026-10-09
Experiencing high error rate in AZURE in West Europe region, 10h 33mdeclared on their status page2026-10-09
Experiencing high error rate in AZURE in Germany West Central region, 56mdeclared on their status page2026-10-08
Missing Metrics on Confluent Cloud, 1mdeclared on their status page2026-09-27

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

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

Full check history for Confluent Cloud: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

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

What we check

secondary
https://www.confluent.io/
secondary
https://status.confluent.cloud/
primaryfunctional: live API
https://api.confluent.cloud/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.confluent.cloud

RealUptime is not affiliated with Confluent Cloud; the name identifies what we checked, and nothing here speaks for Confluent Cloud's own team. We send a single web request to Confluent Cloud from 4 regions on our own schedule and time the response. We do not see inside Confluent Cloud's systems, do not use an account or real transaction, and are not the same signal Confluent Cloud's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Confluent Cloud 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. Confluent Cloud operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 3792 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts