---
name: containers-ts-network-nhc005
title: Why does the Network status show an `NHC005` error?
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2026-04-30
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why does the Network status show an `NHC005` error?
{: #ts-network-nhc005}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}

When you check the status of your cluster's health by running the `ibmcloud ks cluster health issues --cluster <CLUSTER_ID>`, you see an error similar to the following example.
{: tsSymptoms}

```sh
ID       Component   Severity   Description
NHC005   Network     Warning    Tigera operator is reporting that Calico is in 'degraded' state.
```
{: screen}

This warning indicates that the Tigera operator, which manages Calico in IBM Cloud Kubernetes Service, has detected that Calico is in a degraded state. This could impact network policies, pod networking, or other network-related features.
{: tsCauses}

Check the logs of the Tigera operator and Calico components to investigate the cause of the degradation.
{: tsResolve}

1. Check Tigera status custom resources and conditions and look for `"conditions"` with `"Progressing": true`.
    ```sh
    kubectl get tigerastatus -o yaml
    ```
    {: pre}

    ```sh
    kubectl get tigerastatus calico -o yaml
    ```
    {: pre}

2. Check Calico and Calico-typha components status by listing the Calico pods in `calico-system` namespace:
    ```sh
    kubectl get pods -n calico-system
    ```
    {: pre}

3. Check the rollout status of deployments and daemonset.
    ```sh
    kubectl rollout status deployment/calico-kube-controllers -n calico-system
    kubectl rollout status deployment/calico-typha -n calico-system
    kubectl rollout status daemonset/calico-node -n calico-system
    ```
    {: pre}

4. If pods are not ready or stuck in `Init` or `CrashLoopBackOff`, get the pod logs.
    ```sh
    kubectl logs <pod-name> -n calico-system
    ```
    {: pre}

5. Look for any configuration errors, networking issues, or crash loops in logs.

6. After resolving any identified issues, wait a few minutes and recheck the network health.

7. For more information, see [Controlling traffic with network policies](https://cloud.ibm.com/docs/containers?topic=containers-network_policies&format=markdown){: external} and [Debugging Calico components](https://cloud.ibm.com/docs/containers?topic=containers-calico_log_level&format=markdown){: external}

8. If the issue persists, contact support for further assistance. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.