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
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Mar 19, 2019

No incidents reported today.

Mar 18, 2019

No incidents reported.

Mar 17, 2019

No incidents reported.

Mar 16, 2019

No incidents reported.

Mar 15, 2019

No incidents reported.

Mar 14, 2019

No incidents reported.

Mar 13, 2019

No incidents reported.

Mar 12, 2019

No incidents reported.

Mar 11, 2019

No incidents reported.

Mar 10, 2019

No incidents reported.

Mar 9, 2019

No incidents reported.

Mar 8, 2019
Completed - The scheduled maintenance has been completed.
Mar 8, 10:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 8, 09:31 UTC
Update - We will be undergoing scheduled maintenance during this time.
Mar 8, 09:27 UTC
Scheduled - 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/.
Mar 8, 09:27 UTC
Mar 7, 2019
Completed - The scheduled maintenance has been completed.
Mar 7, 16:15 UTC
Update - The master node Infrastructure maintenance is still in-progress and is taking longer than expected, current estimate for completion is 18:00 UTC.
Mar 7, 15:52 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 7, 15:15 UTC
Scheduled - Scheduled maintenance was delayed but is now back in progress. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 7, 15:11 UTC
Update - Master node Infrastructure maintenance on pro-us-east-1 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 8, 07:30 UTC
Completed - The master node Infrastructure maintenance for pro-us-east-1 will need to be rescheduled due to a separate logging issue which SRE are currently working on.
Mar 7, 13:59 UTC
Update - The master node Infrastructure maintenance is still in-progress and is taking longer than expected, current estimate for completion is 16:00 UTC.
Mar 7, 13:55 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/.
Mar 7, 13:00 UTC
Scheduled - SRE is performing master node Infrastructure maintenance on this cluster.

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
Mar 5, 14:19 UTC
Mar 6, 2019
Resolved - Remove compute nodes for pro-ap-southeast-2 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 6, 19:06 UTC
Investigating - Remove compute nodes

SRE is removing compute nodes from the cluster. Running applications may be impacted if they migrate for existing nodes to new 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
Mar 6, 18:50 UTC
Resolved - Add compute nodes for pro-eu-west-1 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 6, 18:12 UTC
Investigating - Add compute nodes

SRE is adding compute nodes to the cluster. Running applications may be impacted if they migrate for existing nodes to new 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/
Mar 6, 17:57 UTC
Completed - Master node Infrastructure maintenance on pro-eu-west-1 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 6, 14:22 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/.
Mar 6, 14:00 UTC
Scheduled - SRE is performing master node Infrastructure maintenance on this cluster.

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
Mar 5, 14:18 UTC
Mar 5, 2019
Completed - Master node Infrastructure maintenance on pro-ap-southeast-2 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 5, 14:26 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/.
Mar 5, 14:01 UTC
Scheduled - SRE is performing master node Infrastructure maintenance on this cluster.

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
Mar 4, 19:00 UTC