asn.dev

Observed topology

AS38896 CERGIS-AS-AP PT. Centra Global Investama

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38896: 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
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv61,165
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6154
AS4787PT Cyberindo AditamaResidentialIPv4130
AS24482SG.GSHostingIPv436
AS35280F5 Networks SARLHostingIPv432
AS45725Kings Network Indonesia, PTResidentialIPv410

Transit

Downstream networks

inferred

Networks for which AS38896 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 AS38896 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv61,165
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6154
AS4787PT Cyberindo AditamaResidentialIPv4130
AS24482SG.GSHostingIPv436
AS35280F5 Networks SARLHostingIPv432
AS45725Kings Network Indonesia, PTResidentialIPv410

Provenance

Where this comes from

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