asn.dev

Observed topology

AS42331 FREEHOST

Unclassified RIPE

Upstreams 7 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 7
Upstream graph Who carries AS42331, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS42331 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42331: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv6291
AS28917Fiord Networks, UABUnclassifiedIPv4188
AS174Cogent Communications, LLCTransitIPv4 IPv6170
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS1820WNET TELECOM USA Corp.ResidentialIPv4 IPv6126
AS24482SG.GSHostingIPv4 IPv616
AS3303Swisscom (Schweiz) AGResidentialIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47987Zemlyaniy Dmitro LeonidovichUnclassifiedIPv4 IPv6964

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS47987Zemlyaniy Dmitro LeonidovichUnclassifiedIPv4 IPv6964
AS9002RETN LimitedUnclassifiedIPv4 IPv6594
AS174Cogent Communications, LLCTransitIPv4 IPv6394
AS6939Hurricane Electric LLCTransitIPv4 IPv6350
AS28917Fiord Networks, UABUnclassifiedIPv4342
AS1820WNET TELECOM USA Corp.ResidentialIPv4 IPv6215
AS42159Zemlyaniy Dmitro LeonidovichHostingIPv464
AS24482SG.GSHostingIPv4 IPv638
AS3303Swisscom (Schweiz) AGResidentialIPv424
AS29632Netassist International EOODUnclassifiedIPv66

All 11 adjacent →

Provenance

Where this comes from

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