asn.dev

Observed topology

AS212567 FNMUC Freie Netze Muenchen e.V.

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS212567: 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
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv6152
AS5405Inter.link GmbHUnclassifiedIPv4 IPv634
AS24961WIIT AGHostingIPv4 IPv632
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS50629LWLcom GmbHUnclassifiedIPv4 IPv628
AS3320Deutsche Telekom AGMobileIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv63
AS6797GlobalConnect ABUnclassifiedIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205791SONNABEND GmbHUnclassifiedIPv633
AS201173Chaotikum e.V.UnclassifiedIPv62

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv6185
AS5405Inter.link GmbHUnclassifiedIPv4 IPv634
AS205791SONNABEND GmbHUnclassifiedIPv633
AS24961WIIT AGHostingIPv4 IPv632
AS50629LWLcom GmbHUnclassifiedIPv4 IPv630
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS3320Deutsche Telekom AGMobileIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv63
AS6797GlobalConnect ABUnclassifiedIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv42

Provenance

Where this comes from

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