bgpreport

Network · data from 2026-11-12

AS12611 R-KOM

Registry name: RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH, DE · PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS12611, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS12611, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
5.149.224.0/20 Valid RIR databaseRIPE 672 100% 66
46.227.96.0/21 Valid RIR databaseRIPE 672 100% 66
80.209.192.0/19 Valid RIR databaseRIPE 672 100% 66
81.27.160.0/20 Valid RIR databaseRIPE 672 100% 66
88.133.176.0/20 Valid RIR databaseRIPE 672 100% 66
88.133.232.0/21 Valid RIR databaseRIPE 672 100% 66
91.106.120.0/21 Valid RIR databaseRIPE 672 100% 66
95.130.160.0/21 Valid RIR databaseRIPE 672 100% 66
130.185.0.0/18 Valid RIR databaseRIPE 672 100% 66
185.119.92.0/22 Valid RIR databaseRIPE 672 100% 66
193.23.119.0/24 Valid RIR databaseRIPE 672 100% 66
194.55.106.0/23 Valid RIR databaseRIPE 672 100% 66
194.150.226.0/23 Valid RIR databaseRIPE 672 100% 66
194.169.251.0/24 Valid RIR databaseRIPE 672 100% 66
212.77.160.0/19 Valid RIR databaseRIPE 672 100% 66
217.74.0.0/21 Valid RIR databaseRIPE 672 100% 66
2001:16e0::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS12611: AS12611:AS-RKOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS12611 isn't in the set, or no route object for AS12611 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS12611 in itNot covered
AS12611:AS-RKOM RIPElists itself further down 3118286 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS12611 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.