asn.dev

Observed topology

AS39892 XPOUNDIT Frank Scholl trading as xpoundit GmbH & Co. KG

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39892: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6263
AS174Cogent Communications, LLCTransitIPv4 IPv6110
AS2914NTT America, Inc.TransitIPv4 IPv6109
AS3320Deutsche Telekom AGMobileIPv4 IPv624
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200797UBN24 GmbHUnclassifiedIPv4 IPv6259

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6552
AS200797UBN24 GmbHUnclassifiedIPv4 IPv6516
AS2914NTT America, Inc.TransitIPv4 IPv6239
AS174Cogent Communications, LLCTransitIPv4 IPv6172
AS3320Deutsche Telekom AGMobileIPv4 IPv659
AS37721Virtual Technologies & SolutionsResidentialIPv61

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.