Network · data from 2026-11-12
AS213791 XeniaGroup
Registry name: XeniaGroup-SRL XeniaGroup SRL, IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213791, 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.
| 31.57.112.0/24 | Invalid: origin | Other origin only | 47 7%low visibility |
| 79.172.207.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 116.204.166.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 178.239.122.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2.58.84.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 37.202.205.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 38.211.244.0/24 | Valid | RIR databaseARIN | 669 99% |
| 2a0c:b641:d60::/44 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS213791: AS213791:AS-XENIAGROUP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS213791 isn't in the set, or no route object for AS213791 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS213791 in it | Not covered |
|---|---|---|---|---|---|
| AS213791:AS-XENIAGROUP | RIPElists itself further down4 member sets in no database: AS199746:AS-NEXTSERV, AS215110:AS-CUSTOMERS, AS39753:AS-LIUXYON, AS401833:AS-AXNETCUSTOMERS | 813 | 307 | Yes | 4 |
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 12 are in fix.csv.
- ROA: origin4
- Route object: none4
- AS-SET: missing member4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 31.57.112.0/24 | ROAs covering it name AS834, not AS213791. If AS213791 should announce it, add a ROA for AS213791. |
| Route object: none | 31.57.112.0/24 | Route objects for it name AS834. Add a route object with origin AS213791 in the RIR database for the space. |
| ROA: origin | 79.172.207.0/24 | ROAs covering it name AS834, not AS213791. If AS213791 should announce it, add a ROA for AS213791. |
| Route object: none | 79.172.207.0/24 | Route objects for it name AS834. Add a route object with origin AS213791 in the RIR database for the space. |
| ROA: origin | 116.204.166.0/24 | ROAs covering it name AS216472, not AS213791. If AS213791 should announce it, add a ROA for AS213791. |
| Route object: none | 116.204.166.0/24 | Route objects for it name AS216472. Add a route object with origin AS213791 in the RIR database for the space. |
| ROA: origin | 178.239.122.0/24 | ROAs covering it name AS13537, not AS213791. If AS213791 should announce it, add a ROA for AS213791. |
| Route object: none | 178.239.122.0/24 | Route objects for it name AS13537. Add a route object with origin AS213791 in the RIR database for the space. |
| AS-SET: missing member | AS213791:AS-XENIAGROUP | AS213791:AS-XENIAGROUP (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | AS213791:AS-XENIAGROUP | AS213791:AS-XENIAGROUP (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS213791:AS-XENIAGROUP | AS213791:AS-XENIAGROUP (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it. |
| AS-SET: missing member | AS213791:AS-XENIAGROUP | AS213791:AS-XENIAGROUP (RIPE) lists AS401833:AS-AXNETCUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS213791 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.