Live diagnostic

Diagnose once. Watch continuously.

Describe what to test in plain language — then keep watching the same targets from your nodes with latency and failure alerts.

try →

No credit card · icmp · tcp · http · traceroute · dns

What you get

Diagnose in chat, then turn the same vantage points into continuous checks.

◎

Plain-language probes

Ask in English. The agent picks icmp, tcp, http, dns, or traceroute.

⬡

Your own nodes

Self-host probes with systemd. Traffic leaves from networks you trust.

⏱

Continuous monitoring

Schedule jobs on a few-minute cadence. Charts for latency & TTFB; alerts on failure.

See health over time — not just a single probe

Turn a diagnosis into a job. Track HTTP latency & TTFB, or ICMP RTT & loss, with clear thresholds.

api.github.com · production edge
HTTP · US-California · every 60s · last 24h
Healthy
Uptime
99.97%
p95 latency
142 ms
Last 12 checks
Latency (ms)TTFB (ms)

03:14–03:18 HKT — brief latency spike (p95 ≈ 480ms) then recovery. No sustained failure; alert threshold not crossed.

Three steps to continuous checks

Aligned with ConnSentinel's diagnose → monitor flow.

01

Pick target & node

Reuse the host and region you just diagnosed — or choose another probe in your fleet.

02

Set the interval

HTTP checks every 30s–10m. ICMP as fast as 15s. Tune for cost vs. signal.

03

Alert on failure & latency

Notify when checks fail, or when p95 / loss crosses the threshold you set.

Probes stay outbound-only

Your host dials out. Nothing listens for the public internet. Same vantage points power chat diagnosis and continuous monitoring.

bash · linux host
$ curl -fsSL https://download.connsentinel.com/install-probe.sh | sudo bash -s -- \
    --install-token "YOUR_INSTALL_TOKEN"
# Linux x86-64/arm64 · systemd · outbound 443
ok Installed /usr/local/bin/probe-service
ok Started connsentinel-probe.service
  • No inbound ports

    No public listener, no open firewall holes. The probe only makes outbound HTTPS to the agent registry.

  • Scoped install token

    Enrollment uses a short-lived token tied to your account. After check-in, the node appears in your fleet — nothing else.

  • Least privilege on the host

    Runs as a systemd service with CAP_NET_RAW for ICMP where needed, and NoNewPrivileges — not a full root shell.

Know when it breaks — or just slows down

Failure alerts and latency thresholds, without drowning you in noise.

Notification rules

  • Alert on consecutive check failures
  • Threshold on p95 latency or packet loss
  • Recovered notices when the path clears
  • Route to email / webhook

Recent events

Recoveredcheckout.example · EU path
Today 14:22 HKT · p95 back under 200ms
Degradedcheckout.example · latency
Today 13:58 HKT · p95 410ms · 3 checks
Spikeapi.github.com · brief blip
Yesterday 03:16 HKT · threshold not crossed

Start a session

Open the app to diagnose now — monitoring jobs unlock when you're signed in.