Observed topology
AS150942 IDNIC-LAMBDA-AS-ID - LAMBDA
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS150942: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
Transit
Downstream networks
Networks for which AS150942 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS155049 | PT Jati Buana Sentosa | Unclassified | IPv4 | 195 |
| AS153071 | PT Cloudlink Ardtech Indonesia | Unclassified | IPv4 | 134 |
| AS152798 | PT Aufa Berkah Media | Unclassified | IPv4 | 130 |
| AS150247 | PT Pandawa Lima Java Network | Unclassified | IPv4 | 44 |
| AS149720 | PT Adi Solusindo Teknologi | Unclassified | IPv4 | 29 |
| AS141903 | PT Natha Buana Indonesia | Residential | IPv4 | 4 |
| AS147145 | PT Jalur Satu Aman | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS150942 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS133840 | PT Jala Lintas Media | Unclassified | IPv4 | 564 |
| AS155049 | PT Jati Buana Sentosa | Unclassified | IPv4 | 195 |
| AS55685 | PT Jala Lintas Media | Unclassified | IPv4 | 154 |
| AS153071 | PT Cloudlink Ardtech Indonesia | Unclassified | IPv4 | 134 |
| AS152798 | PT Aufa Berkah Media | Unclassified | IPv4 | 130 |
| AS150247 | PT Pandawa Lima Java Network | Unclassified | IPv4 | 44 |
| AS149720 | PT Adi Solusindo Teknologi | Unclassified | IPv4 | 29 |
| AS150279 | PT Lintas Network Solusi | Unclassified | IPv4 | 18 |
| AS141903 | PT Natha Buana Indonesia | Residential | IPv4 | 4 |
| AS147145 | PT Jalur Satu Aman | Unclassified | IPv4 | 4 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.