What TRCR Monitors
Six of the 14 probe types, in brief. The probe catalogue lists all of them with the metrics each one records.
Network Probes
01 Latency & Reachability (ICMP Ping)
TRCR's ICMP ping probe sends 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's batch mode pings thousands of targets in parallel from one socket, with intervals down to 1 second.
02 Network Path Analysis (Traceroute)
TRCR's traceroute probe records the hop-by-hop path to each destination, with every router's IP, hostname and per-hop latency, and enriches each hop with its autonomous system. Automatic path-change and AS-path-change detection flags when traffic is rerouted, surfacing ISP failovers and BGP shifts, and keeps the previous path for comparison.
03 DNS Health
TRCR's DNS probe queries the system resolver or specific resolvers for A, AAAA, CNAME, MX, TXT, NS, SOA, PTR and SRV records, measures response time and checks the answer against an expected value. The DNS propagation probe asks up to 32 public resolvers the same question and reports whether they agree.
Service Probes
01 Web Service Health (HTTP/HTTPS)
TRCR's HTTP probe makes a full HTTP/HTTPS request and breaks the response into phases: DNS resolution, TCP connect, TLS handshake, time to first byte (TTFB), and transfer time. It records the status code, body size and checksum, redirects and final URL, and confirms the service answers with the status you expect.
02 Native Throughput Testing
TRCR's throughput probe measures TCP bandwidth between two agents over the same mTLS connection the agents already trust, with no iperf3 to install. Each test is bounded by duration or byte count (up to 60 seconds) and reports bandwidth, bytes transferred and, on Linux, TCP retransmit counts, which indicate congestion.
03 Flexible Data Backends
TRCR ships results to PostgreSQL (partitioned time-series tables), InfluxDB for Grafana, Elasticsearch for Kibana, or a Prometheus exporter endpoint for scraping and remote_write, in any combination at once. Stdout and file outputs cover debugging and log shippers. Backends are free in every tier.
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.
The file on the right is a real fragment: three probes, three types, one backend, and a traceroute pinned to two agents. trcrd validate checks it before anything starts, and a change reaches every agent within a minute.
# Three targets, three probe types, one backend.
probes:
- name: api-edge
type: http
url: https://api.example.com/health
interval: 30s
expected_status: [200]
backends: [postgres-main]
- name: core-router
type: ping
target: 203.0.113.1
interval: 10s
count: 5
backends: [postgres-main]
- name: path-to-dc2
type: traceroute
target: dc2-gw.example.net
interval: 5m
agents: [agent-sfo, agent-fra]
backends: [postgres-main]How TRCR Works
-
1.Deploy the Master
Install TRCR on your central node with one command. Define all targets, agents, probes, and output backends in a single YAML configuration file.
-
2.Add Agents
Deploy lightweight agents on remote sites, branch offices, data centers, or cloud regions. Each agent enrols once over mTLS; the master pushes its probes automatically.
-
3.Full Mesh Probing
Each agent automatically probes every other agent, creating a measurement grid. 10 agents = 90 measurement paths with zero per-agent configuration.
-
4.Visualize & Alert
Results flow to your chosen backends. Use the published Grafana and Kibana dashboards, run SQL queries, and set threshold, failure and path-change 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. Your agents, your data, your database: see how TRCR compares with scripts, host monitoring and SaaS uptime checkers.
Proactive Detection
Catch rising latency, packet loss, DNS failures, expiring certificates 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 and interface utilisation 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.
Real Probes, Real Data, No Login
The public demo is a Grafana fed by a running TRCR master and its agents in Dallas, Los Angeles and San Francisco: ping, HTTP, DNS, SSL, traceroute, throughput and BGP dashboards, read-only, no account needed. The screenshot is the ping dashboard as captured on 5 October 2026.
The dashboards behind it and the product documentation are public on GitHub under github.com/trcrdev. TRCR (trcr.dev) is network monitoring software from NameVerse, Inc.; it is not a cryptocurrency, token or carbon-credit project.
Open the Live Demo Dashboards on GitHub
Get Started Today
Start Monitoring For Free
Free forever: 5 agents and 50 monitors across all four bundles, every bundle enabled.
No credit card, no commitment. Install in about a minute and start seeing your network.