Sometimes, it is worthwhile to go back to the beginning. The evolution of surnames, family names or last names varies around the world1. As human population increased, the use of surnames turned from a convenience, to a necessity, to a full set of customs and laws with each constituency or culture having its own rules as to how these names are formed, transmitted and used. One common practice held by many West Eurasian societies is that, upon marriage, the couple and their offspring would adopt the father’s surname after the given name. The fact that such a patrilineal surname system is deeply rooted in human culture is self-evident as patronyms (Son of Steven), serving as the first surnames, transformed throughout the generations into modern-day patronymic surnames (Stevenson). Geneticists have been quick to understand that the patrilineal surname system matches the inheritance mode of the Y chromosome2,3,4. Since the Y chromosome is transmitted only from fathers to their sons, it is an ideal genetic locus for purposes such as tracing paternal ancestry and genealogical relatedness among contemporary males5. The absence of Y chromosome recombination enables merging of all contemporary Y chromosome sequences into a single, ever-evolving, phylogenetic tree whose branches are often referred to as haplogroups. Recently, the availability of high-coverage Y chromosome sequences marked a significant transition in the field of phylogenetics, allowing the resolution and understanding of paternal demographic events that were heretofore obscure4,6,7,8,9,10.

Jewish surnames have not been different in their evolution and, among others, are currently comprised of Aramaic and Hebrew patronymic surnames, surnames representing a Diaspora residency or occupation, and modern day Hebraized names11,12. World Jewry, estimated at 14 million individuals, can be roughly divided into Ashkenazi and non-Ashkenazi Jews. The former group is considered to have been formed approximately 2,000 ybp and to account for approximately 75% of contemporary Jews13. Notably, despite this remote split, Ashkenazi and non-Ashkenazi communities share two designations representing the two Jewish priesthood lineages, Levite (Levi, in Hebrew) and Cohen, whose etymologies relate to the Biblical male ancestors Levi and Aaron14. According to the Biblical narrative, Levi was the third son of the Biblical Patriarch Jacob. Levi’s given name was transformed, in time, to the Levite tribal honorific Halevi (The Levite, in Hebrew). One great-grand son of Levi, namely Aaron, was given an honorific to represent his occupation – Cohen (to serve, in Hebrew), the first high priest. Alternative theories for the origins of the Levite caste have been proposed15. While many contemporary Levites still use the Biblical surname form (Levi), the surname continued to evolve throughout the millennia through phonetic spelling variations (e.g. Levin, Lewicki), or through the adoption of a residency location of a specific Levite dynasty as a surname. An illustrative example of the latter is the Horowitz Rabbinical Levite dynasty16 established by the migration of one Levite family from Girona, Catalonia to Horovice, a small town near Prague, Czech Republic, circa 1400 CE. While claims for documented origin in medieval Spain have been made, the founder of the dynasty is considered to be Yeshayah ‘Horovsky’ Ish Horovice (1450–1514 CE)17. Genealogical records of the Horowitz patrilineal dynasty comprising no less than 15 subsequent generations are available17.

Not surprisingly, the Levite and Cohen castes have been the focus of a series of genetic studies during the past two decades using ever-expanding portions of the Y chromosome for the analysis18,19,20,21,22. First, the Cohen dynasty was studied and found to have a limited number of founding lineages that were shared between Ashkenazi and non-Ashkenazi Jews19,21,22. The most frequent Cohen lineage, comprising 46.1% of contemporary, self-identifying Cohen males, is found within haplogroup J1-P58, which is prevalent in the Middle East19. Next, it was shown that the paternal ancestry found among Ashkenazi Levites is dominated by a set of tightly evolving Y chromosome lineages falling within haplogroup R1a-M198 which was, at the time of publication, the most resolved branch known on this evolutionary path18. Other haplogroups reported among Ashkenazi Levites demonstrated no additional significant founding event, and the haplogroup R1a-M198 founder event was not shared with Sephardi Levites. These findings captured the attention of both scientists and laypersons, as the magnitude of the founder effect suggests that fully ~200,000 males with the tradition of Levite descent share a recent common direct male ancestor within recent historical time frames23. Importantly, the initial genetic analyses suggested in this first publication incorrectly attributed this Ashkenazi Levite lineage’s origin to Eastern Europe18. A follow up study, summarizing information from whole Y chromosome sequencing, focused specifically on this Ashkenazi Levite lineage and confirmed that that 65% of the 97 randomly assembled Ashkenazi Levites carried haplogroup R1a-M19820. Strikingly, the better resolved whole Y chromosome based phylogeny of haplogroup R1a, showed that 100% of these samples could be reassigned to the refined haplogroup R1a-M582. This distinctive R1a-M582 lineage was found, other than in Ashkenazi Jews, among 15.7% males self-affiliating as non-Ashkenazi Levites and, importantly, at low frequencies only in the Middle East, consistent with this location as its ancestral origin20.

