asn.dev

Observed topology

AS197301 PARKNET-AS

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS197301: 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 IPv679
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS42708Glesys ABUnclassifiedIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS50304Blix Solutions ASUnclassifiedIPv4 IPv63
AS204092Association GRIFONUnclassifiedIPv4 IPv63

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202361Ask SelmerHostingIPv4 IPv691

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6134
AS202361Ask SelmerHostingIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv4 IPv650
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS42708Glesys ABUnclassifiedIPv4 IPv65
AS50304Blix Solutions ASUnclassifiedIPv4 IPv65
AS33891Core-Backbone GmbHHostingIPv44
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63
AS12552GlobalConnect ABUnclassifiedIPv43

All 22 adjacent →

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.