Confluent: Schema Registry Service Issue
Timeline of updates
- resolved
This issue is intermittent and only when attempting to register Schemas from the front-end. Clients who are accessing Schema Registry via API keys (eg regular application integrations), are unaffected. We have a ticket filed and will prioritize it and fix it. If you are affected by this issue and need urgent help, please raise an escalation with our Customer Support, and have them reference CC-4100-CAAS-3284. As a work-around, you can keep re-trying the Schema Registration repeatedly until it succeeds.
From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Confluent, started 2019-04-27 22:54 UTC, resolved after 56 min, 1 update(s).
- Title
- Schema Registry Service Issue
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/3r6fwbqtwn2j
Confluent profileRecent Confluent incidentsAll outages on April 27, 2019Confluent in April 2019MarkdownJSON