asn.dev

Observed topology

AS141955 IDNIC-TIMORLINTAS-AS-ID - PT Timor Lintas Nusantara

Unclassified RIPE

Upstreams 6 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 0
Upstream graph Who carries AS141955, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS141955 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141955: 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.

ASNetworkTypeFamiliesPaths seen
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4105
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv434
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv419
AS24482SG.GSHostingIPv44
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv42
AS35280F5 Networks SARLHostingIPv41

Transit

Downstream networks

inferred

Networks for which AS141955 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS141955 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4105
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv434
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv419
AS24482SG.GSHostingIPv44
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv42
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.