asn.dev

Observed topology

AS22442 HOU-PHONOSCOPE

Unclassified ARIN

Upstreams 2 carry this network
Downstreams 8 this network carries
Adjacent (IPv4) 11
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.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,751
AS6939Hurricane Electric LLCTransitIPv4172

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19927Lone Star College System DistrictUnclassifiedIPv4236
AS394936-Reserved AS-UnclassifiedIPv468
AS63153Stewart & Stevenson LLCUnclassifiedIPv439
AS393383Spring Independent School DistrictUnclassifiedIPv433
AS400782Harris County Public LibraryUnclassifiedIPv427
AS394309HBU.eduUnclassifiedIPv416
AS55291Harris CountyUnclassifiedIPv411
AS46094Lee CollegeUnclassifiedIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv63,131
AS19927Lone Star College System DistrictUnclassifiedIPv4236
AS6939Hurricane Electric LLCTransitIPv4203
AS394936-Reserved AS-UnclassifiedIPv468
AS63153Stewart & Stevenson LLCUnclassifiedIPv439
AS393383Spring Independent School DistrictUnclassifiedIPv433
AS400782Harris County Public LibraryUnclassifiedIPv427
AS6300FidiumResidentialIPv424
AS394309HBU.eduUnclassifiedIPv416
AS55291Harris CountyUnclassifiedIPv411

Provenance

Where this comes from

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