bgpreport

Network · data from 2026-11-12

AS35665 Netensia

Registry name: Netensia Netensia SARL, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35665, 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.18.96.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.97.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.98.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.99.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.100.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.101.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.102.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
46.18.103.0/24 Valid Nonecovered by 46.18.96.0/21 670 100% 67
152.89.96.0/22 Valid RIR databaseRIPE 673 100% 67
195.160.188.0/24 Valid RIR databaseRIPE 673 100% 67
195.160.189.0/24 Valid RIR databaseRIPE 673 100% 67
213.108.232.0/23 Valid RIR databaseRIPE 673 100% 67
213.108.234.0/23 Valid RIR databaseRIPE 673 100% 67
213.108.236.0/23 Valid RIR databaseRIPE 673 100% 67
213.108.238.0/23 Valid RIR databaseRIPE 673 100% 67
185.177.224.0/22 Valid RIR databaseRIPE 671 100% 67
2a02:2778::/32 Valid RIR databaseRIPE 376 59% 65

AS-SET

PeeringDB's irr_as_set for AS35665: AS-NETENSIA. 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 (AS35665 isn't in the set, or no route object for AS35665 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 objectsAS35665 in itNot covered
AS-NETENSIA RIPE 5121 Yes 0

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.

  • Route object: none8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none46.18.96.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.97.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.98.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.99.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.100.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.101.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.102.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673
Route object: none46.18.103.0/24No route object for it. A route object for 46.18.96.0/21 with origin AS35665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35665 in the RIR database for the space.670 of 673

Route objects not announced

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

46.18.96.0/21RIPENo ROA
195.160.188.0/23RIPENo ROA
213.108.232.0/21RIPENo ROA
2a02:2778:4000::/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.