asn.dev

Observed topology

AS38777 PT. NTT Indonesia

Unclassified ARIN

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS147168PT NTT IndonesiaUnclassifiedIPv4 IPv6154
AS152806PT Sinar Technology JayaUnclassifiedIPv4 IPv667
AS141890PT Condifa Digitech SolusindoUnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS10217PT. NTT IndonesiaUnclassifiedIPv4 IPv6321
AS147168PT NTT IndonesiaUnclassifiedIPv4 IPv6246
AS152806PT Sinar Technology JayaUnclassifiedIPv4 IPv667
AS141890PT Condifa Digitech SolusindoUnclassifiedIPv48

Provenance

Where this comes from

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