bgpreport

Network · data from 2026-11-12

AS60522 KomMITT

Registry name: KOMMITT-AS KomMITT-Ratingen GmbH, DE · PeeringDB

12IPv4 routes 83.3% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS60522, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60522, 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.
91.212.3.0/24 No ROA RIR databaseRIPE 673 100% 66
195.210.48.0/23 No ROA RIR databaseRIPE 673 100% 66
37.131.179.0/24 Valid RIR databaseRIPE 673 100% 66
37.131.180.0/22 Valid RIR databaseRIPE 673 100% 66
86.111.152.0/21 Valid RIR databaseRIPE 673 100% 66
134.255.192.0/22 Valid RIR databaseRIPE 673 100% 66
185.29.216.0/22 Valid RIR databaseRIPE 673 100% 66
185.188.108.0/22 Valid RIR databaseRIPE 673 100% 66
185.205.124.0/22 Valid RIR databaseRIPE 673 100% 66
185.212.52.0/22 Valid RIR databaseRIPE 673 100% 66
195.192.216.0/21 Valid RIR databaseRIPE 673 100% 66
217.61.192.0/20 Valid RIR databaseRIPE 673 100% 66
2a0b:72c0::/32 Valid RIR databaseRIPE 635 100% 69
2a0b:bf80::/32 Valid RIR databaseRIPE 635 100% 69
2a00:ab60::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS60522: RIPE::AS-KOMMITT. 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 (AS60522 isn't in the set, or no route object for AS60522 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 objectsAS60522 in itNot covered
RIPE::AS-KOMMITT RIPE 1115 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none91.212.3.0/24No ROA covers it. Add a ROA for AS60522, maxLength 24.673 of 673
ROA: none195.210.48.0/23No ROA covers it. Add a ROA for AS60522, maxLength 23.673 of 673

Route objects not announced

Every route object with origin AS60522 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.