Is IBM Cloud Streaming Analytics down?
Current IBM Cloud Streaming Analytics status is UP

What are we changing?The Streaming Analytics service will undergo scheduled maintenance to the Kubernetes environments. This maintenance completes a portion of the September 11, 2022 maintenance which was delayed. Why are we making this change?This change will apply Kubernetes security updates and patches to the underlying infrastructure of the service for improved security and quality.How will it impact the environment?During the maintenance period, the service might experience small periods of disruption to instances and applications (depending on the nature of the application). Customer applications will be moved from one container to another (processing elements are restarted). At the conclusion of the maintenance process, you should not need to restart applications.For information on how to make your application highly available, see the High availability and disaster recovery article.Maintenance Duration: 120 minutesDisruption Duration: 120 minutes

What are we changing?The Streaming Analytics service will undergo scheduled maintenance to the Kubernetes environments. This maintenance is rescheduled from August 30, 2022. Why are we making this change?This change will apply Kubernetes security updates and patches to the underlying infrastructure of the service for improved security and quality.How will it impact the environment?During the maintenance period, the service might experience small periods of disruption to instances and applications (depending on the nature of the application). Customer applications will be moved from one container to another (processing elements are restarted). At the conclusion of the maintenance process, you should not need to restart applications.For information on how to make your application highly available, see the High availability and disaster recovery article.Maintenance Duration: 120 minutesDisruption Duration: 120 minutes

What are we changing?The Streaming Analytics service will undergo scheduled maintenance to the Kubernetes environments.Why are we making this change?This change will apply Kubernetes security updates and patches to the underlying infrastructure of the service for improved security and quality.How will it impact the environment?During the maintenance period, the service might experience small periods of disruption to instances and applications (depending on the nature of the application). Customer applications will be moved from one container to another (processing elements are restarted). At the conclusion of the maintenance process, you should not need to restart applications.For information on how to make your application highly available, see the High availability and disaster recovery article.Maintenance Duration: 120 minutesDisruption Duration: 120 minutes

What are we changing?The Streaming Analytics service will undergo scheduled maintenance to the Kubernetes environments.Why are we making this change?This change will apply Kubernetes security updates and patches to the underlying infrastructure of the service for improved security and quality.How will it impact the environment?During the maintenance period, the service might experience small periods of disruption to instances and applications (depending on the nature of the application). Customer applications will be moved from one container to another (processing elements are restarted). At the conclusion of the maintenance process, you should not need to restart applications.For information on how to make your application highly available, see the High availability and disaster recovery article.Maintenance Duration: 120 minutesDisruption Duration: 120 minutes

What are we changing?The Streaming Analytics service will undergo scheduled maintenance to the Kubernetes environments.Why are we making this change?This change will apply Kubernetes security updates and patches to the underlying infrastructure of the service for improved security and quality.How will it impact the environment?During the maintenance period, the service might experience small periods of disruption to instances and applications (depending on the nature of the application). Customer applications will be moved from one container to another (processing elements are restarted). At the conclusion of the maintenance process, you should not need to restart applications.For information on how to make your application highly available, see the High availability and disaster recovery article.Maintenance Duration: 120 minutesDisruption Duration: 2 minutes