asn.dev

Observed topology

AS31148 FREENET_LLC

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31148: 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
AS21497PrJSC "VF UKRAINE"MobileIPv414,698
AS6939Hurricane Electric LLCTransitIPv4 IPv62,166
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6305
AS24482SG.GSHostingIPv4292
AS29632Netassist International EOODUnclassifiedIPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20971INFOTECH LtdUnclassifiedIPv4214
AS25174Osokorky Online LLCUnclassifiedIPv482
AS42512X-COM LLCUnclassifiedIPv418

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS21497PrJSC "VF UKRAINE"MobileIPv414,967
AS6939Hurricane Electric LLCTransitIPv4 IPv62,194
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6315
AS24482SG.GSHostingIPv4299
AS20971INFOTECH LtdUnclassifiedIPv4214
AS25174Osokorky Online LLCUnclassifiedIPv482
AS42512X-COM LLCUnclassifiedIPv418
AS29632Netassist International EOODUnclassifiedIPv612

Provenance

Where this comes from

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