asn.dev

Observed topology

AS45499 CABLELINK-TRANSIT-AS-AP Cablelink & Holdings Corp. Transit AS Internet Service Provider Philippines

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45499: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,847
AS135607Infinivan IncorporatedResidentialIPv4 IPv6445
AS24482SG.GSHostingIPv4 IPv641
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv434
AS38001NewMedia Express Pte LtdHostingIPv4 IPv627

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138689CONCEPCION PAY-TV NETWORK, INC.UnclassifiedIPv4297
AS137406Airlive Communications Inc.UnclassifiedIPv464
AS136513FILINVEST BUSINESS SERVICES CORPORATIONUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,226
AS135607Infinivan IncorporatedResidentialIPv4 IPv6445
AS138689CONCEPCION PAY-TV NETWORK, INC.UnclassifiedIPv4297
AS137406Airlive Communications Inc.UnclassifiedIPv464
AS24482SG.GSHostingIPv4 IPv648
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv434
AS38001NewMedia Express Pte LtdHostingIPv4 IPv634
AS136513FILINVEST BUSINESS SERVICES CORPORATIONUnclassifiedIPv432

Provenance

Where this comes from

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