bgpreport

Network · data from 2026-11-12

AS199216 COMPASS-AS Compass-Verlag GmbH

Registry name: COMPASS-AS Compass-Verlag GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199216, 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.195.198.0/23 No ROA RIR databaseRIPE 673 100% 66
91.195.198.0/24 No ROA RIR databaseRIPE 673 100% 66
91.195.199.0/24 No ROA RIR databaseRIPE 673 100% 66
193.56.204.0/22 Valid RIR databaseRIPE 673 100% 66
193.56.204.0/24 Valid RIR databaseRIPE 673 100% 66
193.56.205.0/24 Valid RIR databaseRIPE 673 100% 66
193.56.206.0/24 Valid RIR databaseRIPE 673 100% 66
193.56.207.0/24 Valid RIR databaseRIPE 673 100% 66
2a01:190:15ec::/48 Valid RIR databaseRIPE 636 100% 69
2a0c:8f40::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS199216 isn't in PeeringDB, where networks name their 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none91.195.198.0/23No ROA covers it. Add a ROA for AS199216, maxLength 23.673 of 673
ROA: none91.195.198.0/24No ROA covers it. Add a ROA for AS199216, maxLength 24.673 of 673
ROA: none91.195.199.0/24No ROA covers it. Add a ROA for AS199216, maxLength 24.673 of 673

Route objects not announced

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