Cloud probes can't reach 10.0.0.0/8
UptimeRobot, Pingdom, and BetterStack run from the public internet — they can't ping your internal MikroTik router, office printer, NAS, or AWS VPC endpoints.
Private Probe · PRO+
Monitor your LAN, intranet, and home lab from one dashboard
Self-host a tiny Docker probe inside your network. PingZen does the rest — multi-channel alerts, incident history, public status pages — without your data leaving your network.
Why external uptime SaaS can't do this
Zabbix and The Dude need infrastructure
Self-hosted alternatives require a dedicated server, agents, templates, and ongoing maintenance. Great for ISPs and NOCs, overkill for an office LAN.
You still want one dashboard
Mixing public and private monitoring across two tools means two dashboards, two alert channels, and two on-call rotations. Private Probe keeps everything in PingZen.
The fix: PingZen Private Probe
A Private Probe is a single Docker container you run inside your network. It opens an outbound WebSocket connection to PingZen (no inbound ports, no static IP, NAT-friendly), and PingZen pushes check tasks to it. The probe runs the checks against RFC1918 hosts (10.x, 172.16-31.x, 192.168.x) and reports status back. ~200 MB RAM, runs on Linux/amd64, Linux/arm64, or macOS via Docker Desktop.
docker-compose.yaml
services:
pingzen-checker:
image: ilyakong/pingzen-checker:0.3.2
restart: unless-stopped
cap_add: [NET_RAW]
environment:
PINGZEN_URL: https://pingzen.dev
PROBE_KEY: pz_your_api_key_here
PROBE_NAME: "Office LAN"
PROBE_TYPE: home
PROBE_REGION: "Office, RU"Generate a pz_* API key in your account settings, then paste it into PROBE_KEY. After docker compose up -d, the probe appears in your dashboard within 30 seconds.
Real-world use cases
What the Private Probe actually monitors inside a typical office or home network.
MikroTik router
Check that your edge router is reachable and its WAN interface is up. Ping the gateway, TCP-check the API port, monitor the web UI.
ICMP · 192.168.88.1 TCP · 192.168.88.1:8728 (RouterOS API) HTTP · http://192.168.88.1/login
Network printer
Catch printer outages before users complain. Most network printers expose IPP (port 631) and a web UI for ink/toner status.
TCP · 192.168.1.50:9100 (RAW print) HTTP · http://192.168.1.50/ (printer status)
NAS (Synology / QNAP / TrueNAS)
Make sure your backup target is online. Check the web admin, SMB share availability, and the DSM/QTS API.
HTTP · http://nas.local:5000 (DSM) TCP · nas.local:445 (SMB) TCP · nas.local:5001 (DSM HTTPS)
Protocols supported by Private Probe
The Private Probe handles every protocol you need for intranet uptime checks. Higher-tier protocols (PageSpeed, Transaction, gRPC) still route through PingZen's central probes — only LAN-style protocols need the Private Probe.
- HTTP / HTTPS
- TCP / UDP
- ICMP / Ping
- DNS (A, AAAA, MX, TXT, CNAME)
- SSL certificate expiry
- WebSocket (WS / WSS)
- WHOIS
- SOCKS5 proxy
- MTProxy
SNMP is not yet supported. If you need SNMP graphs (CPU, RAM, interface counters) on top of uptime, leave feedback in the dashboard — it's the next protocol on the consideration list.
Plan limits
How many Private Probes you can register on your account.
| Plan | Private probes per account |
|---|---|
| FREE | 0 (upgrade to PRO) |
| PRO | 3 |
| BUSINESS | 10 |
| ENTERPRISE | 50 |
Frequently asked questions
Ready to monitor your LAN?
Free account → upgrade to PRO when you're ready to add Private Probes. The Docker container takes 60 seconds to start.