Vendor reports: degradedResolved · vendor status “resolved”Official status API

Kafka consumer and producer degradation in Azure spaincentral

Reported by Confluent Cloud · Data & Analytics · source last read just now

Official source (opens in a new tab)
Vendor start
Jun 29, 2026, 17:44 UTC
Vendor's clock
Resolved
Jun 29, 2026, 20:36 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 52 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Confluent Cloud reports degraded: "Kafka consumer and producer degradation in Azure spaincentral".[E1, E2]
  • The vendor marked it resolved at 2026-06-29 20:36 UTC.[E3, E7]

Affected products and regions

  • Components: Confluent Cloud.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-06-29 20:36 UTC · summary s1, evidence ba43c29f2fa16be7

Evidence (7)
  1. E1Confluent Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Kafka consumer and producer degradation in Azure spaincentral". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-29 17:44 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Confluent Cloud. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-06-29 20:36 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Confluent Cloud

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Confluent Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jun 29, 2026, 17:44 UTCVendor-reported startVendor time
  2. Jun 29, 2026, 20:36 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.