Traceroute
“traceroute for gossip. Your grandma just called to say congratulations on Delaware. You have never been to Delaware. You have never mentioned Delaware. Somewhere in the family mesh, a packet mutated. traceroute grandma.family.localtells you where. Enterprise: MTR mode monitors the mesh continuously and pages you on BGP hijacks (your therapist showed up in the AS_PATH at 4:07pm on Tuesday).”
The Problem
You mentioned to your roommate that you might visit Denver in October. Nine days later, your grandmother texts “so proud of you and Kyle for the move — Delaware is beautiful this time of year.” You do not know a Kyle. You have never been east of Ohio. Something happened between hops 0 and 6.
The Solution
We wire tiny ICMP probes into every mention of your name across the family mesh. Each hop rewrites the payload; we log the mutation. By the time it reaches grandma, you have the full changelog — and receipts.
The Mesh
Your family isn’t a tree, it’s a full-mesh graph with preferential peering between cousins. One nephew has a BGP session with three separate group chats. We map it.
Pricing
TAM
The Ask
$5M seed. 50% to the mutation classifier — distinguishing an honest mishear (“Denver” → “Delaware”) from a deliberate rewrite (“maybe” → “engaged”) is the whole moat. 30% to the mesh crawler that stays under the 8-hop TTL your grandma’s book club enforces. 20% to legal, in case an aunt sues.
Series A pitch: “We’re Wireshark, but the packets are your family.”