asn.dev

Autonomous system

AS12611 RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH

Unclassified RIPE

IPv4 addresses 57.86K 16 prefixes
IPv6 prefixes 1 counted as prefixes, not addresses
Countries 1 mostly DE
Exchanges 2 recorded by PCH
Upstreams 17 9 downstream
Flagged prefixes 0 none

Summary

R-KOM

Germany · AI-generated

isp business telecom

A Regensburg city network whose reverse names say which customers are behind carrier NAT and which data centre they sit in.

What it's used for

  • Internet access in and around Regensburg. 57,856 addresses in 16 IPv4 prefixes, one IPv6 prefix, and 122 observed BGP neighbours.

Notable

  • Twelve netname dates from DE-R-KOM-19990728 through 20001215, 20011212, 20020412, 20051028, 20090312, 20110128, 20111021, 20120621, 20120717 and 20150929.
  • Sampled addresses in the largest block answer 130-185-16-0.cgnat.rz1.r-kom.net and 130-185-47-254.cgnat.rz3.r-kom.net.
  • Addresses in the other blocks answer hsi.r-kom.net instead, as in 80-209-207-255.hsi.r-kom.net.
  • The IPv6 announcement is 2001:16e0::/29.

Interesting

  • cgnat is carrier-grade address translation: many subscribers sharing one public address. Publishing that label in reverse DNS tells anyone who looks which addresses cannot be traced to a single customer, which is useful to an abuse desk reading logs and equally useful to anyone deciding whether blocking an address will hit one household or a hundred.
  • The rz1 and rz3 labels number the data centres the translation runs in, so the reverse zone doubles as a topology map. The /18 carrying the shared addresses is the largest block here — the growth of the subscriber base outran the address supply, and this is what the workaround looks like from outside.
  • Twelve dated allocations across sixteen years is the most complete growth record in this stretch of the number range, one row per visit to the registry.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

Recorded at 2 exchanges in 1 country, largest first.

ExchangeLocationTheir address
DE-CIX FrankfurtFrankfurt, Germany80.81.192.202
DE-CIX MunichMunich, Germany185.1.208.72

Transit providers

17 upstream, 9 downstream and 47 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS1299Arelion Sweden AB273
AS2914NTT America, Inc.193
AS60169R-KOM Regensburger Telekommunikationsgesellschaft mbH178
AS6939Hurricane Electric LLC153
AS34549meerfarbig GmbH & Co. KG65
AS24482SG.GS17
AS48362Stadtwerke Feldkirch17
AS212024Marc Schmitt17

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 16 prefixes · 57.86K addresses IPv6 1 prefixes

CountryNamePrefixes
DEGermany17

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS12611
Registry name
RKOM
Registrant
R-KOM Regensburger Telekommunikationsgesellschaft mbH
Abuse contact
abuse@r-kom.de
Registered
2002-09-25
Last changed
2026-04-28
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 17 valid, 0 with no ROA
ROAs
17 authorising AS12611
ASPA
no ASPA record
IRR
100% registered · 17 of 17 announcements
Route objects
17 naming AS12611

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,782 prefixes, as published 2026-10-16. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check