While the phylogenetic origin of the R1a-M582 lineage was clarified20, the aim of this study is to further explore several questions that remained open regarding this founder lineage among Ashkenazi Levites. First, the limited number of whole Y chromosome sequences from Ashkenazi Levites had precluded a definitive description of their phylogenetic branch, its coalescence time and its route of entrance to Europe (Fig. 1). Second, the ancestral ties between Ashkenazi Jews self-affiliating as Levites and Ashkenazi Jews self-affiliating as non-Levites within haplogroup R1a-M582 remained elusive. Third, the existence of haplogroup R1a-M582 in both Ashkenazi and non-Ashkenazi Levites was not explained. Fourth, lack of whole Y chromosome sequences from other Ashkenazi haplogroups did not allow a comparison between a specific founding event for Ashkenazi Levites and a general expansion of Ashkenazi Jews that also affected the Ashkenazi Levites. Fifth, a comparison between the coalescence ages of the dominant Cohen priesthood J1-P58 lineage shared between Ashkenazi and non-Ashkenazi Jews and the Ashkenazi Levite lineage at the level of the whole Y chromosome sequences was yet to be conducted. Having these objectives in mind, we assembled 486 whole Y chromosome sequences from Ashkenazi Jews with a tradition of Levite descent (Supplemental Table S1), including members of the Horowitz rabbinical dynasty, Ashkenazi Jews without a tradition of Levite descent, non-Ashkenazi Jews and non-Jews. Of these, 179 are novel, including 65 R1a-M582 samples that were collected following expert genealogical input. This set of 65 samples consists of males with 56 different surnames, who claim to have an Ashkenazi Levite paternal origin. Samples were chosen to include the widest possible range of haplogroup R1a-M582 internal variation based on their previously available short tandem repeat (STR) haplotypes (Supplemental Table S2). Additional samples were included to provide the appropriate phylogenetic framework for the studied haplogroups.

Figure 1
figure 1

Origin and expansion of the Ashkenazi Levite Y chromosome clade. The suggested gradual movement and expansion pattern of the Ashkenazi Levite haplogroup R1a-Y2619 are denoted by ascending numerical labels. An ancestral origin in the Middle East (1) is followed by a migration route (purple arrows) paralleling the dispersal of Ashkenazi Jews to Europe (2). Expansion within the Ashkenazi Jewish population in Europe (3) is followed by a paternal gene flow of R1a-Y2619 Y chromosomes to non-Ashkenazi Jewish communities (4). A second theoretical expansion route of Levites from the Middle East to Europe (5) via the expansion of non-Ashkenazi Jews is shown but not supported by the obtained results. Map data is from ©2017 Google Maps.


The Ashkenazi Levite phylogenetic branch

All R1a-M582 Y chromosomes sampled from Ashkenazi Levites, non-Ashkenazi Levites, Ashkenazi non-Levites, and non-Jews with known or suspected Ashkenazi origin established a well-defined phylogenetic branch nested within haplogroup R1a-M582 and demonstrated a star-like expansion pattern (Fig. 2 and Supplemental Figure S1). The root of this branch is defined by a total of six polymorphic sites and designated according to one of the positions, R1a-Y2619 (g.6733896A>G) coalescing 1,743 (1,334–2,200) ybp (Table 1). The five non-Ashkenazi Levites and the single Iraqi Jew did not establish a distinct phylogenetic cluster but scattered within the Ashkenazi Levite samples. The sister clades of R1a-Y2619 within R1a-M582, coalescing ~3,143 (2,620–3,682) ybp, were sampled in Iranian Azeris, a Kerman, a Yazidi and one sample from Iberia. Further, the phylogeny demonstrates a rich diversity of R1a samples distributed throughout the Middle East, Anatolia, Caucasus and the Indian sub-continent, whereas East European branches represent an early split within R1a.

Figure 2
figure 2

