Observed topology

AS22442 HOU-PHONOSCOPE - Phonoscope, Inc.

Unclassified ARIN NSP

Upstreams 1 carry this network

Downstreams 8 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22442: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	2,971

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS19927	Lone Star College System District	Unclassified	IPv4	237
AS394936	-Reserved AS-	Unclassified	IPv4	70
AS400782	Harris County Public Library	Unclassified	IPv4	42
AS394309	HBU.edu	Unclassified	IPv4	39
AS63153	Stewart & Stevenson LLC	Unclassified	IPv4	38
AS393383	Spring Independent School District	Unclassified	IPv4	35
AS55291	Harris County	Unclassified	IPv4	32
AS46094	Lee College	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	3,469
AS19927	Lone Star College System District	Unclassified	IPv4	237
AS394936	-Reserved AS-	Unclassified	IPv4	70
AS400782	Harris County Public Library	Unclassified	IPv4	42
AS394309	HBU.edu	Unclassified	IPv4	39
AS63153	Stewart & Stevenson LLC	Unclassified	IPv4	38
AS393383	Spring Independent School District	Unclassified	IPv4	35
AS55291	Harris County	Unclassified	IPv4	32
AS46094	Lee College	Unclassified	IPv4	5

Provenance

Where this comes from

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