asn.dev

Observed topology

AS31950 AS-DANS - Data Network Solutions

Unclassified ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS31950: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6118
AS6461Zayo BandwidthTransitIPv460
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS22652Videotron LteeResidentialIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS293ESnetUnclassifiedIPv44
AS32097WholeSale Internet, Inc.HostingIPv44
AS9002RETN LimitedUnclassifiedIPv63
AS34549meerfarbig GmbH & Co. KGHostingIPv62

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26031Monmouth CountyUnclassifiedIPv440

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6143
AS6939Hurricane Electric LLCTransitIPv4 IPv662
AS6461Zayo BandwidthTransitIPv460
AS26031Monmouth CountyUnclassifiedIPv440
AS22652Videotron LteeResidentialIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS32097WholeSale Internet, Inc.HostingIPv45
AS293ESnetUnclassifiedIPv44
AS9002RETN LimitedUnclassifiedIPv63

All 13 adjacent →

Provenance

Where this comes from

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