The Ashkenazi Levite clade. (a) Haplogroup R1a phylogeny comprising 170 samples is illustrated to nest the refined Ashkenazi Levite clade R1a-Y2619. The phylogeny and coalescence times (Y axis) were calculated using the software package BEAST v.1.7.5. The Ashkenazi Levite R1a-Y2619 clade coalesces 1,743 (1,334–2,200) ybp. Each terminal branch represents one sample (Supplemental Figure S1). The single arrow points to a sample sequenced by both the Complete Genomics and Illumina platforms. Samples highlighted by a blue star are from non-Ashkenazi Levites. The area shaded in blue represents the sub-Ashkenazi Levite clade nesting all the samples self-affiliating as belonging to the Horowitz pedigree (Fig. 3). The area shaded in red is magnified in (b) and details the ancestries of the individuals making the Ashkenazi paraphyletic clades within haplogroup R1a-M582.

Table 1 Coalescence times of most relevant haplogroups to the Ashkenazi expansion. Bayesian estimations of ages are expressed in ybp with 95% HPD intervals.

We then explored the allocation of the Horowitz Levite samples included in the phylogeny. First, the six tested Horowitz Levites were grouped into the Y chromosome haplogroup R1a-Y2619, allowing a unique glimpse into medieval Europe (Fig. 3a). The genealogic records for three of the individuals with the Horowitz surname converged to a common male ancestor born at 1615 CE or 402 ybp (Fig. 3b). The observed sequence variation between these three samples is consistent with this proposed genealogy (Fig. 3c), and accordingly, their genealogical claim could not be refuted. This prompted us to use this node as an internal calibration point. The two additional individuals affiliating with the Horowitz dynasty formed the closest paraphyletic clade R1a-YP268 to the described three sample cluster, coalescing with them 691 (555–852) ybp (Fig. 3c). The sixth sample carrying the Horowitz surname but claiming no ancestral relations with the Horowitz dynasty did not cluster with these five samples (Supplemental Figure S1).

Figure 3
figure 3

The Horowitz Levite pedigree. (a) The presumed migration route of the first named founder of the Horowitz pedigree from Girona to Horovice, circa 1400 CE, is shown. (b) A total of five individuals self-affiliated as descendants of the pedigree. Of these, three individuals supplied detailed written genealogies showing the ancestral relatedness among them. These three individuals are highlighted by the green, yellow and blue colors, and the noted birth years of their ancestors are noted. The node noted by the blue star symbol was used as an internal calibration point for the R1a phylogeny (Fig. 1). (c) The obtained YP268 clade phylogeny including all five Horowitz Y chromosomes is shown to coalesce 690 (555–852) ybp. The respective allocations of the three individuals comprising the written genealogies are noted by the same colors. The digits to the left of the branches denote the number of mutational events observed in each branch (Supplemental File 1). The two additional individuals are noted in red. The dashed double-headed arrow points to the YP268 node and the first named ancestor of Horowitz pedigree. Map data is from ©2017 Google Maps.

Additional Ashkenazi Y chromosome haplogroups

We further studied the major Y chromosome haplogroups found among Ashkenazi Jews24 to shed light on their origin and expansion times in comparison to the findings obtained for the R1a lineages among the Levites.

Haplogroup J grants the largest overall contribution to the Ashkenazi paternal gene pool, accounting for 38% of the total variation19,21,22. The haplogroup J phylogeny, including its two major sub-branches J1 and J2, is presented in Supplemental Figure S2. We first focused on J1-M267 and particularly on the Cohen lineage nested with haplogroup J1-P5819. A total of five Ashkenazi and five non-Ashkenazi novel Cohen J1-P58 samples were included in the analysis. Remarkably, the five Ashkenazi Cohen samples formed the tight cluster J1b-B877, shared only with one Yemenite, one Bulgarian and one Moroccan Cohen coalescing ~2,570 ybp (Table 1). Additional J1-P58 samples from Jews clustered within this branch or within other J1-P58 sub-branches. Both the paraphyletic haplogroups and the clades within which the Ashkenazi Cohen samples were nested, were of clear Middle Eastern origin. Another minor Cohen haplogroup has been previously described within haplogroup J2-M1219. The three J2-M12 samples included in this study share the deep clade J2b-M241 with one Albanian sample coalescing ~5,442 ybp (Table 1). Two of the three Cohen J2-M12 samples coalesced ~1,836 ybp (Supplemental Figure S2). Interestingly, the third sample shares the clade J2b-B239 with two Cochin Jews, coalescing ~1,455 ybp (Table 1). This finding provides the first evidence of an instance of shared paternal ancestry between Ashkenazi and Cochin Jews claiming to have resided in Kerala, India, since biblical times. Last, a minor, previously described Cohen J-M318 haplotype specific to the Tunisian island of Djerba24, is now phylogenetically fully characterized and the two included samples coalesce ~1,645 ybp (Table 1) with one mainland Tunisian Jew, whose Cohen status is unknown.

