Skip to content

Outage tracker / Confluent Cloud / In the US

Is Confluent Cloud down in the US?

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 16:09 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 passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Confluent Cloud at Nov 5, 2026, 4:13 PM UTC.

Over the last 24 hours we completed 256 checks from Ashburn and San Jose and 256 answered cleanly, 100.00% availability.

Of the 2 other regions we check Confluent Cloud from, all 2 read checks passing right now.

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

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

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

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing114 checks in 24h, 100.00%

Last checked Nov 5, 2026, 4:13 PM UTC.

Confluent Cloud from Ashburn and San Jose over the last 30 days

Over the last 30 days, Confluent Cloud answered our Ashburn probe in 2,754 ms on average, and 1 check in 20 took longer than 3,984 ms.

Over the last 30 days, Confluent Cloud answered our San Jose probe in 2,954 ms on average, and 1 check in 20 took longer than 4,267 ms.

Ranked by average response time across the 4 cities we check Confluent Cloud from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 2,140 ms and Tokyo slowest at 4,389 ms.

From Ashburn and San Jose we ran 782 checks of Confluent Cloud in 4 days, and 781 answered cleanly: 99.87% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 249 checks.

In Ashburn local time (EST), Confluent Cloud was slowest around 12 AM, at 3,689 ms on average over the last 14 days, and quickest around 10 AM, at 2,299 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5172100.00%2,986 ms
Wed, Nov 4255100.00%2,702 ms
Tue, Nov 324999.59%2,796 ms
Mon, Nov 2106100.00%3,053 ms

Confluent Cloud outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Confluent Cloud outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Confluent Cloud from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 101 checks
TokyoChecks passing100.00% of 61 checks

Other countries we check Confluent Cloud from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Confluent Cloud's public endpoints. They are not user reports, and they are not Confluent Cloud's own status page.

See Confluent Cloud's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Confluent Cloud has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

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