Ancestry DNA,**I am writing in regard to what I see as a huge mistake in your formula*c...

GetHuman1334725's customer service issue with Ancestry.com from October 2018

Help with my Ancestry.com issue
The issue in GetHuman1334725's own words
Ancestry DNA,**I am writing in regard to what I see as a huge mistake in your formula*calculations. It seems that the true DNA test is not used as the only predictor. My grandfather on my father’s side was Mexican but none shows up in your summary. Also, on my father’s side was Indian but none shows up for me and more of a percentage for my daughter than her father. **Another very strange ethnicity summary figure that shows up for us lately is the Philippines. So from what I see the Spanish speaking regions are not being used, is this correct? It seems that only the regions you know a person is Ethnically linked is used and combined with both parents strongest Ethnicity. I expect true references to my birth, origins, and*or cultural background.
GetHuman1334725 did not yet indicate what Ancestry.com should do to make this right.
I have an issue with Ancestry.com too
How GetHuman1334725 fixed the problem
We are waiting for GetHuman1334725 to fix the problem and share the solution with the rest of us customers.
Please help with my Ancestry.com issue
Do you have a customer issue as well?
We can help you get Ancestry.com's attention and get better help faster. Tap below to get started.
Having Ancestry.com issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Ancestry.com email you?
This email address isn't valid

Ancestry.com

Customer service issue
Reported by GetHuman1334725
Oct 12th, 2018 - 2 mons ago
I have an issue with Ancestry.com too
Fixed
Seen by 3 customers so far
Similar issue to 1565 others
0 customers following this
Items needed
Account holder name
Billing address
Email address on account
Your birthday
Timeline
GetHuman1334725 started working on this issue
Oct 12th 8:16pm
GetHuman1334725 indicated the issue is not fixed yet.
Oct 13th 8:46pm