asn.dev

Observed topology

AS140384 BITNIAGA-AS-ID PT BITNIAGA CIPTA GEMILANG

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140384: 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
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6218
AS147168PT NTT IndonesiaUnclassifiedIPv49
AS24482SG.GSHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151572PT Evolution Karya Lintas DataResidentialIPv4195
AS153059PT Akses Datatrans IndonesiaResidentialIPv4195
AS153092PT Redi Revolusi Digital SolusiUnclassifiedIPv433
AS149911PT Blitar Sarana DataUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6584
AS151572PT Evolution Karya Lintas DataResidentialIPv4195
AS153059PT Akses Datatrans IndonesiaResidentialIPv4195
AS147168PT NTT IndonesiaUnclassifiedIPv456
AS153092PT Redi Revolusi Digital SolusiUnclassifiedIPv433
AS24482SG.GSHostingIPv4 IPv614
AS35280F5 Networks SARLHostingIPv41
AS149911PT Blitar Sarana DataUnclassifiedIPv41

Provenance

Where this comes from

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