Observed topology

AS135419 CABLECONNECT1-AS-AP - Cableconnect Co.,Ltd

Hosting APNIC Network Services

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS135419, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS135419 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135419: 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.

AS	Network	Type	Families	Paths seen
AS45629	JasTel Network International Gateway	Residential	IPv4 IPv6	259
AS9304	HGC Global Communications Limited	Hosting	IPv4	179
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	22
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS10089	Total Access Communication PLC.	Unclassified	IPv4 IPv6	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS138204	Sophon Broadband Networks co.,ltd	Unclassified	IPv4	128

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS45629	JasTel Network International Gateway	Residential	IPv4 IPv6	363
AS9304	HGC Global Communications Limited	Hosting	IPv4	199
AS138204	Sophon Broadband Networks co.,ltd	Unclassified	IPv4	128
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	22
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS10089	Total Access Communication PLC.	Unclassified	IPv4 IPv6	6

Provenance

Where this comes from

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