bgpreport

Network · data from 2026-11-12

AS211066 RYZEHOSTING-TRADING Simon Mariacher

Registry name: RYZEHOSTING-TRADING Simon Mariacher, AT · not in PeeringDB

4IPv4 routes 75.0% RPKI valid · 75.0% with a route object
19IPv6 routes 94.7% RPKI valid · 47.4% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 11 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS211066, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211066, 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.
89.106.75.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a05:dfc3:fc00::/40 No ROA None 631 99% 67
2a06:1283:8b12::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b13::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b14::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b15::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b16::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b17::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b18::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b19::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
2a06:1283:8b1a::/48 Valid Nonecovered by 2a06:1283:8b00::/40 633 100% 69
5.175.192.0/24 Valid RIR databaseRIPE 671 100% 66
5.175.221.0/24 Valid RIR databaseRIPE 671 100% 66
5.175.130.0/24 Valid RIR databaseRIPE 668 99% 67
2a06:1283:8a00::/40 Valid RIR databaseRIPE 633 100% 69
2a06:1283:8e00::/40 Valid RIR databaseRIPE 633 100% 69
2a06:1283:8f00::/40 Valid RIR databaseRIPE 633 100% 69
2a06:1283:c130::/44 Valid RIR databaseRIPE 633 100% 69
2a09:54c3:9000::/36 Valid RIR databaseRIPE 633 100% 69
2a0f:9400:7722::/48 Valid RIR databaseRIPE 633 100% 69
2a06:1283:8c00::/40 Valid RIR databaseRIPE 632 99% 69
2a14:1ec1:1300::/40 Valid RIR databaseRIPE 632 99% 67
2a14:1ec1:1400::/40 Valid RIR databaseRIPE 632 99% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none11
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin89.106.75.0/24ROAs covering it name AS12586, not AS211066. If AS211066 should announce it, add a ROA for AS211066.2 of 673
Route object: none89.106.75.0/24Route objects for it name AS12586. Add a route object with origin AS211066 in the RIR database for the space.2 of 673
ROA: none2a05:dfc3:fc00::/40No ROA covers it. Add a ROA for AS211066, maxLength 40.631 of 636
Route object: none2a05:dfc3:fc00::/40No route object for it. Add a route object with origin AS211066 in the RIR database for the space.631 of 636
Route object: none2a06:1283:8b12::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b13::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b14::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b15::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b16::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b17::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b18::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b19::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636
Route object: none2a06:1283:8b1a::/48No route object for it. A route object for 2a06:1283:8b00::/40 with origin AS211066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211066 in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS211066 whose prefix no peer sees AS211066 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.83.133.0/24RIPEValid
5.83.134.0/24RIPEValid
5.175.140.0/24RIPEValid
2a06:1283:8b00::/40RIPEValid
2a06:1283:8b08::/48RIPEValid
2a06:1283:8b09::/48RIPEValid
2a06:1283:8b0a::/48RIPEValid
2a06:1283:8b0b::/48RIPEValid
2a06:1283:8b0c::/48RIPEValid
2a06:1283:8bb0::/44RIPEValid
2a06:1283:8d00::/40RIPEValid
2a06:1283:c11f::/48RIPEValid
2a14:1ec1:1000::/36RIPEValid

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.