asn.dev

Observed topology

AS201983 ANSLUTEN-AS Ansluten Hosting i Sverige AB

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201983: 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
AS8473Bahnhof ABResidentialIPv4 IPv61,480
AS34244Teleservice Bredband Skane ABUnclassifiedIPv4 IPv6466
AS6939Hurricane Electric LLCTransitIPv4 IPv6356
AS35706Net at Once Sweden ABUnclassifiedIPv4 IPv6133
AS24482SG.GSHostingIPv4 IPv641
AS20473The Constant Company, LLCHostingIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8949Johan HedbergUnclassifiedIPv671

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8473Bahnhof ABResidentialIPv4 IPv61,543
AS34244Teleservice Bredband Skane ABUnclassifiedIPv4 IPv6466
AS6939Hurricane Electric LLCTransitIPv4 IPv6356
AS35706Net at Once Sweden ABUnclassifiedIPv4 IPv6137
AS8949Johan HedbergUnclassifiedIPv671
AS24482SG.GSHostingIPv4 IPv643
AS20473The Constant Company, LLCHostingIPv65

Provenance

Where this comes from

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