asn.dev

Observed topology

AS22672 PDKPL-AS-AP - Kinetix Networks

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22672: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv679
AS38195SuperloopUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv62
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv62
AS64073Vetta GroupUnclassifiedIPv4 IPv62
AS38001NewMedia Express Pte LtdHostingIPv41
AS61292Blix Group ASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134143Kinetix NetworksResidentialIPv4 IPv61,626
AS138637VOCPHONE PTY LTDHostingIPv4387
AS142588Sharon AIUnclassifiedIPv4290

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv62,330
AS134143Kinetix NetworksResidentialIPv4 IPv62,169
AS138637VOCPHONE PTY LTDHostingIPv4387
AS38195SuperloopUnclassifiedIPv4 IPv6294
AS142588Sharon AIUnclassifiedIPv4290
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv678
AS38001NewMedia Express Pte LtdHostingIPv476
AS17639Converge ICT Solutions Inc.UnclassifiedIPv450
AS61292Blix Group ASUnclassifiedIPv616

All 12 adjacent →

Provenance

Where this comes from

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