Skip to main content

AS12931

IDKOM

IDKOM Networks GmbH

Registry

Authoritative registration data

AS number
12931
Name
IDKOM
Organisation
IDKOM Networks GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS12931
213.182.0.0/19 IPv4 /19 not checked
46.35.48.0/20 IPv4 /20 not checked
2001:14e0::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS12931
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 1,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
MegaIX Berlin 1,000 Mbps IPv4 · IPv6
MegaIX Dusseldorf 1,000 Mbps IPv4 · IPv6
MegaIX Frankfurt 1,000 Mbps IPv4 · IPv6
MegaIX Hamburg 1,000 Mbps IPv4 · IPv6
MegaIX Munich 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS12931 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

41 networks seen before AS12931 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS12931 in AS paths

Observed downstreams
Families
AS21173 ASN-LANTANA 156 382
v4

No rows match “”.

Showing – of

Uncertain adjacencies

53 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.