asn.dev

Observed topology

AS149710 IDNIC-ALCEN-ID PT GEMILANG CATUR PERSADA

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS149710: 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
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4 IPv698
AS58495PT Parsaoran Global DatatransUnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138823PT. Trimitra Usaha SejahteraResidentialIPv4 IPv6208
AS149898PT Retbizz Exabit IndonesiaUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4 IPv6308
AS138823PT. Trimitra Usaha SejahteraResidentialIPv4 IPv6210
AS58495PT Parsaoran Global DatatransUnclassifiedIPv4 IPv615
AS149898PT Retbizz Exabit IndonesiaUnclassifiedIPv412
AS24482SG.GSHostingIPv41

Provenance

Where this comes from

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