The phylogeny of haplogroup E, comprising 20.4% of the paternal variation found among Ashkenazi Jews24, demonstrates a complex pattern of a few, well defined, evolving sub-haplogroups (Supplemental Figure S3). As expected, the Ashkenazi samples were distributed among various sub-E haplogroups24. The emerging pattern is of a complex demographic history. A few well-defined recent lineages coalesce ~1,604, ~1,476, ~1,302 and ~1,208 ybp within haplogroups E-Z838, E- PF3780, E- B923 and E-B933 (Table 1), respectively, alongside deep-rooted branches suggesting their long existence within Ashkenazi Jews. Non-Ashkenazi Jewish samples found within these haplogroups primarily coalesce with the Ashkenazi samples in time periods that antedate the arrival of the latter to Northeast Europe.

Haplogroup G-M377, found in 9.7% of contemporary Ashkenazi males24, coalesces ~5,757 ybp (Supplemental Figure S4). The Ashkenazi samples clustered only with other Ashkenazi samples reported elsewhere and could be refined here to haplogroup G-BY764 coalescing ~1,223 ybp (Table 1). Interestingly, the closest Y chromosome within G-M377 is from a Punjabi male. The phylogeny obtained for haplogroup Q-M378 comprising 5.2% of the Ashkenazi paternal variation24, shows a similar pattern to that observed for haplogroup G-M377 (Supplemental Figure S5). Herein five new Jewish sequences from three Ashkenazi, one Moroccan and one Yemenite Jew are presented. The Yemenite Jewish sample seems to fall within the central Asian and Indian sub-continent variety. The three Ashkenazi samples form a tight cluster Q3-B853, coalescing ~1,672 ybp, that was shared only with a previously reported Ashkenazi sample (Table 1). The sequence from a Moroccan Jew and a previously reported sample of unclarified ancestry form the closest branch coalescing with the Ashkenazi samples ~4,007 ybp. The deep split of this Jewish cluster from its closest sister clade is ~32,431 ybp, leaving the phylogenetic origin of this lineage enigmatic. This pattern might suggest an occasional survival of remote splits within a population residing in, or transiting through, the Levant that have survived in small frequencies among contemporary Ashkenazi Jews.

The phylogeny of haplogroup T-M70 bears a few deep-rooted branches shared by Ashkenazi, non-Ashkenazi, and non-Jewish samples (Supplemental Figure S6). The diversity of this haplogroup attests to its long presence within Jewish populations at time frames that predate the Jewish Diaspora25.

The phylogeny of haplogroup R1b-M269 shows the presence of this haplogroup in various Jewish communities. The Ashkenazi samples clustered primarily with European R1b samples or created recently forming clusters. This pattern might be compatible with repeated introgression of non-Jewish European R1b Y chromosomes into the Ashkenazi Jewish population (Supplemental Figure S7).


Cumulatively, the extensive number of samples assembled herein, combined with the availability of very highly resolved paternal phylogenies extending back many generations, have enabled certain inferences about the Ashkenazi Levite haplogroup R1a founding lineage to be formulated with a high degree of confidence. A total of 71 individuals declaring an Ashkenazi Levite or Ashkenazi non-Levite paternal heritage were ascertained at the inception of the study to belong to haplogroup R1a-M582, and based on their STR profiles, to represent a broad range of the variation found within that haplogroup. Strikingly, all 71 Y chromosomes could be reassigned to a single expanding clade nested within R1a-M582 and labeled herein R1a-Y2619, following one of the six variants found at that level (Fig. 2 and Supplemental Figure S1). The only previously reported samples who shared this clade were five samples of Ashkenazi Jewish heritage for which the Levite status was not reported26. Accordingly, all R1a-Y2619 individuals, whether self-affiliating as Jews or non-Jews, whether Ashkenazi or non-Ashkenazi, whether Levites or non-Levites, are the direct male descendants of the paternal line of one common male ancestor who lived ~1,743 ybp (Table 1). As contemporary males from all branches of R1a-Y2619 sampled so far carry one of the many Levites surnames, it can be strongly argued that this male ancestor self-affiliated as a Levite and may have carried the patronymic surname Levite. The magnitude of the founding event can be estimated by calculating the number of contemporary individuals expected to carry an R1a-Y2619 Y chromosome. Two independent sample sets of Ashkenazi Jews in which the Levite status was unknown have similarly estimated the percentage of the R1a-Y2619 paternal haplogroup, R1a-M17/M198, in the Ashkenazi population at 9.6%20 and 11.5%, respectively27. The former paper reported that haplogroup R1a-M582 accounted for 7.9% of the total Ashkenazi population20. Here, we show that all Ashkenazi samples belonging to haplogroup R1a-M582 can be reclassified as R1a-Y2619. Based upon an Ashkenazi population size of ~4,000,00013 males, of whom about 7.9% are R1a-Y2619, there would be ~300,000 Ashkenazi males descending on their direct male line from a single relatively recent ancestor, with many of those men self-affiliating as Levite.

