> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/platform-settings/customization-options.md).

# Ping Settings

The **Ping Settings** tab in Platform Settings allows administrators to configure how Nexus automatically monitors device connectivity. By defining ping intervals and inactivity thresholds, administrators can ensure timely awareness of device availability and health across the platform.

These settings require the [Administrator Role](/platform-architecture/security-architecture/user-roles-and-permissions.md) to access and modify.

***

## Key Configurations

<figure><img src="/files/X5fIZxTmYBwTXK1p5li0" alt=""><figcaption><p>The Ping Settings of Platform Settings</p></figcaption></figure>

### Automatic Pinging of Active Devices

When enabled, Nexus will automatically **ping all active devices** at a defined interval to verify connectivity.

* **Time Period Between Active Device Pings**: Specifies how often an active device is pinged (default: **1 hour**).
* **Ping All Button**: Allows administrators to trigger an **on-demand ping** of all active devices immediately.

The last time a device was successfully pinged can be found in [Device Details](/management-portal/operations/monitoring/device-details.md) in the Operations Monitoring.

***

### Automatic Pinging of Inactive Devices

When enabled, Nexus will also ping devices that are marked as **inactive**, ensuring that devices which were previously offline are checked for reconnection.

* **Time Period Between Inactive Device Pings**: Specifies how often inactive devices are re-pinged (default: **7 days**).
* This feature helps detect when devices that were offline come back online automatically.

***

### Inactivity Threshold

This setting determines how long Nexus waits without receiving a response from a device before classifying it as **inactive**.

* **Time Period With No Response Before Becoming Inactive**: Defines the threshold for inactivity (default: **7 days**).
* Once this threshold is reached, the device is flagged as **inactive**, and ping rules for inactive devices will apply.

***

## When to Adjust Settings

* **Reduce active ping intervals** for critical devices where uptime is business-critical and needs close monitoring.
* **Increase inactive ping intervals** to reduce unnecessary system load for large fleets with many offline devices.
* **Adjust inactivity thresholds** based on operational requirements - for example, shorter thresholds for high-availability devices, or longer thresholds for devices that are expected to be offline occasionally.