All Systems Operational
Uptime over the past 90 days. View historical uptime.
pro-us-east-1 Operational
90 days ago
100.0 % uptime
Today
Master API Service Operational
90 days ago
100.0 % uptime
Today
Application Creation Service Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service Operational
90 days ago
100.0 % uptime
Today
etcd Service Operational
90 days ago
100.0 % uptime
Today
pro-eu-west-1 Operational
90 days ago
100.0 % uptime
Today
Master API Service Operational
90 days ago
100.0 % uptime
Today
Application Creation Service Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service Operational
90 days ago
100.0 % uptime
Today
etcd Service Operational
90 days ago
100.0 % uptime
Today
pro-ap-southeast-2 Operational
90 days ago
100.0 % uptime
Today
Master API Service Operational
90 days ago
100.0 % uptime
Today
Application Creation Service Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service Operational
90 days ago
100.0 % uptime
Today
etcd Service Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage

No incidents or maintenance related to this downtime.

Scheduled Maintenance
CVE-2019-5736 Runc and Docker vulnerability remediation Apr 23, 02:00-08:00 UTC
Clusters will be undergoing maintenance to remediate the runc escape vulnerability: https://access.redhat.com/security/vulnerabilities/runcescape.

As part of maintenance, pods will be migrated from unpatched nodes to patched nodes.

What should you do?
You can minimize the impact on your applications by scaling your services to more than one pod. In general, for applications to be able to continue to service clients, they should be scaled. Some pod workloads are not appropriate for scaling, such as a single-instance, non-replicated database using a persistent volume claim. In this situation, a deployment strategy of 'recreate' will ensure the pod is restarted after migration, although a brief outage will be experienced.

For more information, refer to the following guide:
https://blog.openshift.com/deploying-highly-available-applications-openshift-kubernetes/

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport/

Thank you for choosing Red Hat OpenShift,
OpenShift SRE
Posted on Apr 18, 07:14 UTC
CVE-2019-5736 Runc and Docker vulnerability remediation Apr 23, 09:00-15:00 UTC
SRE needs to apply pending security updates, especially runc and docker:

https://access.redhat.com/security/vulnerabilities/runcescape
https://access.redhat.com/errata/RHSA-2019:0303
https://access.redhat.com/errata/RHSA-2019:0304

This will Apply update security updates and reboot hosts.
Posted on Apr 17, 15:02 UTC
pro-ap-southeast-2 - Imagestream and template updates Apr 23, 16:00-18:00 UTC
The OpenShift Online Pro cluster, pro-ap-southeast-2, is scheduled to undergo maintenance of templates and imagestreams. The maintenance will start at 16:00 UTC on Apr 23, 2019 and end at approximately 18:00 UTC on Apr 23, 2019. Applications using the following imagestreams will be automatically upgraded:

jboss-eap64-openshift-rhel7
jboss-eap70-openshift-rhel7
jboss-eap71-openshift-rhel7
jenkins-rhel7
mysql-rhel7
php-rhel7
redhat-sso-cd-openshift-rhel7
redhat-sso72-openshift-rhel7
redhat-sso73-openshift-rhel7
wildfly-centos7
datagrid-service
datagrid71-basic
datagrid71-https
datagrid72-https
decisionserver64-amq-s2i
eap-cd-basic-s2i
eap-cd-postgresql-persistent-s2i
eap71-amq-persistent-s2i
eap71-basic-s2i
eap71-https-s2i
eap71-postgresql-persistent-s2i
eap71-sso-s2i
jenkins-persistent
jws31-tomcat7-https-s2i
jws31-tomcat8-https-s2i
jws31-tomcat8-mysql-persistent-s2i
jws50-tomcat9-https-s2i
jws50-tomcat9-mysql-persistent-s2i
processserver64-amq-mysql-s2i
processserver64-basic-s2i
rhdm73-optaweb-employee-rostering
rhpam73-managed
rhpam72-prod
sso-cd-x509-https
sso72-x509-https

What should you do?
To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.

https://docs.openshift.com/container-platform/3.11/dev_guide/deployments/basic_deployment_operations.html#image-change-trigger

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport/

Thank you for choosing Red Hat OpenShift Online,
OpenShift SRE
Posted on Apr 17, 18:51 UTC
Past Incidents
Apr 22, 2019

No incidents reported today.

Apr 21, 2019

No incidents reported.

Apr 20, 2019

No incidents reported.

Apr 19, 2019

No incidents reported.

Apr 18, 2019

No incidents reported.

Apr 17, 2019
pro-ap-southeast-2 - CVE-2019-5736 Runc and Docker vulnerability remediation
Completed - Runc escape remediation for pro-ap-southeast-2 has been successfully completed.