Two factors enabled us to achieve more accurate coalescence ages and confidence intervals than previously calculated for the Ashkenazi Levite R1a lineage18,20. First, the large number of whole Y chromosomes available (Supplemental Table S1), and second, the data available from the Horowitz pedigree that allowed an internal calibration point (Fig. 3). The well-documented genealogical records of the Horowitz pedigree demonstrate how robust whole Y chromosome sequences can be in reconstructing paternal ancestries. The calibration point was based on three Horowitz samples with well-documented genealogies coalescing 402 ybp. Two additional individuals, self-affiliating with the Horowitz dynasty, but without clear genealogies clustered tightly with these three samples. None of the samples in the immediate sister clades self-identified as part of the Horowitz dynasty. Strikingly, the molecular age of the node comprising all five Horowitz samples was calculated to be ~690 ybp, while the genealogical coalescence time suggests it to be 546 ybp. This suggests that the Horowitz node R1a-YP268 (g.23133909G > A) might represent the actual reconstructed whole-Y sequence of the named founder of this pedigree (Fig. 3b). However, it is important to note that the estimated coalescence ages are approximate, as a few methodological variations may lead to somewhat different results. For example, the application of our coalescence methodology to the data obtained from the Illumina platform alone, would have yielded a coalescence age of ~1,398 ybp for the Ashkenazi Levite R1a-Y2619 clade and ~645 years ybp for the R1a-YP268 clade. Such differences might be attributable to the ability to use longer overlapping stretches of the Y chromosome when comparing samples sequenced by the same machinery and parameters. We did not calculate a coalescence time based on STR variations, as we have previously shown they provide no further information for recently coalescing clades6.

The proposed Middle Eastern origin of the Ashkenazi Levite lineage based on what was previously a relatively limited number of reported samples20, can now be considered firmly validated. While the highest frequencies of haplogroup R1a are found in Eastern Europe18,28, our data revealed a rich variation of haplogroup R1a outside of Europe which is phylogenetically separate from the typically European R1a branches. Evidently, R1a-Y2619 is well nested within a plethora of phylogenetically close Middle Eastern sister-clades, sampled in Iranian Azeris, a Kerman, a Yazidi and one man from Iberia. This provides the needed evidence for its origin (Fig. 2 and Supplemental Figure S1). However, the exact migration pathway of R1a-Y2619 to Europe remains elusive. Most historical records suggest two major routes of Jewish migration to Europe (Fig. 1)29,30. Ashkenazi Jewry is considered to have been founded as the result of Jewish migration via Italy to the Rhine Valley, and then Poland. Sephardic (Spanish) Jews are considered to have migrated along with the gradual Islamic expansion to North Africa and then Spain14. Because R1a-Y2619 is of Middle Eastern origin, it is possible that its introduction to Europe was by either, or both, of these routes. Naturally, the strong founding event for R1a-Y2619 among Ashkenazi Jews, coupled with the presence of all known branches of R1a-Y2619 in Ashkenazi Jews, tempts to infer that its migration route from the Levant was directly related to the Ashkenazi founders. However, these facts might merely reflect an expansion within Ashkenazi Jews rather than a proof of first arrival of the R1a-Y2619 with or into the Ashkenazi population. More confusing is the fact that genealogical records of the Horowitz rabbinical dynasty, now shown to carry the R1a-Y2619 Y chromosome, suggest their presence in the Iberian Peninsula in the 15th century and probably earlier (Fig. 3)17. In fact, repeated Jewish migrations that might have carried R1a-Y2619 Y chromosomes to Catalonia are documented since the 4th century and during the Muslim expansion to Iberia31. Additionally, because Catalonia was again Christian territory since 800 CE, proto-Horowitz R1a-Y2619 ancestors could also represent migration of Ashkenazi Jews to Iberia. Accordingly, the presence of R1a-Y2619 in Spain in the 15th century could not establish proof for the first arrival of the R1a-Y2619 lineage to the Iberian Peninsula, as this could simply reflect repeated and unrecorded movements of Jews back and forth between Eastern and Western Europe and the Iberian Peninsula. Previous evidences from mtDNA and autosomal markers have already suggested a likely gene flow between Ashkenazi and Sephardic Jews within Europe32,33,34. Taken together, our results tend to favor a single route of entry to Europe as part of the Ashkenazi migration and expansion in Europe. Because the coalescence time of all contemporary R1a-Y2619 Levites is ~1,743 ybp, well within the time of the Roman exile Diaspora, and each of the branches of R1a-Y2619 is found in Ashkenazi Jews, our results are inconsistent with a scenario of rapid expansion in the Levant followed by a spread via multiple routes to Europe. The results from the non-Ashkenazi R1a-Y2619 Levite samples also suggest single expansion route. Had the R1a-Y2619 Levite lineage already been as widely prevalent in the Levant, the non-Ashkenazi Levites would have been expected to split from the Ashkenazi Levite samples prior to the time of the Diaspora and to form a different cluster. However, the results show that the non-Ashkenazi Levites fall within multiple relatively recently coalescing sub-branches of R1a-Y2619 (Fig. 2 and Supplemental Figure S1). This pattern is more compatible with continuous gene flow from the Ashkenazi population to the non-Ashkenazi population during the Diaspora, rather than multiple routes of entrance for haplogroup R1a-Y2619 to Europe from the Levant.

