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

Affected components

• Confluent Cloud

1. resolvedSep 16, 2026, 01:21 UTC

   This incident has been resolved.

2. monitoringSep 16, 2026, 00:22 UTC

   The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC).

3. identifiedSep 16, 2026, 00:00 UTC

   The issue has been identified and a fix is being implemented.

4. investigatingSep 15, 2026, 23:59 UTC

   Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue is fully mitigated, whichever happens first.

What APIStatus.watch saw

• Sep 16, 2026, 00:00 UTCoperational → degraded
• Sep 16, 2026, 00:25 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• OpenAI: Elevated errors with gpt-image-2.5-flareMajor · Sep 15, 2026, 23:50 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Telnyx: Outbound Messaging LatencyMinor · Sep 15, 2026, 15:27 UTC
• ClickHouse Cloud: ClickPipes failing on Kinesis in AWS us-east-1Minor · Sep 15, 2026, 18:57 UTC
• Telnyx: SMS Delivery — Encoding Issues on Outbound Messages to T-MobileMinor · Sep 15, 2026, 21:57 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history