During a recent planned maintenance activity for IBM Cloud Databases for Redis, an automatic failover occurred and caused temporary application impact.

The maintenance was treated as a normal service operation and no customer notification was provided.

Although the maintenance completed successfully, it caused customer impact on our services and required operational investigation and root cause analysis.

We would like IBM Cloud to provide an optional notification mechanism for maintenance activities that may trigger failover events, node restarts, topology changes, or temporary connectivity impacts.

This would help customers prepare monitoring activities, validate resiliency designs, reduce unnecessary incident investigations, and improve operational readiness.