What trcr Monitors
Network Probes
01 Latency & Reachability (ICMP Ping)
Sends ICMP echo requests to every target and measures round-trip time (min, avg, max, stddev), jitter for VoIP and real-time applications, and packet loss percentage. At scale, trcr uses a high-performance batch mode with a single raw socket.
02 Network Path Analysis (Traceroute)
Traces the hop-by-hop path to each destination, recording every router with IP, hostname, and per-hop latency. Automatic path change detection flags when traffic is rerouted, surfacing ISP failovers and BGP shifts.
03 DNS Health
Queries specific DNS servers with configurable record types (A, AAAA, MX, CNAME) and measures query response time and answer correctness. Detects resolver failures, slow propagation, and incorrect records.
Service Probes
01 Web Service Health (HTTP/HTTPS)
Makes full HTTP/HTTPS requests and breaks the response into phases: DNS resolution, TCP connect, TLS handshake, time to first byte (TTFB), and transfer time. Confirms services are responding with correct status codes.
02 Bandwidth Testing (iperf3)
Runs throughput tests between nodes measuring TCP bandwidth with retransmit counts (indicating congestion) and UDP bandwidth with jitter and packet loss. Supports upload, download, and configurable durations.
03 Flexible Data Backends
Ship results to Elasticsearch for Kibana dashboards, InfluxDB for Grafana time-series visualization, PostgreSQL for SQL queries and long-term archival, or stdout for local debugging. Use any combination simultaneously.
One Config, Total Visibility
Define all your targets, probes, agents, and data backends in a single YAML file. trcr handles the rest — continuously probing your infrastructure and shipping structured results to the databases you already use.
No fragmented scripts. No manual traceroutes. No guesswork. Just deploy, configure, and see every hop, every millisecond, everywhere.
Learn More
How trcr Works
Deploy Master
Install trcr on your central node. Define all targets, agents, probes, and output backends in a single YAML configuration file.
Add Agents
Deploy lightweight agents on remote sites, branch offices, data centers, or cloud regions. The master pushes configuration automatically.
Full Mesh Probing
Each agent automatically probes every other agent, creating a measurement grid. 10 agents = 90 measurement paths with zero per-agent configuration.
Visualize & Alert
Results flow to your chosen backends. Build Kibana or Grafana dashboards, run SQL queries, and set up alerts on the metrics that matter.
Why Teams Choose trcr
Whether you are an ISP monitoring backbone links, an enterprise tracking WAN performance, or an MSP managing dozens of client sites, trcr provides the visibility you need to catch problems before users report them.
Proactive Detection
Catch rising latency, packet loss, DNS failures, and HTTP degradation before they impact users or voice/video quality.
Faster Troubleshooting
Historical data is already in your database. Query exact timestamps, traceroute changes, and HTTP phase breakdowns to isolate root causes in seconds.
Capacity Planning
Track bandwidth utilization over weeks and months. Identify congested paths, measure the impact of infrastructure changes, and plan upgrades with data.
Multi-Site Visibility
The agent mesh measures every site to every other site. No blind spots. Asymmetric issues are immediately visible. Results tagged by source and destination.
What Engineers Say
trcr replaced a dozen cron scripts we had scattered across our infrastructure. Now we have a single config file and full visibility into every hop between our data centers.
Sarah Chen
Network Engineer, ISP
The automatic traceroute change detection is a game-changer. We caught a BGP misconfig within minutes instead of spending hours on manual traceroutes.
Marcus Rivera
SRE Lead, Enterprise
Deploying 15 agents across our client sites took under an hour. The full-mesh probing gives us 210 measurement paths automatically. Our NOC dashboard has never been more comprehensive.
James Okafor
Director of Operations, MSP
The HTTP phase breakdown pinpointed that our latency issue was in TLS handshake, not the application. What used to take hours of debugging now takes seconds.
Priya Sharma
DevOps Engineer, SaaS
Get Started Today
Start Monitoring For Free
Up to 5 monitored nodes, no license key required.
No credit card, no commitment. Just deploy and start seeing your network.