CVE details: https://access.redhat.com/security/cve/cve-2019-5736
Public announcement: https://seclists.org/oss-sec/2019/q1/119


Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Apr 17, 16:29 UTC
In progress - Scheduled maintenance is currently starting. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 17, 16:00 UTC
Scheduled - Clusters will be undergoing maintenance to remediate the runc escape vulnerability: https://access.redhat.com/security/vulnerabilities/runcescape.

As part of maintenance, pods will be migrated from unpatched nodes to patched nodes.

What should you do?
You can minimize the impact on your applications by scaling your services to more than one pod. In general, for applications to be able to continue to service clients, they should be scaled. Some pod workloads are not appropriate for scaling, such as a single-instance, non-replicated database using a persistent volume claim. In this situation, a deployment strategy of 'recreate' will ensure the pod is restarted after migration, although a brief outage will be experienced.

For more information, refer to the following guide:
https://blog.openshift.com/deploying-highly-available-applications-openshift-kubernetes/

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport/

Thank you for choosing Red Hat OpenShift Dedicated,
OpenShift SRE
Apr 16, 18:37 UTC
CVE-2019-5736 Runc and Docker vulnerability remediation
Completed - Scheduled maintenance has been cancelled. We will re-schedule this maintenance if necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 17, 15:01 UTC
Scheduled - SRE needs to apply pending security updates, especially runc and docker:

https://access.redhat.com/security/vulnerabilities/runcescape
https://access.redhat.com/errata/RHSA-2019:0303
https://access.redhat.com/errata/RHSA-2019:0304

This will Apply update security updates and reboot hosts.
Apr 17, 07:58 UTC
Apr 16, 2019
pro-ap-southeast-2 - CVE-2019-5736 Runc and Docker vulnerability remediation
Completed - Scheduled maintenance has been cancelled. We will re-schedule this maintenance if necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 16, 18:29 UTC
Scheduled - Clusters will be undergoing maintenance to remediate the runc escape vulnerability: https://access.redhat.com/security/vulnerabilities/runcescape.

As part of maintenance, pods will be migrated from unpatched nodes to patched nodes.

What should you do?
You can minimize the impact on your applications by scaling your services to more than one pod. In general, for applications to be able to continue to service clients, they should be scaled. Some pod workloads are not appropriate for scaling, such as a single-instance, non-replicated database using a persistent volume claim. In this situation, a deployment strategy of 'recreate' will ensure the pod is restarted after migration, although a brief outage will be experienced.

For more information, refer to the following guide:
https://blog.openshift.com/deploying-highly-available-applications-openshift-kubernetes/

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport/

Thank you for choosing Red Hat OpenShift Dedicated,
OpenShift SRE
Apr 16, 18:19 UTC
pro-us-east-1 remove service ELBs
Completed - Cluster maintenance for pro-us-east-1 is complete.
Apr 16, 16:43 UTC
In progress - Scheduled maintenance is currently starting. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 16, 16:00 UTC
Scheduled - Infrastructure maintenance - SRE has identified an issue with AWS permissions and OpenShift service objects on this cluster.

SRE will update OpenShift service objects with corrected permissions.

This maintenance is not expected to cause any interruption of service.
Apr 5, 14:55 UTC
pro-eu-west-1 remove service ELBs
Completed - Cluster maintenance for pro-eu-west-1 is complete.
Apr 16, 16:20 UTC
In progress - Scheduled maintenance is currently starting. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 16, 16:02 UTC
Scheduled - Infrastructure maintenance - SRE has identified an issue with AWS permissions and OpenShift service objects on this cluster.

SRE will update OpenShift service objects with corrected permissions.

This maintenance is not expected to cause any interruption of service.
Apr 5, 14:55 UTC
pro-ap-southeast-2 remove service ELBs
Completed - Cluster maintenance for pro-ap-southeast-2 is complete.
Apr 16, 15:09 UTC
In progress - Scheduled maintenance is currently starting. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Apr 16, 15:05 UTC
Scheduled - Infrastructure maintenance - SRE has identified an issue with AWS permissions and OpenShift service objects on this cluster.

SRE will update OpenShift service objects with corrected permissions.

This maintenance is not expected to cause any interruption of service.
Apr 5, 14:54 UTC
Apr 15, 2019
Webconsole issues on online-stg cluster
Resolved - This issue has been fixed.

Thank you for using OpenShift,
SRE
Apr 15, 15:24 UTC
Investigating - SRE has identified an issue regarding master nodes of online-stg cluster. This issue is now being fixed.

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport

Thank you for choosing Red Hat OpenShift Online Pro,
OpenShift SRE
Apr 15, 12:17 UTC
Apr 14, 2019

No incidents reported.

Apr 13, 2019

No incidents reported.

Apr 12, 2019

No incidents reported.

Apr 11, 2019

No incidents reported.

Apr 10, 2019

No incidents reported.

Apr 9, 2019

No incidents reported.

Apr 8, 2019

No incidents reported.

← Incident History Powered by Statuspage