bgpreport

Network · data from 2026-11-12

AS272138 AS272138 - RENOCA GROUP SRL

Registry name: AS272138 - RENOCA GROUP SRL, DO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272138, 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.
38.199.26.0/24 No ROA None 672 100% 67
206.84.83.0/24 No ROA Nonecovered by 206.84.82.0/23 672 100% 67
206.84.82.0/24 No ROA Nonecovered by 206.84.82.0/23 671 100% 67
38.199.27.0/24 No ROA None 670 100% 67
2803:e090::/33 No ROA Nonecovered by 2803:e090::/32 635 100% 67
2803:e090:8000::/33 No ROA Nonecovered by 2803:e090::/32 635 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.199.26.0/24No ROA covers it. Add a ROA for AS272138, maxLength 24.672 of 673
Route object: none38.199.26.0/24No route object for it. Add a route object with origin AS272138 in the RIR database for the space.672 of 673
ROA: none206.84.83.0/24No ROA covers it. Add a ROA for AS272138, maxLength 24.672 of 673
Route object: none206.84.83.0/24No route object for it. A route object for 206.84.82.0/23 with origin AS272138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272138 in the RIR database for the space.672 of 673
ROA: none206.84.82.0/24No ROA covers it. Add a ROA for AS272138, maxLength 24.671 of 673
Route object: none206.84.82.0/24No route object for it. A route object for 206.84.82.0/23 with origin AS272138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272138 in the RIR database for the space.671 of 673
ROA: none38.199.27.0/24No ROA covers it. Add a ROA for AS272138, maxLength 24.670 of 673
Route object: none38.199.27.0/24No route object for it. Add a route object with origin AS272138 in the RIR database for the space.670 of 673
ROA: none2803:e090::/33No ROA covers it. Add a ROA for AS272138, maxLength 33.635 of 636
Route object: none2803:e090::/33No route object for it. A route object for 2803:e090::/32 with origin AS272138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272138 in the RIR database for the space.635 of 636
ROA: none2803:e090:8000::/33No ROA covers it. Add a ROA for AS272138, maxLength 33.635 of 636
Route object: none2803:e090:8000::/33No route object for it. A route object for 2803:e090::/32 with origin AS272138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272138 in the RIR database for the space.635 of 636

Route objects not announced

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

206.84.82.0/23RADBNo ROA
2803:e090::/32RADBNo 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.