Further support for a single migration route and subsequent expansion within Ashkenazi Jews, emanates from the observed patterns of expansion of additional Ashkenazi haplogroups. Accordingly, it is important to distinguish between an Ashkenazi Levite specific founding event for haplogroup R1a-Y2619 which could have been the result of a favorable socio-economic or other status, and a general expansion of Ashkenazi founding Y chromosome lineages, including R1a-Y2619 Ashkenazi Levites. For this purpose, we have studied a handful of other haplogroups previously described to be prevalent among Ashkenazi Jews19,24,35. Our results show that the expansion of R1a-Y2619 among Ashkenazi Jews is not specific or unique to this haplogroup. For example, the coalescence of haplogroup G-M377 (Supplemental Figure S4) and Q-M242 (Supplemental Figure S5), known to each represent 5% of the Ashkenazi paternal variation24, coalesce at ~1,223 ybp and ~1,672 ybp, respectively (Table 1). The Y chromosome strategy adopted herein allowed us to resolve haplogroup E lineages into its minute sub-branches (Supplemental Figure S3). The coalescence ages of haplogroup E-Z838, E- PF3780, E- B923 and E-B933, known to cumulatively represent 20% of the Ashkenazi paternal variation24, were estimated at ~1,200–1,600 ybp. This pattern of multiple founding events, not observed among Spanish Jews36 provides further support that the R1a-Y2619 Ashkenazi Levite ancestor entered Europe via the Ashkenazi route rather than via the Jewish expansion to the Iberian Peninsula. Other patterns are also clearly visible in the Ashkenazi Jewish paternal ancestry. Haplogroup T-M70, prevalent in the Middle East, is also present among Ashkenazi Jews (Supplemental Figure S6). The genotyped samples showed deeply rooted splits probably pointing to the preservation of an ancient diversity of this haplogroup in the Levant, dating back to Pleistocene. Meanwhile, the pattern observed for haplogroup R1b-M269 (Supplemental Figure S7), prevalent in Western Europe, primarily suggests repeated punctuated introgression of European Y chromosomes to the Ashkenazi community, and is compatible with previous reports36.

