asn.dev

Observed topology

AS29686 PROBENETWORKS-AS Jonas Frey trading as Probe Networks

Hosting RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS29686: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6212
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6189
AS2914NTT America, Inc.TransitIPv4 IPv6149
AS3320Deutsche Telekom AGMobileIPv4 IPv681
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv612
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv612
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612
AS1836green.ch AGResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206293proIO GmbHUnclassifiedIPv4472
AS214197virtion GmbHUnclassifiedIPv4 IPv6170
AS211600SECUPAY AGUnclassifiedIPv466

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS206293proIO GmbHUnclassifiedIPv4472
AS6939Hurricane Electric LLCTransitIPv4 IPv6370
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6365
AS2914NTT America, Inc.TransitIPv4 IPv6319
AS214197virtion GmbHUnclassifiedIPv4 IPv6170
AS3320Deutsche Telekom AGMobileIPv4 IPv6104
AS211600SECUPAY AGUnclassifiedIPv466
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv660
AS24482SG.GSHostingIPv4 IPv624
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv624

Provenance

Where this comes from

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