asn.dev

Observed topology

AS23756 PADINET-AS-ID - PADINET - Padi Internet

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23756: 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,070
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6997
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6578
AS7713PT Telekomunikasi IndonesiaResidentialIPv4265
AS24482SG.GSHostingIPv4 IPv648

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58497PT Integra VenturaUnclassifiedIPv4128
AS153962PT Wismilak Inti Makmur TBKUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv61,125
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv61,070
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6578
AS7713PT Telekomunikasi IndonesiaResidentialIPv4265
AS58497PT Integra VenturaUnclassifiedIPv4128
AS24482SG.GSHostingIPv4 IPv650
AS153962PT Wismilak Inti Makmur TBKUnclassifiedIPv44

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.