bgpreport

Network · data from 2026-11-12

AS216416 Evolus-Fibre Evolus IT Solutions GmbH

Registry name: Evolus-Fibre Evolus IT Solutions GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216416, 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.124.149.0/24 Invalid: origin Other origin only 2 0%low visibility 2
167.148.159.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a12:bec4:19a7::/48 No ROA RIR databaseRIPE 634 100% 69
157.173.16.0/21 Valid None 2 0%low visibility 2
157.173.16.0/24 Valid RIR databaseRIPE 673 100% 67
157.173.21.0/24 Valid RIR databaseRIPE 673 100% 67
157.173.27.0/24 Valid RIR databaseRIPE 673 100% 67
185.207.139.0/24 Valid RIR databaseRIPE 673 100% 67
188.137.152.0/24 Valid RIR databaseRIPE 673 100% 67
89.106.81.0/24 Valid RIR databaseRIPE 672 100% 66
89.144.17.0/24 Valid RIR databaseRIPE 672 100% 66
145.11.16.0/21 Valid RIR databaseRIPE 672 100% 67
157.173.25.0/24 Valid RIR databaseRIPE 672 100% 67
157.173.26.0/24 Valid RIR databaseRIPE 672 100% 67
157.173.29.0/24 Valid RIR databaseRIPE 672 100% 67
157.173.30.0/24 Valid RIR databaseRIPE 672 100% 66
185.207.136.0/24 Valid RIR databaseRIPE 672 100% 66
185.207.138.0/24 Valid RIR databaseRIPE 672 100% 67
188.137.153.0/24 Valid RIR databaseRIPE 672 100% 67
188.137.154.0/24 Valid RIR databaseRIPE 672 100% 67
188.137.156.0/24 Valid RIR databaseRIPE 672 100% 67
188.137.157.0/24 Valid RIR databaseRIPE 672 100% 67
157.173.20.0/24 Valid RIR databaseRIPE 671 100% 67
185.207.137.0/24 Valid RIR databaseRIPE 671 100% 67
157.173.17.0/24 Valid RIR databaseRIPE 666 99% 67

AS-SET

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

  • ROA: origin2
  • ROA: none1
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin91.124.149.0/24ROAs covering it name AS214483, not AS216416. If AS216416 should announce it, add a ROA for AS216416.2 of 673
Route object: none91.124.149.0/24Route objects for it name AS214483. Add a route object with origin AS216416 in the RIR database for the space.2 of 673
ROA: origin167.148.159.0/24ROAs covering it name AS834, not AS216416. If AS216416 should announce it, add a ROA for AS216416.2 of 673
Route object: none167.148.159.0/24Route objects for it name AS834. Add a route object with origin AS216416 in the RIR database for the space.2 of 673
ROA: none2a12:bec4:19a7::/48No ROA covers it. Add a ROA for AS216416, maxLength 48.634 of 636
Route object: none157.173.16.0/21No route object for it. Add a route object with origin AS216416 in the RIR database for the space.2 of 673

Route objects not announced

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