Juniper Networks, Inc.
This organisation’s record, built from what each source attests and blank where none does.
TypeSemiconductor Equipment MakerHQUS
Reading the record…
This organisation’s record, built from what each source attests and blank where none does.
Reading the record…
Everything below is drawn from what the record carries for this organisation: its documented parents, the constraints that reach it, and the relationships and sites recorded against it. Each claim carries its source on the same line, and a blank means the record holds nothing.
Each hop carries its data source, source URL (where one exists), as-of date, and confidence label on the same line as the parent name. When two sources name different parents for the same hop, both render as alternates; the walker picks no winner.
Starting entity. The walker climbs from here through documented parent / subsidiary edges.
Chain-of-title terminates at HPE (HPE). No further parent is documented. For a public filer that means ultimate beneficial ownership is the dispersed float; for a state-linked entity, that the chain has reached the sovereign apex.
LP-to-fund commitments from sovereign or state-linked vehicles into funds whose portfolios include this entity. The per-fund commitment amounts and fund identities are drawn from a licensed fund/LP database held under subscription and not redistributed. The sovereign LP attribution and disclosure status are shown; the dollar figures and fund names are withheld. Even where disclosed, a fund commitment is spread across that fund’s whole portfolio, of which this entity is one position among many; presence here is not a claim of control. The methodology note explains why entity-attributable share is not imputed. Commitments dated 12+ years ago are framed in the past tense: closed-end private-market funds are typically structured on a ~10-year term plus extensions, and the source records the commitment event, not whether a position remains today.
| Sovereign limited partner | Commitments | Dated | Amount disclosed | Past typical fund term | Source status |
|---|---|---|---|---|---|
| GIC Private | 2 | 2 of 2 · 2001 | none | 2 | Current |
Every commitment is via a private-market fund; the fund identities and dollar amounts are held under license and never published, so “disclosed” reports that the source records an amount, while the amount itself stays withheld. A commitment past the typical closed-end fund term records the commitment event; it does not establish a current position. Source: Documented ownership record · vintage 2026-04-24 · tier 2
Dollar flows are annual figures from the fiscal year labelled on the row, drawn from SEC segment and >10%-customer disclosures, re-derived company disclosures, or a licensed supply-chain database; per-row source and authority tier on hover. A row without a year means the source does not state the period. Disclosures older than 5 years are tagged historical and ordered below current rows: they record what was disclosed then, and the counterparty may since have been acquired or dissolved. The 3-month Pearson r comes from a licensed supply-chain database; correlation is a coupling proxy for shared market sensitivity, and it is not a causal channel. Sole-source edges are flagged inline.
The records above join to the platform's analytical surfaces. Each link carries Juniper Networks, Inc.'s own numbers into the tool that acts on them.
6 upstream · 13 downstream. The interactive graph opens with Juniper Networks, Inc. selected, and the cascade simulator propagates seed disruptions across this same edge set, weighted by the curator's substitutability assessment.
Facilities, sovereign-AI programs, export-control posture, and the announced-versus-deployed reality gap for the country.
Licensed sources do reach Juniper Networks, Inc.: the supply relationships above are drawn from a licensed supply-chain database, and the sovereign-LP commitments from a licensed fund/LP database. What is missing is one specific feed: the corporate-financials extract behind this profile (geographic revenue, segment mix, capital allocation), which is built from listed-company disclosures; Juniper Networks, Inc. carries no listing or filer identifier, so there is no row for it to load. The public industry classification (SIC, NAICS) is absent as well. Coverage rules in the methodology.