Observed topology

AS14447 Infinitron Internet LLC

Hosting ARIN

Upstreams 0 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS212085	Alexander Bruegmann	Unclassified	IPv6	68
AS208223	SHU-HAO TUNG	Unclassified	IPv4 IPv6	64
AS209710	SNRD NETWORKS LIMITED	Hosting	IPv4 IPv6	35
AS213729	Rikki Network Limited	Unclassified	IPv6	35
AS402810	TDDT,	Unclassified	IPv4	19
AS197291	Ken Marfilla	Unclassified	IPv6	15
AS152848	asdf.hk	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS209109	DataSphere (H.K) Limited	Residential	IPv4 IPv6	241
AS212085	Alexander Bruegmann	Unclassified	IPv6	68
AS208223	SHU-HAO TUNG	Unclassified	IPv4 IPv6	64
AS209710	SNRD NETWORKS LIMITED	Hosting	IPv4 IPv6	35
AS213729	Rikki Network Limited	Unclassified	IPv6	35
AS402810	TDDT,	Unclassified	IPv4	19
AS197291	Ken Marfilla	Unclassified	IPv6	15
AS152848	asdf.hk	Unclassified	IPv4	5

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.