asn.dev

Observed topology

AS15702 ONSTAGENET euNetworks GmbH

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15702: 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
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6220
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv628

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206876MeinSystem GmbHUnclassifiedIPv4228
AS44453interneX GmbHUnclassifiedIPv462
AS50876Kopernikus IT Systems GmbHUnclassifiedIPv462
AS211817Wirtschafts- und Sozialwissenschaftliches RechenzentrumUnclassifiedIPv437
AS209637vnet-services GmbHUnclassifiedIPv414
AS199994RUBICON IT GmbHUnclassifiedIPv46
AS207426GSS Media Services GmbHUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6630
AS206876MeinSystem GmbHUnclassifiedIPv4228
AS44453interneX GmbHUnclassifiedIPv462
AS50876Kopernikus IT Systems GmbHUnclassifiedIPv462
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv649
AS211817Wirtschafts- und Sozialwissenschaftliches RechenzentrumUnclassifiedIPv437
AS209637vnet-services GmbHUnclassifiedIPv414
AS199994RUBICON IT GmbHUnclassifiedIPv46
AS207426GSS Media Services GmbHUnclassifiedIPv46

Provenance

Where this comes from

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