AS12611 RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH
π©πͺOrg handle: ORG-RA3-RIPE
R-KOM Regensburger Telekommunikationsgesellschaft mbH
RIPE NCCallocated
Announced Prefixes (BGP)
17total
16 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)57,856
Announced (BGP)57,856
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)6.3Γ10Β²βΉ
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
5
Country
π©πͺ DERIR
RIPE NCCStatus
allocated
Allocated
1999-08-20
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)17Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.149.224.0/20 | π©πͺ DE | RIPENCC | allocated |
| 46.227.96.0/21 | π©πͺ DE | RIPENCC | allocated |
| 80.209.192.0/19 | π©πͺ DE | RIPENCC | allocated |
| 81.27.160.0/20 | π©πͺ DE | RIPENCC | allocated |
| 88.133.176.0/20 | π©πͺ DE | RIPENCC | allocated |
| 88.133.232.0/21 | π©πͺ DE | RIPENCC | allocated |
| 91.106.120.0/21 | π©πͺ DE | RIPENCC | allocated |
| 95.130.160.0/21 | π©πͺ DE | RIPENCC | allocated |
| 130.185.0.0/18 | π©πͺ DE | RIPE | assigned |
| 185.119.92.0/22 | π©πͺ DE | RIPENCC | allocated |
1-10 of 17
1 / 2
All 17 announced prefixes of AS12611 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS12611 hands its own prefixes to: transit providers, or peers at an exchange.
- AS60169GFIT R KOM Regensburger Telekommunikationsgesellschaft MbH17
Downstreams (8)
Networks whose own prefixes AS12611 passes on: usually its customers.
ASPA
No ASPA
Abuse Contact
+31205354444
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS12611 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/12611Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/12611" | jq