Country
—
ASN LANDING PAGE
RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH
Last updated · Jul 20, 2026
Country
—
Total prefixes
17
IPv4 prefixes
16
IPv6 prefixes
1
RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH currently reports 17 prefixes and 49 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS6939
AS6939
—
AS60169
AS60169
—
AS1299
AS1299
—
AS2914
AS2914
—
AS34549
AS34549
—
AS35625
AS35625
—
AS34019
AS34019
—
AS34927
AS34927
—
AS14840
AS14840
—
AS48362
AS48362
—
AS6057
AS6057
—
AS29632
AS29632
—
AS34177
AS34177
—
AS35280
AS35280
—
AS8298
AS8298
—
AS7195
AS7195
—
AS25091
AS25091
—
AS20485
AS20485
—
AS41327
AS41327
—
AS35710
AS35710
—
AS37468
AS37468
—
AS12779
AS12779
—
AS29075
AS29075
—
AS29691
AS29691
—
AS8758
AS8758
—
AS24961
AS24961
—
AS39351
AS39351
—
AS58299
AS58299
—
AS3214
AS3214
—
AS8218
AS8218
—
AS25160
AS25160
—
AS25220
AS25220
—
AS35360
AS35360
—
AS52320
AS52320
—
AS58057
AS58057
—
AS137409
AS137409
—
AS199938
AS199938
—
AS213151
AS213151
—
AS3212
AS3212
—
AS14630
AS14630
—
| Prefix | Name | Country |
|---|---|---|
| 130.185.0.0/18 | AS12611 | — |
| 185.119.92.0/22 | AS12611 | — |
| 193.23.119.0/24 | AS12611 | — |
| 194.150.226.0/23 | AS12611 | — |
| 194.169.251.0/24 | AS12611 | — |
| 194.55.106.0/23 | AS12611 | — |
| 2001:16e0::/29 | AS12611 | — |
| 212.77.160.0/19 | AS12611 | — |
| 217.74.0.0/21 | AS12611 | — |
| 46.227.96.0/21 | AS12611 | — |
| 5.149.224.0/20 | AS12611 | — |
| 80.209.192.0/19 | AS12611 | — |
| 81.27.160.0/20 | AS12611 | — |
| 88.133.176.0/20 | AS12611 | — |
| 88.133.232.0/21 | AS12611 | — |
| 91.106.120.0/21 | AS12611 | — |
| 95.130.160.0/21 | AS12611 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS12611 is an autonomous system number. The current source associates it with RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS12611. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS12611, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.