Observed topology

AS209109 DataSphere-Limited DataSphere (H.K) Limited

Residential RIPE

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209109: 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
AS17433	Hytron Network Services Limited	Residential	IPv4 IPv6	393
AS955	LSHIY LLC	Unclassified	IPv4 IPv6	328
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	21

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS6642	Hyper Group Network LLC	Unclassified	IPv4	34
AS401889	Infinitron Internet LLC	Hosting	IPv6	31

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS955	LSHIY LLC	Unclassified	IPv4 IPv6	607
AS17433	Hytron Network Services Limited	Residential	IPv4 IPv6	432
AS14447	Infinitron Internet LLC	Hosting	IPv4 IPv6	254
AS6642	Hyper Group Network LLC	Unclassified	IPv4	34
AS401889	Infinitron Internet LLC	Hosting	IPv6	31
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	22

Provenance

Where this comes from

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