We further compared the most frequent founding lineage found among Ashkenazi Cohen males, nested within haplogroup J1a-P58, to the Ashkenazi Levite R1a-Y2619 lineage. Evidently, members of the R1a-Y2619 Levite caste and the J1a-P58 Cohen caste do not share a common male ancestor within the time frame of the Biblical narrative. As in the case of the Ashkenazi Levites, the Ashkenazi Cohen J1a-P58 lineage formed a tight cluster nested within a Middle Eastern set of samples confirming its origin, and was shared in our study only with non-Ashkenazi Cohens (Supplemental Figure S2). However, differently from the pattern obtained for R1a-Y2619 Ashkenazi Levites, the cluster coalesces ~2,570 ybp, thus pointing to the start of its expansion in the pre-Diaspora period. Extensive full Y chromosome sequences from larger number of Cohen samples from more Jewish communities on the background of other Levantine populations, including ascertainment of family and clan specific variants would be very informative in addressing the finding that Ashkenazi and non-Ashkenazi Cohen individuals share an overlapping distribution of lineages. In particular, the study of the most dominant Cohen lineage nested with the prevalent haplogroup J1-P58, along with expert historical input, might grant critical insight to the understanding of Hebrews in the Old World. Furthermore, ancient DNA studies of the Levant may offer direct information. Indeed, a recent study revealed the presence of both J1a-P58 and J2-M12 Y-chromosomes, frequent among contemporary Jews, in two Canaanite samples date to 3,700 ybp37.

It is difficult to simulate the maximal number of males that would have needed to be present at the foundation of Ashkenazi Jewry to yield the strong pattern of founding events currently observed in the Ashkenazi Y chromosome pool. Fundamental indices such as frequencies of the respective haplogroups in the ancestral deme populations and the extent of introgression that has occurred throughout the generations are lacking. However, the contemporary frequencies of these Y chromosome founding lineages, in view of their very much lower frequencies in non-Jewish Middle Eastern and European populations, suggest that such lineages must have been present at the inception of Ashkenazi Jewry, when scant number of males comprised the founding population, and allowing for drift to play a role in establishment of their current high frequencies. Indeed, reconstruction of the recent Ashkenazi Jewish history from whole genomes suggested a bottleneck of merely 350 individuals26,38. It is important to note that while this bottleneck does not necessarily coincide with the founding effective male population size and events for Ashkenazi Jews, it does tell us that the Ashkenazi Levite R1a-Y2619 ancestor was likely among the founding males upon whom the bottleneck applied. Correspondingly, data from complete mitochondrial DNA sequences support the same notion of a limited number of major founding maternal lineages33.

Taken together, the magnitude of the data presented herein facilitates a near complete resolution of the genomic tale of Levites within Ashkenazi Jews. It can be strongly argued that contemporary R1a-Y2619 Ashkenazi Levites descend from a single Levite ancestor who arrived in Europe from the Levant. The expansion of his direct male lineage began in a timeframe compatible with the expansion pattern observed for several additional founding fathers of Ashkenazi Jewry. Thus, in addition to providing insight onto a single male genealogy, these findings are an important and highly resolved example of the more general demographic history of Ashkenazi male and female Jewish lineages, in which a relatively small number of founders make disproportionately large contributions to contemporary Ashkenazi population genomic variation. It can be further argued that the fact that the non-Ashkenazi Levite R1a-Y2619 men are well distributed within the Ashkenazi Levite phylogeny, rather than clustered separately, lends more credence to the scenario that the R1a-Y2619 male entered Europe with the Ashkenazi founders. The most enigmatic question – the timing and location whereby the founder of the Ashkenazi Levite R1a-Y2619 pedigree obtained Levite status – remains unresolved. This question might be beyond the scope of genetic studies using contemporary genetic variation, given the absence to date of any tested men whose lines branched off between the time of the shared direct male ancestor of all R1a-M582 men, ~3,143 ybp, and the shared direct male ancestor of the R1a-Y2619 Ashkenazi Levite men ~1,743 ybp. Future historical or archeological insights might provide the means to further investigate this issue.

Material and Methods


A total of 486 samples from unrelated individuals were assembled, of which 179 are novel and 307 were previously reported (Supplemental Table S1). The study was approved by the Research Ethics Committee of the University of Tartu, Estonia and the Rambam Medical Center in Haifa, Israel. All donors provided informed consent and all experiments were performed in accordance with the relevant guidelines and regulations of the collaborating institutions. First, following expert genealogical advice, a total of 85 novel R1a samples were selected by inspecting a database of over 40,000 R1a samples available at Gene by Gene (Family Tree DNA). The samples were selected based on previously available clade diagnostic variants and STR profiles (Supplemental Table S2) aiming to genotype a broad range of R1a-M582 samples or phylogenetic adjacent sister clades18,20. This tier comprised 60 males with documented paternal Ashkenazi Levite ancestry, five non-Jews with known Ashkenazi Levite paternal origin, four Ashkenazi non-Levites, two non-Jews with known paternal Ashkenazi origin, one Iraqi Jew, and 13 non-Jews from the Middle East, Caucasus and Europe (Supplemental Table S1). Next, 85 additional R1a samples, of which 16 are reported for the first time in this study, were included to provide the relevant framework for the R1a phylogeny. Importantly, five of the 16 novel samples were from non-Ashkenazi Levites. Finally, a total of 316 samples, of which 78 are first reported herein, carrying haplogroups known to be prevalent among Ashkenazi Jews were selected including E-M123, E-M78, E-M81, E-M35*, G-M377, J-M12, J-M267, J-M318, J-M410, J-P58, T-M70, Q-M378, and R-M269. These samples represent the variation found among Jews against the background of a wide set of West Eurasian samples. Where available, the paternal ancestry information of these samples also notes the self-reported Jewish caste with which the donor affiliates, namely, Cohen, Levite or Israelite.

