SDN / route propagation issues on starter-us-east-1a and starter-us-east-1b
Investigating - SRE is aware of and investigating issues related to SDN and route propagation affecting starter-us-east-1a and starter-us-east-1b clusters. Networking on these clusters is currently in a degraded state. We will provide updates as the investigation progresses.
Mar 20, 19:16 UTC
SDN / route propagation issues on starter-us-east-2 and starter-us-east-2a
Investigating - SRE is aware of and investigating issues related to SDN and route propagation affecting starter-us-east-2 and starter-us-east-2a clusters. Networking on these clusters is currently in a degraded state. We will provide updates as the investigation progresses.
Mar 19, 18:59 UTC
Uptime over the past 90 days. View historical uptime.
starter-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
starter-us-east-2 Partial Outage
90 days ago
99.54 % uptime
Today
Master API Service Partial Outage
90 days ago
99.54 % uptime
Today
Application Creation Service Partial Outage
90 days ago
99.54 % uptime
Today
Docker Registry Service Partial Outage
90 days ago
99.54 % uptime
Today
etcd Service Partial Outage
90 days ago
99.54 % uptime
Today
starter-us-west-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
starter-us-east-2a Partial Outage
90 days ago
99.54 % uptime
Today
Master API Service Partial Outage
90 days ago
99.54 % uptime
Today
Application Creation Service Partial Outage
90 days ago
99.54 % uptime
Today
etcd Service Partial Outage
90 days ago
99.54 % uptime
Today
Docker Registry Service Partial Outage
90 days ago
99.54 % uptime
Today
fuse-ignite Operational
90 days ago
99.42 % uptime
Today
Master API Service Operational
90 days ago
100.0 % uptime
Today
Application Creation Service Operational
90 days ago
97.7 % uptime
Today
Docker Registry Service Operational
90 days ago
100.0 % uptime
Today
etcd Service Operational
90 days ago
100.0 % uptime
Today
starter-us-east-1a Partial Outage
Master API Service Partial Outage
Application Creation Service Partial Outage
Docker Registry Service Partial Outage
etcd Service Partial Outage
starter-us-east-1b Partial Outage
Master API Service Partial Outage
Application Creation Service Partial Outage
Docker Registry Service Partial Outage
etcd Service Partial Outage
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.

Past Incidents
Mar 21, 2019

No incidents reported today.

Mar 20, 2019
CVE-2019-5736 (runcescape) remediation for starter-us-east-1a
Resolved - Maintenance on starter-us-east-1a has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 20, 19:14 UTC
Update - The cluster has been upgraded to OpenShift 3.11.82 and CVE remediation steps are in progress.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1a as well.

We are investigating and will provides updates as necessary.
Mar 20, 15:13 UTC
Update - The cluster has been upgraded to OpenShift 3.11.82. We are waiting for ElasticSearch to stabilize before proceeding with the remaining CVE remediation steps.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1a as well.

We are investigating and will provides updates as necessary.
Mar 19, 22:01 UTC
Monitoring - The cluster is being upgraded to OpenShift 3.11.82 as part of the CVE remediation.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1a as well.

We are investigating and will provides updates as necessary.
Mar 19, 13:21 UTC
CVE-2019-5736 (runcescape) remediation for starter-us-east-1b
Resolved - Maintenance on starter-us-east-1b has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 20, 17:34 UTC
Update - The cluster has been upgraded to OpenShift 3.11.82 and CVE remediation steps are in progress.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1b as well.

We are investigating and will provides updates as necessary.
Mar 20, 13:09 UTC
Update - The cluster has been upgraded to OpenShift 3.11.82. We are waiting for ElasticSearch to stabilize before proceeding with the remaining CVE remediation steps.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1b as well.

We are investigating and will provides updates as necessary.
Mar 19, 22:00 UTC
Investigating - The cluster is being upgraded to OpenShift 3.11.82 as part of the CVE remediation.

SRE is also aware of SDN and route propagation issues affecting other starter clusters which could manifest on starter-us-east-1b as well.

