bgpreport

Network · data from 2026-11-12

AS203148 Xenius

Registry name: XENIUS Xenius BVBA, BE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203148, 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.
2a02:67e0::/32 No ROA RIR databaseRIPE 636 100% 67
2a02:67e0::/35 No ROA RIR databaseRIPE 636 100% 67
2a02:67e0:e000::/35 No ROA RIR databaseRIPE 636 100% 67
185.130.148.0/24 Valid Other origin onlycovered by 185.130.148.0/22 671 100% 67
185.59.16.0/23 Valid RIR databaseRIPE 671 100% 67
185.59.18.0/24 Valid RIR databaseRIPE 671 100% 67
185.59.19.0/24 Valid RIR databaseRIPE 671 100% 67
185.130.148.0/22 Valid RIR databaseRIPE 671 100% 67
46.18.32.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a02:67e0::/32No ROA covers it. Add a ROA for AS203148, maxLength 32.636 of 636
ROA: none2a02:67e0::/35No ROA covers it. Add a ROA for AS203148, maxLength 35.636 of 636
ROA: none2a02:67e0:e000::/35No ROA covers it. Add a ROA for AS203148, maxLength 35.636 of 636
Route object: none185.130.148.0/24Route objects for it name AS203630. A route object for 185.130.148.0/22 with origin AS203148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203148 in the RIR database for the space.671 of 673

Route objects not announced

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

185.59.16.0/22RIPEValid
2a02:67e0:2000::/35RIPENo ROA

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.