asn.dev

Observed topology

AS31662 KNSURSELVA Kommunikations Netz Surselva

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31662: 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 ABTransitIPv4330
AS6939Hurricane Electric LLCTransitIPv4 IPv6226
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6209
AS24482SG.GSHostingIPv4 IPv615
AS33891Core-Backbone GmbHHostingIPv411
AS34019Hivane AssociationUnclassifiedIPv411
AS48362Stadtwerke FeldkirchResidentialIPv411
AS9002RETN LimitedUnclassifiedIPv64
AS25091IP-Max SAUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31052Exigo AGHostingIPv498
AS49446Somedia Production AGUnclassifiedIPv47

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4378
AS6939Hurricane Electric LLCTransitIPv4 IPv6244
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6241
AS31052Exigo AGHostingIPv498
AS24482SG.GSHostingIPv4 IPv617
AS33891Core-Backbone GmbHHostingIPv413
AS34019Hivane AssociationUnclassifiedIPv413
AS48362Stadtwerke FeldkirchResidentialIPv411
AS49446Somedia Production AGUnclassifiedIPv47
AS9002RETN LimitedUnclassifiedIPv64

All 12 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.