Internal Ping Check lets you monitor the health of private WAN links (MPLS, SD-WAN, VPN, microwave, private fiber, etc.) from inside your network using an Auvik Collector.
Instead of relying on separate tools (like PingPlotter) or manual tests, you can now:
Continuously measure round-trip time (RTT) and packet loss to internal or private IPs
Visualize trends over time for critical paths
Trigger alerts when latency or loss crosses thresholds
This gives you early warning of link degradation, helps prove provider SLAs, and reduces the time to diagnose WAN issues.
Internal Ping Check vs. Cloud Ping Check
Auvik now offers two complementary ways to test connectivity:
Feature |
Cloud Ping Check |
Internal Ping Check |
|---|---|---|
Source of the ping |
Auvik Cloud |
Auvik Collector (on-prem or IaaS) |
Typical use |
Internet reachability / north–south traffic |
Private WAN / east–west traffic |
Targets |
Public IPs (e.g. firewall WAN interface, public host) |
Any reachable internal or private IP address |
Example use case |
“Is this site online from the Internet?” |
“Is this MPLS/SD-WAN/VPN link healthy between sites/endpoints?” |
Use Cloud Ping Check when you want to know if a site is up from the Internet.
Use Internal Ping Check when you want to know if internal paths and private links are healthy from the perspective of the LAN or data center.
Internal Ping Checks vs. Health Checks
Aspect |
Health Check (Built-in) |
Internal Ping Check (Custom) |
|---|---|---|
Primary purpose |
Decide if a device is online/offline |
Monitor path/link quality (latency, packet loss) |
How it works |
Sends 3 ICMP types (Address, Timestamp, Echo). Any reply = success |
Ping from a chosen collector to a specific IP |
Failure / threshold logic |
5 consecutive ping failures → device marked offline |
Evaluated against custom thresholds (latency, loss, availability) |
SNMP interaction |
SNMP success before threshold → failure counter reset to 0 |
No SNMP interaction; purely ping-based |
Target |
Automatically applied to Auvik-monitored devices |
User specified IP address |
Impact on device status |
Drives online/offline status, maps, dashboards, and alerts |
Does not change device online/offline status |
Typical use cases |
Basic device reachability and status |
MPLS/VPN/SD-WAN links, inter-site paths, critical internal IPs, ISP edges |
When to use |
“Is this device up?” |
“How healthy is this link/path over time?” |
How Internal Ping Check works
Internal Ping Check:
Uses ICMP echo (ping) from a selected Auvik Collector
Targets one or more IP addresses you specify
Samples at a configured interval
-
Records:
RTT (min / avg / max) in milliseconds
Packet loss % over the interval
-
Feeds these metrics into:
Graphs on the service detail page
Threshold-based alert conditions in Auvik
You can choose any IP address the collector can route to: local devices, remote sites over MPLS/SD-WAN/VPN, or IaaS-based workloads.
Note: The initial release of Internal Ping Check has a few limitations:
-
FQDN is not supported for targets
You must specify IP addresses, not hostnames.