Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Deadenylation-dependent mRNA decay

R-HSA-429914 in Reactome release 97: under Metabolism of RNA, with 56 genes placed in it by the mapping files and 3 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-MMU-429914 (mouse), R-RNO-429914 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this human pathway

The mapping files place 56 genes in this human pathway; showing 1 to 56, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneCNOT1AuthorityHGNC:7877Mapping file id23019 NCBI fileEvidenceTAS
GeneCNOT10AuthorityHGNC:23817Mapping file id25904 NCBI fileEvidenceTAS
GeneCNOT11AuthorityHGNC:25217Mapping file id55571 NCBI fileEvidenceTAS
GeneCNOT12AuthorityHGNC:19081Mapping file id85456 NCBI fileEvidenceTAS
GeneCNOT2AuthorityHGNC:7878Mapping file id4848 NCBI fileEvidenceTAS
GeneCNOT3AuthorityHGNC:7879Mapping file id4849 NCBI fileEvidenceTAS
GeneCNOT4AuthorityHGNC:7880Mapping file id4850 NCBI fileEvidenceTAS
GeneCNOT6AuthorityHGNC:14099Mapping file id57472 NCBI fileEvidenceTAS
GeneCNOT6LAuthorityHGNC:18042Mapping file id246175 NCBI fileEvidenceTAS
GeneCNOT7AuthorityHGNC:14101Mapping file id29883 NCBI fileEvidenceTAS
GeneCNOT8AuthorityHGNC:9207Mapping file id9337 NCBI fileEvidenceTAS
GeneCNOT9AuthorityHGNC:10445Mapping file id9125 NCBI fileEvidenceTAS
GeneDCP1AAuthorityHGNC:18714Mapping file id55802 NCBI fileEvidenceTAS
GeneDCP1BAuthorityHGNC:24451Mapping file id196513 NCBI fileEvidenceTAS
GeneDCP2AuthorityHGNC:24452Mapping file id167227 NCBI fileEvidenceTAS
GeneDCPSAuthorityHGNC:29812Mapping file id28960 NCBI fileEvidenceTAS
GeneDDX6AuthorityHGNC:2747Mapping file id1656 NCBI fileEvidenceTAS
GeneDIS3AuthorityHGNC:20604Mapping file id22894 NCBI fileEvidenceTAS
GeneEDC3AuthorityHGNC:26114Mapping file id80153 NCBI fileEvidenceTAS
GeneEDC4AuthorityHGNC:17157Mapping file id23644 NCBI fileEvidenceTAS
GeneEIF4A1AuthorityHGNC:3282Mapping file id1973 NCBI fileEvidenceIEA, TAS
GeneEIF4A2AuthorityHGNC:3284Mapping file id1974 NCBI fileEvidenceIEA, TAS
GeneEIF4A3AuthorityHGNC:18683Mapping file id9775 NCBI fileEvidenceIEA, TAS
GeneEIF4BAuthorityHGNC:3285Mapping file id1975 NCBI fileEvidenceIEA, TAS
GeneEIF4EAuthorityHGNC:3287Mapping file id1977 NCBI fileEvidenceIEA, TAS
GeneEIF4G1AuthorityHGNC:3296Mapping file id1981 NCBI fileEvidenceIEA, TAS
GeneEXOSC1AuthorityHGNC:17286Mapping file id51013 NCBI fileEvidenceTAS
GeneEXOSC2AuthorityHGNC:17097Mapping file id23404 NCBI fileEvidenceTAS
GeneEXOSC3AuthorityHGNC:17944Mapping file id51010 NCBI fileEvidenceTAS
GeneEXOSC4AuthorityHGNC:18189Mapping file id54512 NCBI fileEvidenceTAS
GeneEXOSC5AuthorityHGNC:24662Mapping file id56915 NCBI fileEvidenceTAS
GeneEXOSC6AuthorityHGNC:19055Mapping file id118460 NCBI fileEvidenceTAS
GeneEXOSC7AuthorityHGNC:28112Mapping file id23016 NCBI fileEvidenceTAS
GeneEXOSC8AuthorityHGNC:17035Mapping file id11340 NCBI fileEvidenceTAS
GeneEXOSC9AuthorityHGNC:9137Mapping file id5393 NCBI fileEvidenceTAS
GeneHBS1LAuthorityHGNC:4834Mapping file id10767 NCBI fileEvidenceTAS
GeneLSM1AuthorityHGNC:20472Mapping file id27257 NCBI fileEvidenceIEA, TAS
GeneLSM2AuthorityHGNC:13940Mapping file id57819 NCBI fileEvidenceIEA, TAS
GeneLSM3AuthorityHGNC:17874Mapping file id27258 NCBI fileEvidenceIEA, TAS
GeneLSM4AuthorityHGNC:17259Mapping file id25804 NCBI fileEvidenceIEA, TAS
GeneLSM5AuthorityHGNC:17162Mapping file id23658 NCBI fileEvidenceIEA, TAS
GeneLSM6AuthorityHGNC:17017Mapping file id11157 NCBI fileEvidenceIEA, TAS
GeneLSM7AuthorityHGNC:20470Mapping file id51690 NCBI fileEvidenceIEA, TAS
GeneNT5C3BAuthorityHGNC:28300Mapping file id115024 NCBI fileEvidenceTAS
GenePABPC1AuthorityHGNC:8554Mapping file id26986 NCBI fileEvidenceIEA, TAS
GenePAIP1AuthorityHGNC:16945Mapping file id10605 NCBI fileEvidenceIEA, TAS
GenePAN2AuthorityHGNC:20074Mapping file id9924 NCBI fileEvidenceTAS
GenePAN3AuthorityHGNC:29991Mapping file id255967 NCBI fileEvidenceTAS
GenePARNAuthorityHGNC:8609Mapping file id5073 NCBI fileEvidenceTAS
GenePATL1AuthorityHGNC:26721Mapping file id219988 NCBI fileEvidenceIEA, TAS
GeneSKIC2AuthorityHGNC:10898Mapping file id6499 NCBI fileEvidenceTAS
GeneSKIC3AuthorityHGNC:23639Mapping file id9652 NCBI fileEvidenceTAS
GeneSKIC8AuthorityHGNC:30300Mapping file id80349 NCBI fileEvidenceTAS
GeneTUT4AuthorityHGNC:28981Mapping file id23318 NCBI fileEvidenceIEA
GeneTUT7AuthorityHGNC:25817Mapping file id79670 NCBI fileEvidenceIEA
GeneXRN1AuthorityHGNC:30654Mapping file id54464 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, TAS, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the human pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.