asn.dev

Observed topology

AS44974 REGIONETSW-AS

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS44974: 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
AS28876suec // dacor GmbHResidentialIPv4 IPv6133
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS3209Vodafone GmbHResidentialIPv4 IPv677
AS8823Rockenstein AGUnclassifiedIPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv68
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS29632Netassist International EOODUnclassifiedIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203986schnell-im-netz.de GmbH & Co.KGUnclassifiedIPv4 IPv668

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS28876suec // dacor GmbHResidentialIPv4 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS3209Vodafone GmbHResidentialIPv4 IPv677
AS203986schnell-im-netz.de GmbH & Co.KGUnclassifiedIPv4 IPv668
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS8823Rockenstein AGUnclassifiedIPv626
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612
AS20485Joint Stock Company TransTeleComUnclassifiedIPv48
AS24482SG.GSHostingIPv4 IPv68

Provenance

Where this comes from

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