bgpreport

Network · data from 2026-11-12

AS28686 Aveniq

Registry name: AVENIQ-AS Aveniq AG, CH · PeeringDB

26IPv4 routes 88.5% RPKI valid · 100.0% with a route object
5IPv6 routes 60.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS28686, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS28686, 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.
93.191.248.0/21 No ROA RIR databaseRIPE 673 100% 67
185.184.116.0/22 No ROA RIR databaseRIPE 671 100% 67
185.196.104.0/22 No ROA RIR databaseRIPE 671 100% 67
2a0b:3380::/29 No ROA RIR databaseRIPE 634 100% 68
2a0a:6bc0::/29 No ROA RIR databaseRIPE 633 100% 68
93.191.255.0/24 Valid RIR databaseRIPE 673 100% 70
159.168.0.0/16 Valid RIR databaseRIPE 673 100% 67
159.168.0.0/24 Valid RIR databaseRIPE 673 100% 67
159.168.112.0/20 Valid RIR databaseRIPE 673 100% 67
159.168.144.0/21 Valid RIR databaseRIPE 673 100% 67
159.168.152.0/21 Valid RIR databaseRIPE 673 100% 67
194.147.176.0/20 Valid RIR databaseRIPE 673 100% 67
103.55.232.0/22 Valid RIR databaseRIPE 671 100% 67
159.168.1.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.7.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.12.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.14.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.24.0/23 Valid RIR databaseRIPE 671 100% 67
159.168.136.0/23 Valid RIR databaseRIPE 671 100% 67
159.168.138.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.140.0/24 Valid RIR databaseRIPE 671 100% 67
159.168.141.0/24 Valid RIR databaseRIPE 671 100% 67
185.94.144.0/22 Valid RIR databaseRIPE 671 100% 67
185.130.140.0/22 Valid RIR databaseRIPE 671 100% 67
193.135.109.0/24 Valid RIR databaseRIPE 671 100% 67
193.222.224.0/20 Valid RIR databaseRIPE 671 100% 67
193.222.240.0/24 Valid RIR databaseRIPE 671 100% 67
194.147.192.0/22 Valid RIR databaseRIPE 671 100% 67
2001:67c:638::/48 Valid RIR databaseRIPE 634 100% 68
2a05:14c0::/29 Valid RIR databaseRIPE 634 100% 68
2a06:d9c0::/29 Valid RIR databaseRIPE 633 100% 68

AS-SET

AS28686'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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none93.191.248.0/21No ROA covers it. Add a ROA for AS28686, maxLength 21.673 of 673
ROA: none185.184.116.0/22No ROA covers it. Add a ROA for AS28686, maxLength 22.671 of 673
ROA: none185.196.104.0/22No ROA covers it. Add a ROA for AS28686, maxLength 22.671 of 673
ROA: none2a0b:3380::/29No ROA covers it. Add a ROA for AS28686, maxLength 29.634 of 636
ROA: none2a0a:6bc0::/29No ROA covers it. Add a ROA for AS28686, maxLength 29.633 of 636

Route objects not announced

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