TRAACRTRAACR
Network monitoring and data aggregation for UniFi, Pi-hole and your servers.
One view across every site. Every device explained: who it is, when it was here, and what it contacted.
Figure 1 uses synthetic data. Nothing on this page is a customer.
Figure 1 · Overview, Clients, DeviceSynthetic data
TRAACR / overview
All systems operational
- Sites
- 4/4 up
- Devices
- 63/64 online
- Clients
- 118
- Incidents
- 0
Sites (4)
| Site | Devices | Clients | WAN speed (Mbps) | Latency |
|---|---|---|---|---|
| Harbour Office | 24/24 | 41 | 312 ↓ 118 ↑ | 8 ms |
| Usk Workshop | 11/12 | 19 | 94 ↓ 21 ↑ | 14 ms |
| Lakeside | 17/17 | 33 | 487 ↓ 205 ↑ | 6 ms |
| Cottage | 8/8 | 14 | 41 ↓ 9 ↑ | 22 ms |
Connected clients (118)
| Name | Type | Site | Traffic ↓ / ↑ |
|---|---|---|---|
| Front-desk laptop office | wireless | Harbour Office | 2.4 / 0.3 Mb/s |
| Workshop NAS server | wired | Usk Workshop | 0.8 / 6.1 Mb/s |
| Lounge TV media | wireless | Lakeside | 18.2 / 0.1 Mb/s |
| Thermostat iot | wireless | Cottage | 0.01 / 0.01 Mb/s |
| Guest phone | wireless | Harbour Office | 1.1 / 0.2 Mb/s |
Front-desk laptop connected now
- Name in UniFi
- MBP-4471
- Person
- Reception
- Site
- Harbour Office
- Connected via
- AP Lobby · U6 Pro
- MAC address
- AA:BB:CC:00:11:22
- Looks like
- Apple device
- Visits, last 30 days
- 21 visits, 21 days
Sites and services, last 24 hours
Microsoft 365 Work & productivity412
Google Search & web188
Apple Cloud & updates97
NTP time sync System & background24
- 1The status line answers “is anything wrong?” before anything else.
- 2One row per UniFi site: devices online, clients and WAN speed.
- 3WAN speed is read from each console and refreshed about every 10 seconds while the page is open.
- 4Clients and Devices list everything. Every row opens a complete device page.
Specifications
What it connects to, what it records, and how often.
| Sources | UniFi Network through the UniFi Site Manager cloud API, Pi-hole v6, Unraid (small agent), and HTTP service checks. |
|---|---|
| Sites | Several UniFi sites on one account, each monitored on its own. Choose which ones to include. |
| Devices | Every client and network device at each site. Connection history, nicknames, people, tags and notes. |
| Live WAN speed | Per site, about every 10 s while the page is open. |
| Client and device sync | About every 5 min per site. |
| DNS activity | Pi-hole lookups per device per hour: sites and services contacted, including background lookups, with the blocked share. |
| Reports | A PDF connection report per device: every date and time it was present, with its activity. |
| Alerts | Discord webhooks for incidents, and optionally for a device connecting or disconnecting. |
| Retention | Per-site detail kept for 7 to 90 days, your choice (30 by default). Hourly DNS totals are kept for 90 days. |
| Hosting | PHP 8.2 and MySQL on ordinary shared hosting. The agent only connects outward; no inbound ports are opened on your network. |
| Status | Early access |
How it works
Your networks stay where they are. Data comes out; nothing goes in.
Notes
What the data is, and what it isn’t.
- A lookup is not a visit.A site in the activity list means a device looked it up, not that anyone opened it.
- Background is shown.Time sync, connectivity checks and app check-ins appear, labelled as system and background.
- Times are approximate.Connections are accurate to about five minutes, the sync interval.
- Names are local.Nicknames, people, tags and notes stay in TRAACR. UniFi is never renamed.
- Some devices bypass Pi-hole.Devices with their own DNS, such as some TVs, won’t show activity.
- History starts at connection.Reports cover visits from when a site was connected, not before.
Request early access
We’ll email once, when your invite is ready. Plans and pricing are announced at launch.
Your address is used only to send your invite.