Skip to content

Create an account and get up to 25% off.

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.

Cytokine Signaling in Immune system

R-MMU-1280215 in Reactome release 97: under Immune System, with 475 genes placed in it by the mapping files and 7 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-1280215 (human), R-RNO-1280215 (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 475 genes in this mouse pathway; showing 301 to 400, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 4 of 5
GenePlcg1Authority18803Mapping file id18803 NCBI fileEvidenceIEA
GenePpm1bAuthority19043Mapping file id19043 NCBI fileEvidenceIEA
GenePpp2caAuthority19052Mapping file id19052 NCBI fileEvidenceIEA
GenePpp2cbAuthority19053Mapping file id19053 NCBI fileEvidenceIEA
GenePpp2r1aAuthority51792Mapping file id51792 NCBI fileEvidenceIEA
GenePpp2r1bAuthority73699Mapping file id73699 NCBI fileEvidenceIEA
GenePpp2r5aAuthority226849Mapping file id226849 NCBI fileEvidenceIEA
GenePpp2r5dAuthority21770Mapping file id21770 NCBI fileEvidenceIEA
GenePrkacaAuthority18747Mapping file id18747 NCBI fileEvidenceIEA
GenePrkcdAuthority18753Mapping file id18753 NCBI fileEvidenceIEA
GenePrkraAuthority23992Mapping file id23992 NCBI fileEvidenceIEA
GenePrlAuthority19109Mapping file idENSMUSG00000021342 Ensembl fileEvidenceIEA
GenePrlrAuthority19116Mapping file id19116 NCBI fileEvidenceIEA
GenePsma1Authority26440Mapping file id26440 NCBI fileEvidenceIEA
GenePsma2Authority19166Mapping file id19166 NCBI fileEvidenceIEA
GenePsma3Authority19167Mapping file id19167 NCBI fileEvidenceIEA
GenePsma4Authority26441Mapping file id26441 NCBI fileEvidenceIEA
GenePsma5Authority26442Mapping file id26442 NCBI fileEvidenceIEA
GenePsma6Authority26443Mapping file id26443 NCBI fileEvidenceIEA
GenePsma7Authority26444Mapping file id26444 NCBI fileEvidenceIEA
GenePsmb1Authority19170Mapping file id19170 NCBI fileEvidenceIEA
GenePsmb2Authority26445Mapping file id26445 NCBI fileEvidenceIEA
GenePsmb3Authority26446Mapping file id26446 NCBI fileEvidenceIEA
GenePsmb4Authority19172Mapping file id19172 NCBI fileEvidenceIEA
GenePsmb5Authority19173Mapping file id19173 NCBI fileEvidenceIEA
GenePsmb6Authority19175Mapping file id19175 NCBI fileEvidenceIEA
GenePsmb7Authority19177Mapping file id19177 NCBI fileEvidenceIEA
GenePsmc1Authority19179Mapping file id19179 NCBI fileEvidenceIEA
GenePsmc2Authority19181Mapping file id19181 NCBI fileEvidenceIEA
GenePsmc3Authority19182Mapping file id19182 NCBI fileEvidenceIEA
GenePsmc4Authority23996Mapping file id23996 NCBI fileEvidenceIEA
GenePsmc5Authority19184Mapping file id19184 NCBI fileEvidenceIEA
GenePsmc6Authority67089Mapping file id67089 NCBI fileEvidenceIEA
GenePsmd1Authority70247Mapping file id70247 NCBI fileEvidenceIEA
GenePsmd11Authority69077Mapping file id69077 NCBI fileEvidenceIEA
GenePsmd12Authority66997Mapping file id66997 NCBI fileEvidenceIEA
GenePsmd13Authority23997Mapping file id23997 NCBI fileEvidenceIEA
GenePsmd14Authority59029Mapping file id59029 NCBI fileEvidenceIEA
GenePsmd2Authority21762Mapping file id21762 NCBI fileEvidenceIEA
GenePsmd3Authority22123Mapping file id22123 NCBI fileEvidenceIEA
GenePsmd6Authority66413Mapping file id66413 NCBI fileEvidenceIEA
GenePsmd7Authority17463Mapping file id17463 NCBI fileEvidenceIEA
GenePsmd8Authority57296Mapping file id57296 NCBI fileEvidenceIEA
GenePtk2bAuthority19229Mapping file id19229 NCBI fileEvidenceIEA
GenePtpn1Authority19246Mapping file id19246 NCBI fileEvidenceIEA
GenePtpn11Authority19247Mapping file id19247 NCBI fileEvidenceIEA
GenePtpn2Authority19255Mapping file id19255 NCBI fileEvidenceIEA
GenePtpn6Authority15170Mapping file id15170 NCBI fileEvidenceIEA
GenePtprjAuthority19271Mapping file id19271 NCBI fileEvidenceIEA
GenePtprz1Authority19283Mapping file id19283 NCBI fileEvidenceIEA
GeneRaf1Authority110157Mapping file id110157 NCBI fileEvidenceIEA
GeneRapgef1Authority107746Mapping file id107746 NCBI fileEvidenceIEA
GeneRbx1Authority56438Mapping file id56438 NCBI fileEvidenceIEA
GeneRelaAuthority19697Mapping file id19697 NCBI fileEvidenceIEA
GeneRelbAuthority19698Mapping file id19698 NCBI fileEvidenceIEA
GeneRigiAuthority230073Mapping file id230073 NCBI fileEvidenceIEA
GeneRipk2Authority192656Mapping file id192656 NCBI fileEvidenceIEA
GeneRnaselAuthority24014Mapping file id24014 NCBI fileEvidenceIEA
GeneRnf7Authority19823Mapping file id19823 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
GeneSdc1Authority20969Mapping file id20969 NCBI fileEvidenceIEA
GeneSh2b1Authority20399Mapping file id20399 NCBI fileEvidenceIEA
GeneSh2b3Authority16923Mapping file id16923 NCBI fileEvidenceIEA
GeneShc1Authority20416Mapping file id20416 NCBI fileEvidenceIEA
GeneSkp1Authority21402Mapping file id21402 NCBI fileEvidenceIEA
GeneSlaAuthority20491Mapping file id20491 NCBI fileEvidenceIEA
GeneSla2Authority77799Mapping file id77799 NCBI fileEvidenceIEA
GeneSmarca4Authority20586Mapping file id20586 NCBI fileEvidenceIEA
GeneSnap25Authority20614Mapping file id20614 NCBI fileEvidenceIEA
GeneSncaAuthority20617Mapping file id20617 NCBI fileEvidenceIEA
GeneSocs1Authority12703Mapping file id12703 NCBI fileEvidenceIEA
GeneSocs2Authority216233Mapping file id216233 NCBI fileEvidenceIEA
GeneSocs3Authority12702Mapping file id12702 NCBI fileEvidenceIEA
GeneSocs5Authority56468Mapping file id56468 NCBI fileEvidenceIEA
GeneSocs6Authority54607Mapping file id54607 NCBI fileEvidenceIEA
GeneSos1Authority20662Mapping file id20662 NCBI fileEvidenceIEA
GeneSos2Authority20663Mapping file id20663 NCBI fileEvidenceIEA
GeneSphk1Authority20698Mapping file id20698 NCBI fileEvidenceIEA
GeneSqstm1Authority18412Mapping file id18412 NCBI fileEvidenceIEA
GeneStat2Authority20847Mapping file idENSMUSG00000040033 Ensembl fileEvidenceIEA
GeneStat3Authority20848Mapping file id20848 NCBI fileEvidenceIEA
GeneStat4Authority20849Mapping file id20849 NCBI fileEvidenceIEA
GeneStat5aAuthority20850Mapping file id20850 NCBI fileEvidenceIEA
GeneStat5bAuthority20851Mapping file id20851 NCBI fileEvidenceIEA
GeneStat6Authority20852Mapping file id20852 NCBI fileEvidenceIEA
GeneStx1aAuthority20907Mapping file id20907 NCBI fileEvidenceIEA
GeneStx3Authority20908Mapping file id20908 NCBI fileEvidenceIEA
GeneStx4aAuthority20909Mapping file id20909 NCBI fileEvidenceIEA
GeneStxbp2Authority20911Mapping file id20911 NCBI fileEvidenceIEA
GeneSumo1Authority22218Mapping file id22218 NCBI fileEvidenceIEA
GeneSykAuthority20963Mapping file id20963 NCBI fileEvidenceIEA
GeneTab1Authority66513Mapping file id66513 NCBI fileEvidenceIEA
GeneTab2Authority68652Mapping file id68652 NCBI fileEvidenceIEA
GeneTab3Authority66724Mapping file id66724 NCBI fileEvidenceIEA
GeneTarbp2Authority21357Mapping file id21357 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.