All Systems Operational
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
Past Incidents
Nov 15, 2018

No incidents reported today.

Nov 14, 2018

No incidents reported.

Nov 13, 2018

No incidents reported.

Nov 12, 2018
Completed - The upgrade is complete.
Nov 12, 19: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/.
Nov 12, 17:49 UTC
Scheduled - The OpenShift Pro cluster, pro-us-east-1, is scheduled to upgrade starting at 16:00 UTC on Nov 12, 2018 and ending at approximately 00:00 UTC on Nov 13, 2018. The upgrade process is engineered to disrupt applications as little as possible, but brief outages may occur during the upgrade. For short periods of time, developers may be unable to create new applications or interact with existing applications. In addition to the OpenShift version upgrade, the following imagestreams will also be updated:

apicast-gateway
dotnet
dotnet-runtime
eap-cd-openshift
java
jboss-datagrid65-client-openshift
jboss-datagrid65-openshift
jboss-datagrid71-client-openshift
jboss-datagrid71-openshift
jboss-datagrid72-openshift
jboss-eap64-openshift
jboss-eap70-openshift
jboss-eap71-openshift
jboss-webserver30-tomcat7-openshift
jboss-webserver30-tomcat8-openshift
jboss-webserver31-tomcat7-openshift
jboss-webserver31-tomcat8-openshift
nodejs
perl
php
python
redhat-openjdk18-openshift
redhat-sso72-openshift
ruby

To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.

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

You can minimize the impact on your applications by scaling your services to more than one(1) 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.
Oct 29, 20:04 UTC
Completed - The upgrade is complete.
Nov 12, 18:46 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/.
Nov 12, 17:49 UTC
Scheduled - The OpenShift Pro cluster, pro-eu-west-1, is scheduled to upgrade starting at 16:00 UTC on Nov 12, 2018 and ending at approximately 00:00 UTC on Nov 13, 2018. The upgrade process is engineered to disrupt applications as little as possible, but brief outages may occur during the upgrade. For short periods of time, developers may be unable to create new applications or interact with existing applications. In addition to the OpenShift version upgrade, the following imagestreams will also be updated:

apicast-gateway
dotnet
dotnet-runtime
eap-cd-openshift
java
jboss-datagrid65-client-openshift
jboss-datagrid65-openshift
jboss-datagrid71-client-openshift
jboss-datagrid71-openshift
jboss-datagrid72-openshift
jboss-eap64-openshift
jboss-eap70-openshift
jboss-eap71-openshift
jboss-webserver30-tomcat7-openshift
jboss-webserver30-tomcat8-openshift
jboss-webserver31-tomcat7-openshift
jboss-webserver31-tomcat8-openshift
nodejs
perl
php
python
redhat-openjdk18-openshift
redhat-sso72-openshift
ruby

To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.

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

You can minimize the impact on your applications by scaling your services to more than one(1) 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.
Oct 29, 20:05 UTC
Completed - The upgrade is complete.
Nov 12, 18:28 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/.
Nov 12, 17:49 UTC
Scheduled - The OpenShift Pro cluster, pro-ap-southeast-2, is scheduled to upgrade starting at 16:00 UTC on Nov 12, 2018 and ending at approximately 00:00 UTC on Nov 13, 2018. The upgrade process is engineered to disrupt applications as little as possible, but brief outages may occur during the upgrade. For short periods of time, developers may be unable to create new applications or interact with existing applications. In addition to the OpenShift version upgrade, the following imagestreams will also be updated:

apicast-gateway
dotnet
dotnet-runtime
eap-cd-openshift
java
jboss-datagrid65-client-openshift
jboss-datagrid65-openshift
jboss-datagrid71-client-openshift
jboss-datagrid71-openshift
jboss-datagrid72-openshift
jboss-eap64-openshift
jboss-eap70-openshift
jboss-eap71-openshift
jboss-webserver30-tomcat7-openshift
jboss-webserver30-tomcat8-openshift
jboss-webserver31-tomcat7-openshift
jboss-webserver31-tomcat8-openshift
nodejs
perl
php
python
redhat-openjdk18-openshift
redhat-sso72-openshift
ruby

To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.

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

You can minimize the impact on your applications by scaling your services to more than one(1) 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.
Oct 29, 20:05 UTC
Nov 11, 2018

No incidents reported.

Nov 10, 2018

No incidents reported.

Nov 9, 2018

No incidents reported.

Nov 8, 2018
Resolved - The addition of extra routing capacity has resolved this incident.
Nov 8, 13:21 UTC
Monitoring - SRE has identified many long-lived connections to the OpenShift routers and has added routing capacity to alleviate the load. We will be monitoring the router's performance to confirm the performance improvement.
Nov 5, 14:54 UTC
Update - SRE are still actively investigating this issue.
Nov 2, 20:01 UTC
Update - SRE is actively working the issue and will update this page with more information as it becomes available.
Nov 1, 13:51 UTC
Investigating - SRE has identified an issue with the router pods on this cluster. SRE is actively working the issue and will update this page with more information as it becomes available.
Nov 1, 12:07 UTC
Nov 7, 2018

No incidents reported.

Nov 6, 2018

No incidents reported.

Nov 4, 2018

No incidents reported.

Nov 3, 2018

No incidents reported.