MyWhat Does "Trace" Ancestry Mean in DNA Results?
A small percentage tucked at the bottom of an ancestry or ancient-origins report — often labeled "trace region," "trace ancestry," or shown at 1% or less — tends to draw outsized attention. Here's what that small number is actually telling you, and where its limits are.
| Typical threshold | Most providers label results below roughly 1-2% as "trace," though the exact cutoff varies by company |
|---|---|
| What it reflects | A genuine but small and lower-confidence statistical signal linking part of your DNA to a specific reference population |
| Main causes | A distant ancestor from that population, statistical noise near the detection threshold, or shared deep ancestry between neighboring reference populations |
| How stable it is | Less stable than large ancestry percentages — trace results are the most likely to shift or disappear when a provider updates its reference panel |
Why trace results exist at all
Ancestry estimation works by comparing segments of your DNA to reference populations and assigning each segment a best statistical match. Most segments cluster clearly into your main ancestry groups. But a small number of segments can be genuinely ambiguous or can reflect a distant ancestor from an outside population — and when that happens consistently enough across your genome, the algorithm reports it as a small "trace" percentage rather than folding it into your main results.
Three reasons a trace result shows up
A trace percentage generally comes from one of three sources, and providers can't always tell you which one applies to your specific case:
- A real, distant ancestor. Someone several generations back may have belonged to that population, but random inheritance means only a small fragment of their DNA survived down to you.
- Shared ancestry between neighboring groups. Reference populations that lived near each other or share deep ancestry can produce small cross-matches even without a specific ancestor from that group.
- Statistical noise. Near the lower detection threshold, small amounts of measurement uncertainty can produce a trace result that doesn't correspond to a real, distinct ancestral connection at all.
How this applies to ancient-origins results specifically
The same logic applies when a small ancient population result appears in an ancient-origins panel rather than a standard modern ethnicity estimate. Because ancient reference populations are compared over a much longer timespan, a trace-level match to an ancient population is often reflecting deep, shared ancestral connections between regions — rather than a specific recent ancestor — more often than a trace result in a modern ethnicity estimate would.
How to weigh a trace result
A trace result becomes more meaningful when it's consistent with independent evidence: known family history, documented genealogical records, or a consistent appearance across updates to the same provider's algorithm over time. On its own, a single small trace percentage with no supporting evidence is best treated as a tentative signal rather than a settled fact about your ancestry.
For the bigger picture on how any of these percentages — trace or otherwise — are calculated in the first place, see our ancient DNA explainer. If a specific ancient population shows up in your trace results, browse the full ancient populations directory to see what that group means.
Should I ignore trace ancestry results entirely?
Not necessarily, but treat them as a lead rather than a conclusion. A trace result that lines up with known family history or other documented records is worth taking seriously; an unexpected trace result with no other supporting evidence is best treated as tentative.
Why did a trace result I had before disappear after an update?
This is common and expected. As a provider's reference panel and algorithm improve, small low-confidence estimates are often the first results to shift, since they were closest to the noise floor to begin with.