How to monitor multiple IPs at once on Windows

Method 1: Free, one ping -t window per host

The quickest no-install option is one Command Prompt per address:

ping -t 192.168.1.1
ping -t 8.8.8.8

-t keeps pinging until you press Ctrl+C. It works, but with five hosts you're juggling five windows, there's no history, and you can't tell when a host dropped unless you were watching.

Method 2: Free, PowerShell Test-Connection for many hosts

PowerShell's Test-Connection accepts a list of targets (Microsoft Learn). To check a list in one go in PowerShell 7:

'192.168.1.1','192.168.1.20','8.8.8.8' | ForEach-Object -Parallel {
  Test-Connection $_ -Count 1 -Quiet | ForEach-Object { "$using:_ up: $_" }
}

Wrap it in a while ($true) { …; Start-Sleep 5 } loop to repeat. Microsoft's docs note one gotcha: -Repeat with several targets only repeats the first target, so loop it yourself instead.

To check a port (is the web server answering, not just the box?), use Test-NetConnection 192.168.1.20 -Port 443.

This is free and scriptable. What you don't get is a live view: you read text output, and building logs or a history means writing more script.

Method 3: A tile per host in one window (Solace Ping)

Solace Ping is a small Windows app that gives each address its own tile. We ran it for about 45 minutes with up to 10 tiles on Windows 11. Here's how to set it up.

Step 1: Unzip and run

It's a portable ZIP (about 0.26 MB) with no installer. It needs .NET Framework 4.7.2, which current Windows 11 already includes, so there was nothing to install in our test. The ZIP is unsigned, so SmartScreen will warn you on first launch. Check the SHA-256 on the product page first.

Step 2: Add your hosts

Type an IP, a hostname or a host:port into each tile. We used a router (10.0.0.1), 8.8.8.8, dns.google, one.one.one.one and 127.0.0.1 without problems.

• A plain address sends normal ICMP pings.
• host:port does a TCP check instead. For example, 1.1.1.1:443 showed "Port 443: OPEN [18ms]". That's handy for servers that block ping, or when you care whether the service is up.

Step 3: Read the colors

• Green: replying.
• Yellow: replies have started failing.
• Red: down. Our unreachable test address showed "Request timed out."

Each tile shows live reply times plus Sent / Received / Lost counters. Stopping a tile gives a summary with min, max and average.

Step 4: Arrange the grid

A Columns slider (1–10) sets the layout, and tiles reflow when you resize the window. We tried 10 tiles from 900×600 up to a large monitor. At very small window sizes, the stats hide to save space.

Step 5: Save, label and log

• Aliases: name a tile "Home router" instead of 10.0.0.1.
• Favorite sets: save the current hosts as a named set and reload them later.
• Status history: a timestamped list of up, down, start and stop events, with a filter and Export.
• Per-host logs: turn on text logging and you get one file per host, one line per reply, written live. Tip: in our test, putting the same host in two tiles made logging switch off, so keep each host in one tile.
• Traceroute: built in. Ours to 1.1.1.1 finished in about 5 seconds, with the time for each hop.

One more tip: Input Addresses (F2) replaces all current tiles with the list you paste. It doesn't add to them.

Privacy

In our test, Solace Ping only connected to the hosts we entered. We saw no update check and no telemetry. Settings live in %LOCALAPPDATA%\Solace Ping.

Which should you use?

• One host, quick check: ping -t is fine.
• A scripted check of many hosts, or a scheduled report: PowerShell is free and flexible.
• A live dashboard of several hosts, with port checks, history and logs: that's where a tile monitor earns its keep. That's Solace Ping, with our support included.

Get Solace Ping

Solace Ping: multi-host ping monitor for Windows, $36.79 one-time →

You get 12 months of support and a 14-day refund if the package can't start its core check.