Scheduled Maintenance of Confluent Cloud
On March 21st, 2025, between 1:00 AM and 3:00 AM UTC (6:00 PM and 8:00 PM PDT on March 20th, 2025) Confluent Cloud will undergo scheduled maintenance for an infrastructure upgrade. Once started, the maintenance will last approximately 2 hours. During this time, you will not be able to create, update, or delete Stream Shares via UI/CLI/API and will not be able to create or accept new topic access requests via Data Portal. Your existing clusters, their metrics and the flow of data to and from your producers and consumers will be unaffected.
We appreciate your patience and understanding.
What to expect during the scheduled maintenance period
Stream Shares: During the maintenance window, Stream Share cannot be created, updated, deleted, or redeemed. The UI will show an error message. The API will return an “API unavailable. Please try again later.” message with a 503 status code. CLI will try to retry these requests and will give a timeout error. Reading Stream Shares will not be affected. Any Stream Shares that have already been redeemed will continue to function.
Topic Access Requests via Data portal: During the maintenance window, Access Requests cannot be created, approved, or rejected. Users requesting access to a topic via Data Portal will see an “API unavailable. Please try again later.” error message. Users trying to approve or reject any pending topic access requests will get a 503 status code error. Any topic access requests that have been approved or rejected will not be affected.
The scheduled maintenance will have no impact on any other Control Plane and Data Plane APIs or any of your running Confluent Cloud components; including Kafka clusters, Connectors, ksqlDB, Kafka Streams, Flink and Schema Registry.
What can you do to reduce the impact
You can reduce the impact by planning your Stream Sharing and/or topic access request management operations via the Data Portal to occur before or after this maintenance window.
If you experience any issues outside of what has been described in this document, contact Confluent Support.
Details by scenario
The following table provides more details about what features are impacted and what is available for use during this scheduled maintenance window.
| Scenario | Impact | Mitigation |
| Create, Update, or Delete a Stream Share | Stream Shares cannot be created/updated/deleted during the maintenance window | Plan your Stream Sharing create/update/delete operations before or after the maintenance window. All Stream Sharing management operations will automatically be available once the maintenance is complete. |
| Redeeming an existing Stream Share | Stream Shares cannot be redeemed during the maintenance window. | Plan to redeem Stream Shares before or after the maintenance window. Redeeming Stream Shares will automatically be available once the maintenance is complete. |
| Consumer access to a topic data shared via Stream Sharing | Consumers reading data from a shared topic will not be affected during the maintenance window. | No mitigation required. |
| Create, Approve, or Reject an Access Request | Access Requests for topics cannot be created/approved/rejected during the maintenance window |
Plan to create your Access Requests before or after the maintenance window. Privileged users can also workaround approving access to a topic by manually granting the requesting user the RBAC role to access the topic. This can be done in the Access page of the UI. All Access Request management operations will automatically be available once the maintenance is complete. |
| Access Requests that have been approved or rejected | Access Requests that have already been approved or rejected before the maintenance window will not be affected during the maintenance window. | No mitigation required. |
| Deleting Schema Registry Cluster | Deleting a Schema Registry Cluster may fail for a short time (~5 minutes) during the maintenance window while the infrastructure reboots. | Retry the operation after a few minutes. |
| Deleting Confluent Cloud Environment | Deleting a Confluent Cloud Environment may fail for a short time (~5 minutes) during the maintenance window while the infrastructure reboots. | Retry the operation after a few minutes. |