asn.dev

Observed topology

AS45754 CLEARPATH-AS-AP - Clear Path Networks Inc

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45754: 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
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv41,335
AS4775Globe TelecomsUnclassifiedIPv4 IPv6504
AS135607Infinivan IncorporatedResidentialIPv4 IPv6283
AS17639Converge ICT Solutions Inc.UnclassifiedIPv428
AS24482SG.GSHostingIPv428

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14789Cloudflare, Inc.UnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv41,381
AS4775Globe TelecomsUnclassifiedIPv4 IPv6522
AS135607Infinivan IncorporatedResidentialIPv4 IPv6283
AS14789Cloudflare, Inc.UnclassifiedIPv464
AS17639Converge ICT Solutions Inc.UnclassifiedIPv428
AS24482SG.GSHostingIPv428

Provenance

Where this comes from

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