mtr is My Traceroute — ping plus traceroute in one TUI. It prints hop loss. It is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Accidental sysadmins land on mtr because mtr 1.1.1.1 shows Loss% without a dashboard. Then disk is at 91%, nginx dies, and last night's hop 8 lines do not say what to run. A filling /var is a Tink warning; it is not a traceroute reply.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep using mtr if you already want a path dump on an SSH session. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | mtr |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Install mtr, pick a destination, then watch Loss% and Last/Avg/Best/Wrst every time a path looks slow |
| What you get | Working monitoring, diagnosis, and approved fixes | A live hop table: ASN, loss, and latency, only while you are looking |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open source. You still pay the person who SSHs in after the outage |
| Hidden costs | None — fully managed | Which dest, ICMP vs TCP, ICMP-rate-limited hops, and whether anyone was watching when Loss% spiked |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Hop-by-hop path tracer. mtr does not parse auth.log or propose a command |
| Configuration | None after install — heuristics and AI | Count, interval, TCP/UDP/ICMP, and whether the ISP hop even answers |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — you read Loss%, Snt, and Last yourself |
| Fix execution | Proposes and executes approved commands with an audit trail | Monitoring only — mtr cannot restart nginx, free disk, or rotate a cert |
| Alerting | Built-in across 8 channels | None by default — mtr is a snapshot; paging is extra |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Live hops only — mtr does not forecast fill time or a quiet disk going bad later |
| SSH brute-force detection | Built-in — parses auth.log every scan | Not included — mtr does not read host auth.log or journald |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | If the host is down you cannot SSH into mtr either |
| Public status page | Shareable URL with 90-day history | Not included — mtr has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | Not included — a hop table is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire something else into PagerDuty |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | SSH + mtr. No mechanic you text when /var filled |
| Learning curve | None — works after install | Low to launch; higher to map hop 8 loss to the disk that filled |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Operators who already want a path dump and will still SSH in when the box is sick |
Keep using mtr when you already want that exact job:
The tracer is cheap to install. A working ops loop for five Linux boxes is not:
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who opens mtr after the outage, and every scan includes a diagnosis a quiet hop table will not type.
No SSH homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs strace · Tink vs ss · Tink vs tcpdump