bgpreport

Network · data from 2026-11-12

AS218698 XENIAGROUP-AS XeniaGroup SRL

Registry name: XENIAGROUP-AS XeniaGroup SRL, IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218698, 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.
2a14:7582:b000::/36 Invalid: origin None 1 0%low visibility 3
5.175.191.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS218698 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin2a14:7582:b000::/36An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS218698 should announce it, add a ROA for AS218698.1 of 636
Route object: none2a14:7582:b000::/36No route object for it. Add a route object with origin AS218698 in the RIR database for the space.1 of 636

Route objects not announced

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