asn.dev

Observed topology

AS33940 WICHMANN-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33940: 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
AS9136Wobcom GmbHResidentialIPv4 IPv655
AS6939Hurricane Electric LLCTransitIPv4 IPv620
AS3320Deutsche Telekom AGMobileIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv62
AS6797GlobalConnect ABUnclassifiedIPv41
AS8218Zayo Infrastructure France SAUnclassifiedIPv61
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9136Wobcom GmbHResidentialIPv4 IPv655
AS6939Hurricane Electric LLCTransitIPv4 IPv620
AS3320Deutsche Telekom AGMobileIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv62
AS6797GlobalConnect ABUnclassifiedIPv41
AS8218Zayo Infrastructure France SAUnclassifiedIPv61
AS9002RETN LimitedUnclassifiedIPv61

Provenance

Where this comes from

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