asn.dev

Observed topology

AS12931 IDKOM IDKOM Networks GmbH

Hosting RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS12931: 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
AS8767M-net Telekommunikations GmbHResidentialIPv4 IPv671
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv63
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS213241TECHIT.BE SRLResidentialIPv4 IPv63
AS1836green.ch AGResidentialIPv42
AS6797GlobalConnect ABUnclassifiedIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv42

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS21173LANtana GmbHUnclassifiedIPv470

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS8767M-net Telekommunikations GmbHResidentialIPv4 IPv6101
AS21173LANtana GmbHUnclassifiedIPv470
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS3320Deutsche Telekom AGMobileIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS212024Marc SchmittUnclassifiedIPv4 IPv65
AS213241TECHIT.BE SRLResidentialIPv4 IPv65
AS1836green.ch AGResidentialIPv44
AS8551Bezeq International Ltd.UnclassifiedIPv44

All 19 adjacent →

Provenance

Where this comes from

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