Five samples (Supplemental Table S1) self-affiliated with the Horowitz dynasty of which three presented well documented genealogies. A sixth sample carried the Horowitz family name but claimed no relation to the dynasty.

Five samples (Supplemental Table S1) were run on both the Complete Genomics and Illumina platform to reassure that the data obtained from both platforms could be assembled6.

Whole Y chromosome sequencing

All novel samples were genotyped using the Illumina HiSeq. 2,500 platform following Y chromosome capture using a proprietary capture protocol available at Gene by Gene (Family Tree DNA) using the commercially available “BigY” service (, a targeted enrichment design utilizing 67,000 capture probes for sequencing at least 10 Mbp on the Illumina HiSeq platform at >60x coverage. The targeted regions lie within the non-recombining male-specific parts of the Y chromosome.

Mapping and calling the Y chromosome variants

For mapping and calling the raw paired-end read data we followed the best practices recommended by the SAMtools developers (, starting from BWA MEM mapping to the GRCh37 human reference sequence, ‘decoy’ version (hs37d5), including duplicate read removal with picard-tools-2.0.1 (, indel realignment with GATK-3.5 and finishing with multisample base calling by SAMtools and BCFtools39,40,41. All parameters are detailed in the Supplemental Table S3. Quality filtering was done using vcftools-0.1.12, the default filter settings were used except for the following values: base coverage >4x and <500; base quality >20; distance between SNPs >5 bp.

The novel Y chromosome capture data was combined with high coverage Y chromosomes extracted from previously published human whole genomes sequenced6,26,42,43 at Complete Genomics (Mountain View, California), the 1000 Genomes44 Consortium and the Personal Genomes Project (


We extracted the overlap between the published sequences and the newly generated data and applied our previously published custom filtering scheme6 that concentrates on parts of Y chromosome reachable with NGS (the ‘re-mapping filter’) and minimizes the platform bias when merging datasets. After the filtering, we ended up with 6 million bp of Y chromosome data. We also excluded insertions, deletions and multistate SNPs from the analyses, as well as SNP sites with over 5% of no-calls.

Phylogeny reconstruction

We constructed phylogenies for each Y chromosome haplogroup. Maximum likelihood trees were constructed with RaXML45. All identified variants were annotated based on these trees using in-house scripts followed by manual curation. We estimated the coalescence times with the software package BEAST v.1.7.542. We used a Bayesian skyline coalescent tree prior, the general time reversible (GTR) substitution model with gamma distributed rates, and a stringent clock with uniform distribution for all haplogroups was utilized. Runs were performed with a piecewise-constant coalescent model with the number of groups depending on the number of samples on the particular phylogeny, following the best practices in BEAST usage where the number of groups used is the number of samples divided by a value between 5 to 20, but having no more than 20 groups. The MCMC runs had 200 million iterations that were sampled every 3,000 steps. We ran four parallel runs with different seeds for phylogenies with more than 50 samples and two parallels for the smaller phylogenies. We visualized each BEAST run in Tracer v1.5 and confirmed that all effective sample size (ESS) values were above 200. We used previously published ages for relevant nodes6 as calibration points in each tree. The trees were all visualized using FigTree 1.4.2. ( The BEAST-generated phylogenies present the samples comprising them, the coalescence ages of the nodal positions, and the labels of major branches or branches relevant for this paper. Annotations of the major haplogroups of interest appearing in the BEAST phylogenies follow the published nomenclature6 and are detailed in Supplemental File 1.

Data Availability

The 179 whole Y chromosome sequences reported in this paper are deposited in the European Nucleotide Archive ( under the accession number PRJEB21310.