Skip to content
Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

Toll Like Receptor 4 (TLR4) Cascade

R-MMU-166016 in Reactome release 97: under Toll-like Receptor Cascades, with 119 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-HSA-166016 (human), R-RNO-166016 (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.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

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. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [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 mouse pathway

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

Genes Reactome places in this mouse pathway, page 1 of 2
GeneAgerAuthority11596Mapping file id11596 NCBI fileEvidenceIEA
GeneAlpk1Authority71481Mapping file idENSMUSG00000028028 Ensembl fileEvidenceIEA
GeneAppAuthority11820Mapping file id11820 NCBI fileEvidenceIEA
GeneAtf1Authority11908Mapping file id11908 NCBI fileEvidenceIEA
GeneAtf2Authority11909Mapping file id11909 NCBI fileEvidenceIEA
GeneBirc2Authority11797Mapping file id11797 NCBI fileEvidenceIEA
GeneBirc3Authority11796Mapping file id11796 NCBI fileEvidenceIEA
GeneBpiAuthority329547Mapping file id329547 NCBI fileEvidenceIEA
GeneCasp8Authority12370Mapping file id12370 NCBI fileEvidenceIEA
GeneCd14Authority12475Mapping file id12475 NCBI fileEvidenceIEA
GeneCd180Authority17079Mapping file id17079 NCBI fileEvidenceIEA
GeneChukAuthority12675Mapping file idENSMUSG00000025199 Ensembl fileEvidenceIEA
GeneCreb1Authority12912Mapping file id12912 NCBI fileEvidenceIEA
GeneCul1Authority26965Mapping file id26965 NCBI fileEvidenceIEA
GeneDnm1Authority13429Mapping file id13429 NCBI fileEvidenceIEA
GeneDnm2Authority13430Mapping file id13430 NCBI fileEvidenceIEA
GeneDnm3Authority103967Mapping file id103967 NCBI fileEvidenceIEA
GeneDusp3Authority72349Mapping file id72349 NCBI fileEvidenceIEA
GeneDusp4Authority319520Mapping file id319520 NCBI fileEvidenceIEA
GeneDusp6Authority67603Mapping file id67603 NCBI fileEvidenceIEA
GeneDusp7Authority235584Mapping file id235584 NCBI fileEvidenceIEA
GeneEcsitAuthority26940Mapping file id26940 NCBI fileEvidenceIEA
GeneFaddAuthority14082Mapping file id14082 NCBI fileEvidenceIEA
GeneFbxw11Authority103583Mapping file id103583 NCBI fileEvidenceIEA
GeneFosAuthority14281Mapping file id14281 NCBI fileEvidenceIEA
GeneHmgb1Authority15289Mapping file id15289 NCBI fileEvidenceIEA
GeneIkbkbAuthority16150Mapping file id16150 NCBI fileEvidenceIEA
GeneIkbkeAuthority56489Mapping file id56489 NCBI fileEvidenceIEA
GeneIkbkgAuthority16151Mapping file id16151 NCBI fileEvidenceIEA
GeneIrak1Authority16179Mapping file id16179 NCBI fileEvidenceIEA
GeneIrak2Authority108960Mapping file id108960 NCBI fileEvidenceIEA
GeneIrf3Authority54131Mapping file id54131 NCBI fileEvidenceIEA
GeneIrf7Authority54123Mapping file id54123 NCBI fileEvidenceIEA
GeneItgamAuthority16409Mapping file idENSMUSG00000030786 Ensembl fileEvidenceIEA
GeneItgb2Authority16414Mapping file id16414 NCBI fileEvidenceIEA
GeneJunAuthority16476Mapping file id16476 NCBI fileEvidenceIEA
GeneLbpAuthority16803Mapping file id16803 NCBI fileEvidenceIEA
GeneLrrc14Authority223664Mapping file id223664 NCBI fileEvidenceIEA
GeneLy86Authority17084Mapping file id17084 NCBI fileEvidenceIEA
GeneLy96Authority17087Mapping file id17087 NCBI fileEvidenceIEA
GeneMap2k3Authority26397Mapping file id26397 NCBI fileEvidenceIEA
GeneMap2k4Authority26398Mapping file id26398 NCBI fileEvidenceIEA
GeneMap2k6Authority26399Mapping file id26399 NCBI fileEvidenceIEA
GeneMap2k7Authority26400Mapping file id26400 NCBI fileEvidenceIEA
GeneMap3k7Authority26409Mapping file id26409 NCBI fileEvidenceIEA
GeneMap3k8Authority26410Mapping file id26410 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk10Authority26414Mapping file id26414 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 NCBI fileEvidenceIEA
GeneMapk14Authority26416Mapping file id26416 NCBI fileEvidenceIEA
GeneMapk3Authority26417Mapping file id26417 NCBI fileEvidenceIEA
GeneMapk7Authority23939Mapping file id23939 NCBI fileEvidenceIEA
GeneMapk8Authority26419Mapping file id26419 NCBI fileEvidenceIEA
GeneMapk9Authority26420Mapping file id26420 NCBI fileEvidenceIEA
GeneMapkapk2Authority17164Mapping file id17164 NCBI fileEvidenceIEA
GeneMapkapk3Authority102626Mapping file id102626 NCBI fileEvidenceIEA
GeneN4bp1Authority80750Mapping file id80750 NCBI fileEvidenceIEA
GeneNfkb1Authority18033Mapping file id18033 NCBI fileEvidenceIEA
GeneNfkb2Authority18034Mapping file id18034 NCBI fileEvidenceIEA
GeneNfkbiaAuthority18035Mapping file id18035 NCBI fileEvidenceIEA
GeneNfkbibAuthority18036Mapping file id18036 NCBI fileEvidenceIEA
GeneNkiras1Authority69721Mapping file id69721 NCBI fileEvidenceIEA
GeneNkiras2Authority71966Mapping file id71966 NCBI fileEvidenceIEA
GeneNlrc5Authority434341Mapping file id434341 NCBI fileEvidenceIEA
GeneNlrx1Authority270151Mapping file id270151 NCBI fileEvidenceIEA
GeneNod1Authority107607Mapping file id107607 NCBI fileEvidenceIEA
GeneNod2Authority257632Mapping file idENSMUSG00000055994 Ensembl fileEvidenceIEA
GeneOptnAuthority71648Mapping file id71648 NCBI fileEvidenceIEA
GenePeli1Authority67245Mapping file id67245 NCBI fileEvidenceIEA
GenePeli2Authority93834Mapping file id93834 NCBI fileEvidenceIEA
GenePeli3Authority240518Mapping file id240518 NCBI fileEvidenceIEA
GenePlcg2Authority234779Mapping file id234779 NCBI fileEvidenceIEA
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GenePtpn4Authority19258Mapping file id19258 NCBI fileEvidenceIEA
GeneRelaAuthority19697Mapping file id19697 NCBI fileEvidenceIEA
GeneRipk1Authority19766Mapping file id19766 NCBI fileEvidenceIEA
GeneRipk2Authority192656Mapping file id192656 NCBI fileEvidenceIEA
GeneRipk3Authority56532Mapping file id56532 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRps6ka1Authority20111Mapping file id20111 NCBI fileEvidenceIEA
GeneRps6ka2Authority20112Mapping file id20112 NCBI fileEvidenceIEA
GeneRps6ka3Authority110651Mapping file id110651 NCBI fileEvidenceIEA
GeneRps6ka5Authority73086Mapping file id73086 NCBI fileEvidenceIEA
GeneS100bAuthority20203Mapping file id20203 NCBI fileEvidenceIEA
GeneSarm1Authority237868Mapping file id237868 NCBI fileEvidenceIEA
GeneSftpa1Authority20387Mapping file idENSMUSG00000021789 Ensembl fileEvidenceIEA
GeneSftpdAuthority20390Mapping file id20390 NCBI fileEvidenceIEA
GeneSkp1Authority21402Mapping file id21402 NCBI fileEvidenceIEA
GeneTab1Authority66513Mapping file id66513 NCBI fileEvidenceIEA
GeneTab2Authority68652Mapping file id68652 NCBI fileEvidenceIEA
GeneTab3Authority66724Mapping file id66724 NCBI fileEvidenceIEA
GeneTankAuthority21353Mapping file id21353 NCBI fileEvidenceIEA
GeneTbk1Authority56480Mapping file id56480 NCBI fileEvidenceIEA
GeneTicam1Authority106759Mapping file id106759 NCBI fileEvidenceIEA
GeneTicam2Authority225471Mapping file id225471 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, 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: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse 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 mouse 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.