asn.dev

Observed topology

AS42605 FRA-VRNETZE

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS42605: 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
AS2914NTT America, Inc.TransitIPv4 IPv6175
AS6939Hurricane Electric LLCTransitIPv4 IPv656
AS3320Deutsche Telekom AGMobileIPv4 IPv622
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv619
AS33891Core-Backbone GmbHHostingIPv410
AS1836green.ch AGResidentialIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS34019Hivane AssociationUnclassifiedIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS42708Glesys ABUnclassifiedIPv4 IPv67

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206149R+V Allgemeine Versicherung AktiengesellschaftUnclassifiedIPv478

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6203
AS206149R+V Allgemeine Versicherung AktiengesellschaftUnclassifiedIPv478
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS3320Deutsche Telekom AGMobileIPv4 IPv630
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS33891Core-Backbone GmbHHostingIPv410
AS24482SG.GSHostingIPv4 IPv69
AS34019Hivane AssociationUnclassifiedIPv4 IPv69
AS42708Glesys ABUnclassifiedIPv4 IPv69
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv69

All 22 adjacent →

Provenance

Where this comes from

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