# Telemetry always Disabled or Unhealthy

**URL:** <https://forums.portworx.com/t/telemetry-always-disabled-or-unhealthy/1748>\
**Category:** Portworx on Kubernetes\
**Created:** [August 25, 2023, 8:51am UTC](https://forums.portworx.com/t/telemetry-always-disabled-or-unhealthy/1748 "2023-08-25T08:51:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Reeuwijk](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/kevin_reeuwijk/32/719_2.png) [@Kevin\_Reeuwijk](https://forums.portworx.com/u/Kevin_Reeuwijk)\
**Post date:** [August 25, 2023, 8:51am UTC](https://forums.portworx.com/t/telemetry-always-disabled-or-unhealthy/1748/1 "2023-08-25T08:51:28Z")

</div>

I always see “Telemetry: Disabled or Unhealthy” in `pxctl status`, why is that and how can I troubleshoot it?  
I have `spec.monitoring.telemetry.enabled: true` in the storageCluster object, and the `px-telemetry-phonehome` and `px-telemetry-registration` pods are running. Where should I look to see what could be making the state unhealthy? The cluster itself is running just fine, it’s only this telemetry not reporting correctly and I’m seeing this on every cluster we run.

I’m running Portworx 3.0.0