New Matches Coming In

[Mlawton]

I think I will just wait until tomorrow. I sent a message. Surely this is a glitch and I should have a match to somebody at some point, right? I tested at Ancestry because it was cheap and got matches right away and I know Ftdna has a much larger database. I guess I will just log out and wait and see what happens tomorrow. Hopefully that email was sent in error, and my results are still being processed....

[blejerh]

My mother's FF test is another of the ones that were stated to be complete yesterday (7/19) but lo and behold I am not a match to my mother and she only has 5 matches whereas I have over 700 so far. I was flabbergasted, so reading this thread and the one I started very early this morning reassured me that this is just a glitch.

[LindaT]

At least they seem aware that something is wrong. We had a transfer complete yesterday and had no matches at all (which was unexpected given 450 on 23andMe). Today when I tried to log in to check it says Family Finder is offline for maintenance.

Hopefully they can resolve the problem soon!

[T E Peterman]

I just called Family Tree DNA & learned that they have taken the whole Family Finder display system offline, while their IT department works on resolving a problem that involved about 1200 erroneous results upload from yesterday.

I commend them for doing this, rather than letting users see erroneous matches.

Timothy Peterman

[Taz85]

I just called Family Tree DNA & learned that they have taken the whole Family Finder display system offline, while their IT department works on resolving a problem that involved about 1200 erroneous results upload from yesterday.

I commend them for doing this, rather than letting users see erroneous matches.

Timothy Peterman

Even PF is down. Did they say how long it will be down??

[T E Peterman]

No Estimated Time given; probably depends on how severe the problem is. I hope this doesn't affect previously allocated matches (like what happened last October).

Timothy Peterman

[shandy4473]

Hopefully not severe

On past batch 464 - someone I was helping out didn't match to their, supposedly, first half cousins. I was left with the conclusion that this person was not related to them.

I hope maybe a rerun of that batch 464 will produce different results.


Steve

[Taz85]

I wonder if this found issue has been effecting matches for while or if this is a recent issue.

[T E Peterman]

If the "issue" resolution results in new matches that we haven't been receiving, that will be nice; but if it means that a bunch of invalid matches have been posted in past weeks, that will be frustrating.

Timothy Peterman

[Táltos]

No Estimated Time given; probably depends on how severe the problem is. I hope this doesn't affect previously allocated matches (like what happened last October).

Timothy Peterman

Wow this is kind of scary that maybe all of our results might be wrong, and we could lose some. Will be good to gain some, but still....

Like I posted yesterday right before the chromosome browser went down I noticed that I lost 1 of my matches, and when I called FTDNA they acted like it was nothing from their end, and now with all this chaos with Family Finder I don't buy that.

I really hope this gets resolved soon. And I wonder if they are having problems because they seem to be a little speeder in their results.

[T E Peterman]

Actually, I'm fairly certain this is a different type of problem. Last October, Family Tree DNA discovered a problem with one of their formulas that determined the calculation os cm length. When they corrected that, a few matches (maybe 1% to 5%) disappeared & for most, these were "relatives" with whom no connection could be found.

This time, it seems to be a problem with matching the 1200 or so that came in Thursday with the rest of the FF database. Sounds like more of an IT problem, than a formula problem.

Timothy Peterman

[T E Peterman]

...of cm length...

Timothy Peterman

[Táltos]

Actually, I'm fairly certain this is a different type of problem. Last October, Family Tree DNA discovered a problem with one of their formulas that determined the calculation os cm length. When they corrected that, a few matches (maybe 1% to 5%) disappeared & for most, these were "relatives" with whom no connection could be found.

This time, it seems to be a problem with matching the 1200 or so that came in Thursday with the rest of the FF database. Sounds like more of an IT problem, than a formula problem.

Timothy Peterman

I hope it is only an IT problem. I'm just more concerned now because my Family Finder only came in the batch prior to this weeks. I'm in 468, my results all were completed on July 6th. It also looks like some other people who are in my same batch just started to get their results in the past few days.

It was just real strange that I noticed that I lost 1 match, right before all the chaos started.

[MoberlyDrake]

It did look like some sort of problem with matching the newest batch to the rest of the database to me yesterday.

I remember when another company got a plate of samples turned around and females received Y-DNA results etc.! This doesn't look like that has happened, because the 2 matches in my father's newly posted results yesterday were both Italian, which is what I would expect for a man who is the son of Italian immigrants. It's just that he didn't match me, my cousin, or any of the few Italian matches the two of us have - all kits that have been in the database for quite some time.

I just hope they get it cleared up soon!

Carol Anne

[Mlawton]

So I guess FF is still offline? I just got 2 emails saying the same thing..that my YDNA 12 marker was in. I ordered YDNA 67 but I guess the rest isn't complete yet. Still when I go and look at the 12 marker, it tells me no matches. Is that odd? I thought the 12 marker cast the net far and wide. Still new and trying to figure it out....