asn.dev

Observed topology

AS45265 CSLOX-DOM-AS-AP CSLOXINFO Transit AS with Domestic National Internet Exchange

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45265: 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
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS4750CS LOXINFO PUBLIC COMPANY LIMITEDUnclassifiedIPv4 IPv6513
AS9891CS LOXINFO Public Company Limited.HostingIPv4 IPv6114
AS45758Triple T Broadband Public Company LimitedResidentialIPv414
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv68
AS58930My Telecom Group Company LimitedUnclassifiedIPv42
AS139341ACEHostingIPv4 IPv62
AS45581INFONET THAILAND ISPUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS24482SG.GSHostingIPv4 IPv6748
AS4750CS LOXINFO PUBLIC COMPANY LIMITEDUnclassifiedIPv4 IPv6585
AS9891CS LOXINFO Public Company Limited.HostingIPv4 IPv6134
AS45758Triple T Broadband Public Company LimitedResidentialIPv414
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv68
AS63529Bangkok Neutral Internet Exchange Route ServersUnclassifiedIPv67
AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXUnclassifiedIPv65
AS135511CS Loxinfo Public Company LimitedUnclassifiedIPv63
AS58930My Telecom Group Company LimitedUnclassifiedIPv42
AS139341ACEHostingIPv4 IPv62

All 11 adjacent →

Provenance

Where this comes from

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