fresh
Juniper also benefited from the rise of data networking when Nortel couldn't build chips. observed
No person- or entity-level identity check is on record for this company. A name match is not one.
The inclusion bar: two or more independent sourced evidence families. This profile is reachable but not in the ranked index. It is a statement about how much evidence we hold, and about nothing else.
We have not established fit. That is not a soft no and not a soft yes — it is unknown, and it is never counted as a qualified prospect.
No standout signal or flag yet.
No single number decides. Layers can disagree — that's the point. New to this? →
Yeah. So, let's go build with double-digit millions, right? Which is not a huge amount in the context... of maybe a bigger upside than the 2500X Juniper had if you solve the fusion problem.
We invested in Juniper. It was a 2,500x return for us at Kleiner.
1996, since you brought up Juniper, the Internet was growing but not yet clear. The senior management of every major telco in the United States told me they would never adapt TCP IP for the Internet. And I said, fine, we'll build Juniper to build TCP IP. Cisco told me they would never do TCP IP above what is probably your home service today, OC12. Never. And so, we built TCP IP.
| Attribute | Value | Kind | Source | Observed | State | Conf. |
|---|---|---|---|---|---|---|
common_name | Juniper | observed | artifact ↗ | 2026-07-18 | normalized | 0.60 |
community.hn.max_points | 500 | observed | artifact ↗ | 2026-07-18 | superseded | 0.20 |
community.hn.max_points | 0 | observed | artifact ↗ | 2026-10-08 | normalized | 0.20 |
community.hn.mentions | 50 | observed | artifact ↗ | 2026-07-18 | superseded | 0.20 |
community.hn.mentions | 0 | observed | artifact ↗ | 2026-10-08 | normalized | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2026-07-18 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2026-08-16 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [{"url": "https://news.ycombinator.com/item?id=17576419", "title": "New Discovery Around Juniper Backdoor Raises More Questions (2016)", "points": 41, "created_at": "2018-07-20", "evidence_type": "rum | observed | artifact ↗ | 2025-01-30 | superseded | 0.20 |
community.hn.rumors | [] | observed | artifact ↗ | 2026-10-08 | normalized | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2026-07-18 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2026-08-16 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {"url": "https://news.ycombinator.com/item?id=28425354", "title": "Juniper breach mystery starts to clear with new details on hackers and U.S. role", "points": 500, "created_at": "2021-09-05"} | observed | artifact ↗ | 2021-09-05 | superseded | 0.20 |
community.hn.top_story | {} | observed | artifact ↗ | 2026-10-08 | normalized | 0.20 |
description | Juniper also benefited from the rise of data networking when Nortel couldn't build chips. | observed | artifact ↗ | 2026-07-18 | normalized | 0.60 |
index.ai_tie | AI_ADJACENT | observed | classify | 2026-07-25 | derived | 0.60 |
platform.index_excluded | true | derived | calc | 2026-09-28 | normalized | 0.99 |
sector | defense | derived | calc | 2026-08-08 | superseded | 0.90 |
sector | emerging | derived | calc | 2026-08-08 | normalized | 0.50 |
signal.commentary | {"context": null, "run_ref": "01KY8KDJZ4R8ARPACCBDCGX5Y3", "signals": [{"quote": "1996, since you brought up Juniper, the Internet was growing but not yet clear. The senior management of every major t | observed | artifact ↗ | 2023-09-26 | promoted | 0.50 |
signal.commentary | {"context": null, "run_ref": "01KY8KDJZ4R8ARPACCBDCGX5Y3", "signals": [{"quote": "We invested in Juniper. It was a 2,500x return for us at Kleiner.", "stance": "bullish", "signal_class": "fact_claim", | observed | artifact ↗ | 2023-09-26 | promoted | 0.50 |
signal.commentary | {"context": null, "run_ref": "01KY8KDJZ4R8ARPACCBDCGX5Y3", "signals": [{"quote": "Yeah. So, let's go build with double-digit millions, right? Which is not a huge amount in the context... of maybe a bi | observed | artifact ↗ | 2023-09-26 | promoted | 0.50 |
source.document.reference | {"kind": "video", "title": "All-In Summit: In conversation with Vinod Khosla — juniper", "source_id": "01KXRSFZTDXGVSS73CYGYDRC3C-m-17840323ea59b5e1", "extract_ref": "artifact:sha256:b9b87b398507df7c2 | observed | artifact ↗ | 2026-07-23 | normalized | 0.95 |