bgpreport

Network · data from 2026-11-12

AS43142 Adeli

Registry name: AdeliNovius ADELI SAS, FR · PeeringDB

22IPv4 routes 90.9% RPKI valid · 90.9% with a route object
15IPv6 routes 93.3% RPKI valid · 93.3% with a route object
2RPKI invalid 0 origin · 2 maxLength
1No ROA 3 with no route object for this origin
13Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS43142, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43142, 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.

46.227.16.8/32 Invalid: maxLength Nonecovered by 46.227.16.0/24 2 0%low visibility 3
188.214.103.0/32 Invalid: maxLength Nonecovered by 188.214.103.0/24 2 0%low visibility 3
2a10:1800:666::666/128 No ROA None 1 0%low visibility 1
46.227.16.0/21 Valid RIR databaseRIPE 673 100% 67
46.227.16.0/23 Valid RIR databaseRIPE 673 100% 67
91.194.96.0/22 Valid RIR databaseRIPE 673 100% 67
91.194.96.0/24 Valid RIR databaseRIPE 673 100% 67
91.194.97.0/24 Valid RIR databaseRIPE 673 100% 67
91.194.100.0/23 Valid RIR databaseRIPE 673 100% 67
91.194.100.0/24 Valid RIR databaseRIPE 673 100% 67
91.194.101.0/24 Valid RIR databaseRIPE 673 100% 67
185.8.64.0/22 Valid RIR databaseRIPE 673 100% 67
185.8.65.0/24 Valid RIR databaseRIPE 673 100% 67
188.214.102.0/23 Valid RIR databaseRIPE 673 100% 67
188.214.102.0/24 Valid RIR databaseRIPE 673 100% 67
188.214.103.0/24 Valid RIR databaseRIPE 673 100% 67
46.227.20.0/24 Valid RIR databaseRIPE 672 100% 67
46.227.21.0/24 Valid RIR databaseRIPE 672 100% 67
2a01:6e00::/32 Valid RIR databaseRIPE 634 100% 67
2a01:6e00:4::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:5::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:6::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:7::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:8::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:9::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:10::/48 Valid RIR databaseRIPE 381 60% 65
2a01:6e00:8000::/33 Valid RIR databaseRIPE 381 60% 65
46.227.20.0/22 Valid RIR databaseRIPE 4 1%low visibility 3
46.227.18.0/23 Valid RIR databaseRIPE 1 0%low visibility 1
91.194.96.0/23 Valid RIR databaseRIPE 1 0%low visibility 1
91.194.98.0/23 Valid RIR databaseRIPE 1 0%low visibility 1
185.8.64.0/23 Valid RIR databaseRIPE 1 0%low visibility 1
2a01:6e00::/33 Valid RIR databaseRIPE 1 0%low visibility 1
2a01:6e00::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a01:6e00:1::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a01:6e00:2::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a01:6e00:3::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS43142: AS-ADELINOVIUS. 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 (AS43142 isn't in the set, or no route object for AS43142 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.

NameDatabaseASNsSets Route objectsAS43142 in itNot covered
AS-ADELINOVIUS RIPE 163135 Yes 3

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

  • ROA: maxLength2
  • ROA: none1
  • Route object: none3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: maxLength46.227.16.8/32ROA 46.227.16.0/21 AS43142 has maxLength 21; ROA 46.227.16.0/23 AS43142 has maxLength 23; ROA 46.227.16.0/24 AS43142 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 46.227.16.8/32.2 of 673
Route object: none46.227.16.8/32No route object for it. A route object for 46.227.16.0/24 with origin AS43142 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43142 in the RIR database for the space.2 of 673
ROA: maxLength188.214.103.0/32ROA 188.214.102.0/23 AS43142 has maxLength 24; ROA 188.214.103.0/24 AS43142 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 188.214.103.0/32.2 of 673
Route object: none188.214.103.0/32No route object for it. A route object for 188.214.103.0/24 with origin AS43142 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43142 in the RIR database for the space.2 of 673
ROA: none2a10:1800:666::666/128No ROA covers it. Add a ROA for AS43142, maxLength 128.1 of 636
Route object: none2a10:1800:666::666/128No route object for it. Add a route object with origin AS43142 in the RIR database for the space.1 of 636

Route objects not announced

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

46.227.16.0/24RIPEValid
46.227.17.0/24RIPEValid
46.227.18.0/24RIPEValid
46.227.19.0/24RIPEValid
46.227.20.0/23RIPEInvalid: maxLength
46.227.22.0/23RIPEInvalid: maxLength
46.227.22.0/24RIPEValid
46.227.23.0/24RIPEValid
91.194.98.0/24RIPEValid
185.8.64.0/24RIPEValid
185.8.66.0/23RIPEValid
185.8.66.0/24RIPEValid
185.8.67.0/24RIPEValid
2a01:6e00::/34RIPEInvalid: maxLength

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.