An address-only target
Enter a public IPv4 or IPv6 address. No hostname resolution is needed for the target, keeping this check focused on direct network reachability.
Watch the address.
Separate the signal.
Monitor public IPv4 and IPv6 reachability directly. Keep an address-level view of latency and packet loss without depending on a hostname lookup.
Part of your Uptiva workspace · One workspace. Every signal.
RESPONSE TIME24 ms
- Target
- 1.1.1.1
- Address family
- IPv4
- Reachability
- Responding
- Packet loss
- 0%
DNS and network reachability answer different questions. An IP monitor checks the address itself, making it useful when you want a network signal that stays independent of a domain’s resolution.
The check uses ICMP, just like ping monitoring, with an address-only target. Review packet statistics and regional results, then compare them with DNS and service checks for a more complete view of a failure.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
ICMP results
Check whether the address answers echo requests. The target must permit ICMP for the result to represent the availability signal you expect.
Latency and loss
Review average, minimum and maximum latency alongside sent and received packets. Packet loss and jitter add context beyond a simple up or down result.
A regional view
Choose where checks run and compare the latest results. Reachability from one location does not always mean the same route is healthy elsewhere.
Response-time history
Follow the address over time and look for intermittent patterns. Keep the history available when a short network issue has already recovered by the time someone investigates.
Part of a layered check
Pair direct IP reachability with DNS, port and HTTP monitors. Each signal narrows a different part of the path between a customer and a working application.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Known public addresses
Watch a server or device that you identify by a fixed public address. A recognizable monitor name keeps it easy to connect that address with the system it belongs to.
DNS troubleshooting
Compare a direct IP check with a hostname-based monitor. If they behave differently, you have a useful starting point for investigating resolution and routing separately.
Infrastructure changes
Keep a direct reachability check on an address during network work. Continue using service-level checks to verify the application beyond the network interface.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Choose IP and enter the public IPv4 or IPv6 address. Give it a name that identifies the actual system.
- 02
Configure the check.
Select regions, interval and the failed-check count. Confirm that ICMP is an appropriate availability check for that address.
- 03
Follow the signal.
Set alert channels and compare packet details with the DNS and service monitors for the same system.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationHow is this different from Ping?+
Both use ICMP. Ping accepts a hostname or address, while an IP monitor requires an address and avoids a target hostname lookup.
Can I check a private network address?+
Public probes cannot reach private network addresses. Use a monitoring approach appropriate to the network rather than exposing a private system for this check.
Is IPv6 supported?+
You can enter a public IPv6 address as well as IPv4. The target must be reachable and allow the ICMP check.
What if ICMP is blocked?+
The monitor can report down even if a service on the machine is working. A TCP port or HTTP check may better reflect the intended service availability.
Does it check who owns the address?+
No. IP monitoring checks reachability and timing. It is not an ownership, reputation or blocklist service.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring ip monitoring into your workspace.