Skip to content
PulseWatchOUTAGE.INTEL
Confluent Cloud logo

Cloud Infrastructure

Is Confluent Cloud down right now?

NormalOfficial status last polled Sep 28, 2026 09:18 UTCwww.confluent.ioOfficial status page

Managed Apache Kafka platform

Are you on the Confluent Cloud team and see something inaccurate? Report it to us. We respond within one business day.

Is Confluent Cloud down right now?

No. Confluent Cloud has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 10:34 UTC

Normal

Confluent Cloud is operating normally

As of Sep 28, 2026 10:34 UTC

No elevated reports in the last 15 minutes. Baseline 4 reports/hour.

Reports 24h

0

Last incident

Sep 26, 2026 19:45 UTC

Trend

0/15m

Baseline

4/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Confluent Cloud.

6

Incident days

24

No recorded incident

42h 15m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Confluent Cloud. Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

6

Days with incidents

2 incidents

Busiest day

42h 15m

Recorded duration

Report volume

0 reports in last 24H

10:30 AM02:00 PM05:30 PM09:00 PM12:30 AM04:00 AM07:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Confluent Cloud outage on September 26 — 12h 5m disruption

Sep 26, 07:40 AM → Sep 26, 07:45 PM · 12h 5m · medium

Confluent Cloud experienced a service disruption that was detected by automated monitoring signals. The incident began on September 26, 2026, at 07:40:32 UTC. The disruption was resolved on September 26, 2026, at 19:45:35 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
12h 5m
until recovery

Impact

The Confluent Cloud service experienced a medium-severity disruption lasting 12 hours and 5 minutes. This incident was identified through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no information regarding specific affected features, regions, or issue types is available from user reports.

Outage timeline

  1. Sep 26, 07:40 AM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Sep 26, 07:40 AM

    Status updated: possible issue

  3. Sep 26, 07:45 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 26, 07:40 AM

    Confluent Cloud status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

94.1%

90-day uptime

97.9%

Calculated from Confluent Cloud's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Confluent Cloud: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/26/2026, 7:40:32 AM · 12h 5m

07:40 AM07:45 PM
Detection9/26/2026, 7:40:32 AM · 2d ago

Detected — medium severity

Confluent Cloud: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

9/23/2026, 12:15:26 PM · 11h 55m

12:15 PM12:10 AM
Detection9/23/2026, 12:15:26 PM · 4d ago

Detected — high severity

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

9/22/2026, 3:19:09 PM · 6h 3m

03:19 PM09:22 PM
Detection9/22/2026, 3:19:09 PM · 5d ago

Detected — high severity

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

9/21/2026, 4:41:13 PM · 9h 56m

04:41 PM02:37 AM
Detection9/21/2026, 4:41:13 PM · 6d ago

Detected — high severity

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

9/16/2026, 12:00:07 AM · 2h 12m

12:00 AM02:12 AM
Detection9/16/2026, 12:00:07 AM · 12d ago

Detected — high severity

Confluent Cloud: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluent Cloud or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Confluent Cloud enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
4
Open threshold
3x

Official site

www.confluent.io