Skip to content
Order

Pathway Human Homo sapiens

TRAF6 mediated IRF7 activation

R-HSA-933541 in Reactome release 97: under DDX58/IFIH1-mediated induction of interferon-alpha/beta, with 30 genes placed in it by the mapping files and 0 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-933541 (mouse), R-RNO-933541 (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 30 genes in this human pathway; showing 1 to 30, 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
GeneCREBBPAuthorityHGNC:2348Mapping file id1387 NCBI fileEvidenceTAS
GeneEP300AuthorityHGNC:3373Mapping file id2033 NCBI fileEvidenceTAS
GeneIFIH1AuthorityHGNC:18873Mapping file id64135 NCBI fileEvidenceTAS
GeneIFNA1AuthorityHGNC:5417Mapping file id3439 NCBI fileEvidenceTAS
GeneIFNA10AuthorityHGNC:5418Mapping file id3446 NCBI fileEvidenceTAS
GeneIFNA13AuthorityHGNC:5419Mapping file idENSG00000233816 Ensembl fileEvidenceTAS
GeneIFNA14AuthorityHGNC:5420Mapping file id3448 NCBI fileEvidenceTAS
GeneIFNA16AuthorityHGNC:5421Mapping file id3449 NCBI fileEvidenceTAS
GeneIFNA17AuthorityHGNC:5422Mapping file id3451 NCBI fileEvidenceTAS
GeneIFNA2AuthorityHGNC:5423Mapping file id3440 NCBI fileEvidenceTAS
GeneIFNA21AuthorityHGNC:5424Mapping file id3452 NCBI fileEvidenceTAS
GeneIFNA4AuthorityHGNC:5425Mapping file id3441 NCBI fileEvidenceTAS
GeneIFNA5AuthorityHGNC:5426Mapping file id3442 NCBI fileEvidenceTAS
GeneIFNA6AuthorityHGNC:5427Mapping file id3443 NCBI fileEvidenceTAS
GeneIFNA7AuthorityHGNC:5428Mapping file id3444 NCBI fileEvidenceTAS
GeneIFNA8AuthorityHGNC:5429Mapping file id3445 NCBI fileEvidenceTAS
GeneIFNB1AuthorityHGNC:5434Mapping file id3456 NCBI fileEvidenceTAS
GeneIKBKEAuthorityHGNC:14552Mapping file id9641 NCBI fileEvidenceTAS
GeneIRF3AuthorityHGNC:6118Mapping file id3661 NCBI fileEvidenceTAS
GeneIRF7AuthorityHGNC:6122Mapping file id3665 NCBI fileEvidenceTAS
GeneMAVSAuthorityHGNC:29233Mapping file id57506 NCBI fileEvidenceTAS
GeneRIGIAuthorityHGNC:19102Mapping file id23586 NCBI fileEvidenceTAS
GeneRNF135AuthorityHGNC:21158Mapping file id84282 NCBI fileEvidenceTAS
GeneSIKE1AuthorityHGNC:26119Mapping file id80143 NCBI fileEvidenceTAS
GeneTANKAuthorityHGNC:11562Mapping file id10010 NCBI fileEvidenceTAS
GeneTBK1AuthorityHGNC:11584Mapping file id29110 NCBI fileEvidenceTAS
GeneTRAF2AuthorityHGNC:12032Mapping file id7186 NCBI fileEvidenceTAS
GeneTRAF6AuthorityHGNC:12036Mapping file id7189 NCBI fileEvidenceTAS
GeneTRIM25AuthorityHGNC:12932Mapping file id7706 NCBI fileEvidenceTAS
GeneTRIM4AuthorityHGNC:16275Mapping file id89122 NCBI fileEvidenceTAS

Evidence codes on this page: 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

Children

None: no pathway of this release's list names this one as a parent.

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.