asn.dev

Observed topology

AS12348 AS12348 Hermann-Glockner-Str. 7

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12348: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6195
AS3356Level 3 Parent, LLCTransitIPv4 IPv6174
AS29014ScaleUp Technologies GmbH & Co. KGHostingIPv4 IPv680
AS13237euNetworks GmbHUnclassifiedIPv4 IPv679

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24836Klaus Kasimirek trading as Kasimirek IT ConsultingUnclassifiedIPv4 IPv695
AS49735ITSMedia GmbHUnclassifiedIPv436
AS12655Sellwerk Verwaltungs GmbHUnclassifiedIPv426

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6269
AS3356Level 3 Parent, LLCTransitIPv4 IPv6231
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6103
AS24836Klaus Kasimirek trading as Kasimirek IT ConsultingUnclassifiedIPv4 IPv695
AS29014ScaleUp Technologies GmbH & Co. KGHostingIPv4 IPv682
AS49735ITSMedia GmbHUnclassifiedIPv436
AS12655Sellwerk Verwaltungs GmbHUnclassifiedIPv426

Provenance

Where this comes from

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