We are investigating and will provides updates as necessary.
Mar 18, 20:42 UTC
Mar 18, 2019
CVE-2019-5736 (runcescape) remediation for starter-us-east-1a
Update - Maintenance on starter-us-east-1a has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 20, 19:13 UTC
Completed - The scheduled maintenance has been completed.
Mar 18, 23:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 18, 15:55 UTC
Scheduled - OSIO clusters need to be patched to finish remediation of https://access.redhat.com/security/cve/cve-2019-5736.

SRE is performing 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 18, 15:54 UTC
CVE-2019-5736 (runcescape) remediation for starter-us-east-1b
Update - Maintenance on starter-us-east-1b has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 20, 17:33 UTC
Completed - The scheduled maintenance has been completed.
Mar 18, 16:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 18, 15:55 UTC
Scheduled - OSIO clusters need to be patched to finish remediation of https://access.redhat.com/security/cve/cve-2019-5736.

SRE is performing 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 18, 15:54 UTC
CVE-2019-5736 (runcescape) remediation for starter-us-east-2a
Completed - Maintenance on starter-us-east-2a has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 18, 16:21 UTC
Update - starter-us-east-2a upgrade to OpenShift 3.11.82 is complete, CVE remediation resuming. Estimated completion time to be determined shortly.
Mar 18, 13:00 UTC
Update - starter-us-east-2a is in the process of being upgraded to OpenShift 3.11.82. Due to the intermittent API errors, no estimated completion time is available.
Mar 15, 19:42 UTC
Update - Incident is ongoing and no ETA is available.
Mar 15, 00:47 UTC
Update - OpenShift SRE is aware of a condition affecting some failing routes and periodic API issues and continues to investigate the situation.
Mar 14, 22:10 UTC
Update - We are experiencing a higher rate of errors than initially expected and continue to investigate.
Mar 14, 17:44 UTC
Update - Scheduled maintenance for starter-us-east-2a is still in progress and is taking longer than expected, the current estimate for completion is Mar 15, 2019 at 13:00 UTC.
Mar 14, 12:12 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 14, 05:01 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 14, 2019 at 05:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 14, 03:00 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 14, 2019 at 05:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 14, 01:00 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 14, 2019 at 05:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 13, 21:00 UTC
Scheduled - OSIO clusters need to be patched to finish remediation of https://access.redhat.com/security/cve/cve-2019-5736.

SRE is performing 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 12, 15:48 UTC
CVE-2019-5736 (runcescape) remediation for starter-us-east-2
Completed - Maintenance on starter-us-east-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 18, 16:21 UTC
Update - starter-us-east-2 upgrade to OpenShift 3.11.82 is complete, CVE remediation resuming. Estimated completion time to be determined shortly.
Mar 18, 12:59 UTC
Update - starter-us-east-2 is in the process of being upgraded to OpenShift 3.11.82. Due to the intermittent API errors, no estimated completion time is available.
Mar 15, 19:43 UTC
Update - Scheduled maintenance for starter-us-east-2 is still in progress and is taking longer than expected, the current estimate for completion is Mar 15, 2019 at 20:00 UTC.
Mar 14, 19:01 UTC
Update - Scheduled maintenance for starter-us-east-2 is still in progress and is taking longer than expected, the current estimate for completion is Mar 14, 2019 at 20:00 UTC.
Mar 13, 17: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/.
Mar 13, 12:00 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 13, 2019 at 12:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 13, 10:00 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 13, 2019 at 12:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 13, 08:00 UTC
Update - This is a reminder regarding your upcoming scheduled maintenance on Mar 13, 2019 at 12:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Mar 13, 04:00 UTC
Scheduled - OSIO clusters need to be patched to finish remediation of https://access.redhat.com/security/cve/cve-2019-5736.

SRE is performing 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 12, 15:47 UTC
Mar 17, 2019

No incidents reported.

Mar 16, 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
Elevated API Errors
Resolved - Infrastructure Maintenance

This maintenance is not expected to cause any interruptions to your applications.

Thank you for using OpenShift Starter.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Mar 8, 16:23 UTC
Investigating - We're experiencing an elevated level of API errors and are currently looking into the issue.
Mar 7, 20:56 UTC
← Incident History Powered by Statuspage