bgpreport

Network · data from 2026-11-12

AS31259 Komsa

Registry name: KOMSA-AS Komsa GmbH, DE · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS31259, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31259, 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.
217.119.208.0/21 No ROA RIR databaseRIPE 673 100% 66
217.119.216.0/22 No ROA RIR databaseRIPE 673 100% 66
217.119.220.0/22 No ROA RIR databaseRIPE 673 100% 66
2a05:57c0::/36 No ROA RIR databaseRIPE 636 100% 69

AS-SET

AS31259's PeeringDB record names no AS-SET.

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 4 are in fix.csv.

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none217.119.208.0/21No ROA covers it. Add a ROA for AS31259, maxLength 21.673 of 673
ROA: none217.119.216.0/22No ROA covers it. Add a ROA for AS31259, maxLength 22.673 of 673
ROA: none217.119.220.0/22No ROA covers it. Add a ROA for AS31259, maxLength 22.673 of 673
ROA: none2a05:57c0::/36No ROA covers it. Add a ROA for AS31259, maxLength 36.636 of 636

Route objects not announced

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