Ftdna I1 to Haplogroup J Glitch

**mwauthy** · 01-31-2020, 05:39 PM

There is some kind of technical glitch going on with the Ftdna Haplotree where previously assigned I1 downstream folks are now being assigned to haplogroup J. Just scroll down the results of the first page in the I1 project to see examples. I hope this gets fixed soon because it’s confusing a lot of people.

**deadly77** · 01-31-2020, 05:44 PM

Originally Posted by mwauthy

There is some kind of technical glitch going on with the Ftdna Haplotree where previously assigned I1 downstream folks are now being assigned to haplogroup J. Just scroll down the results of the first page in the I1 project to see examples. I hope this gets fixed soon because it’s confusing a lot of people.

Yes, we're seeing this in the I-Z140 project. it's affected 38 folks out of 908, mostly show showing as J-L136 but one showing as J-817 and one J-M267 (although it looks like the latter is actually hg J for real and joined our project by mistake...) - it's spread among the subclades but all the people it affects seem to have done Big Y. Also folks in I-P109 have seen it so it appears to be all over.

There's a couple of things I can think of - FTDNA's system can't handle two different SNP mutations at the same position, so that could be the problem. Another possibility is that this is a recurrent mutation that appears in more than one haplogroup - this is known and there are several examples. YFull allows recurrent SNPs in 5 or less "localizations" but excludes SNPs from it's reliable list if it appears in more than that.

Or it could be that someone just pressed the wrong button...

oz · 01-31-2020, 06:08 PM

A whole bunch of I1s just disappeared.

**spruithean** · 01-31-2020, 06:11 PM

Probably just an error with the software or something. It’s not like it actually changed their haplogroup. You could check your SNP results or your Big Y results and determine for yourself what the situation is. That and the 8-9-8 STR string in all I1s.

**mwauthy** · 01-31-2020, 06:11 PM

Originally Posted by deadly77

Yes, we're seeing this in the I-Z140 project. it's affected 38 folks out of 908, mostly show showing as J-L136 but one showing as J-817 and one J-M267 (although it looks like the latter is actually hg J for real and joined our project by mistake...) - it's spread among the subclades but all the people it affects seem to have done Big Y. Also folks in I-P109 have seen it so it appears to be all over.

There's a couple of things I can think of - FTDNA's system can't handle two different SNP mutations at the same position, so that could be the problem. Another possibility is that this is a recurrent mutation that appears in more than one haplogroup - this is known and there are several examples. YFull allows recurrent SNPs in 5 or less "localizations" but excludes SNPs from it's reliable list if it appears in more than that.

Or it could be that someone just pressed the wrong button...

My first cousin got switched to J-L136. According to YFull there are 3 different SNPs at this location. We are positive for MF37714 but are negative for the other two which includes L136. So I thought this might be the issue but it doesn’t account for why it’s affecting family members differently or why some people are being assigned to different J subclades besides L136.

To confuse things further when I search L136 on Ftdna it says we are both positive for it yet only my cousins Haplotree changed. Furthermore, it says we are positive for L136 even though our genotyped alleles are the same as the reference alleles which doesn’t make any sense so maybe indeed someone pressed the wrong button lol?

**JMcB** · 01-31-2020, 09:00 PM

Coincidentally, they’re updating my branch today. So maybe it’s my fault! I screwed them up so bad, they’re changing everyone into J-L136!

oz · 01-31-2020, 10:00 PM

Whatever it is it's very odd.

**mwauthy** · 01-31-2020, 10:15 PM

Originally Posted by oz

Whatever it is it's very odd.

Agreed! It started yesterday too so apparently it’s not an easy or immediate fix.

oz · 01-31-2020, 10:46 PM

And what's up with their A-T haplogroup bracket? It's missing C, G and I Hgs. Is someone drunk over there? Are we being trolled?

**romelson** · 01-31-2020, 10:50 PM

In I1 project there is also four guys who got the haplogroup IJ-P124. For one of them, TMRCA with his cousin went from ab.100 years to 42.000 years.

Thread: Ftdna I1 to Haplogroup J Glitch

Thread Tools

Display

Ftdna I1 to Haplogroup J Glitch

The Following 5 Users Say Thank You to mwauthy For This Useful Post:

The Following 4 Users Say Thank You to deadly77 For This Useful Post:

The Following User Says Thank You to oz For This Useful Post:

The Following User Says Thank You to spruithean For This Useful Post:

The Following 2 Users Say Thank You to JMcB For This Useful Post:

The Following 2 Users Say Thank You to oz For This Useful Post:

The Following User Says Thank You to mwauthy For This Useful Post:

The Following 2 Users Say Thank You to oz For This Useful Post:

The Following 3 Users Say Thank You to romelson For This Useful Post:

Similar Threads

A glitch with nMonte web runner scaled?

FTDNA Y-dna testers: Please join your appropriate FTDNA Haplogroup Project(s)

Gedmatch question ? Relative or glitch?

FTDNA refuses to assign a haplogroup to this guy

Excel Sheet of Haplotypes Glitch

Posting Permissions