bgpreport

Network · data from 2026-11-12

AS273102 AS273102 - REDNET GROUP SAS

Registry name: AS273102 - REDNET GROUP SAS, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273102, 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.191.217.0/24 No ROA None 670 100% 67
2803:b050:1000::/38 Valid Nonecovered by 2803:b050::/32 636 100% 67
2803:b050:400::/38 Valid Nonecovered by 2803:b050::/32 635 100% 69
2803:b050:800::/38 Valid Nonecovered by 2803:b050::/32 635 100% 69
2803:b050:1400::/38 Valid Nonecovered by 2803:b050::/32 635 100% 69
2803:b050:1800::/38 Valid Nonecovered by 2803:b050::/32 635 100% 69

AS-SET

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

  • ROA: none1
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.191.217.0/24No ROA covers it. Add a ROA for AS273102, maxLength 24.670 of 673
Route object: none38.191.217.0/24No route object for it. Add a route object with origin AS273102 in the RIR database for the space.670 of 673
Route object: none2803:b050:1000::/38No route object for it. A route object for 2803:b050::/32 with origin AS273102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273102 in the RIR database for the space.636 of 636
Route object: none2803:b050:400::/38No route object for it. A route object for 2803:b050::/32 with origin AS273102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273102 in the RIR database for the space.635 of 636
Route object: none2803:b050:800::/38No route object for it. A route object for 2803:b050::/32 with origin AS273102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273102 in the RIR database for the space.635 of 636
Route object: none2803:b050:1400::/38No route object for it. A route object for 2803:b050::/32 with origin AS273102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273102 in the RIR database for the space.635 of 636
Route object: none2803:b050:1800::/38No route object for it. A route object for 2803:b050::/32 with origin AS273102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273102 in the RIR database for the space.635 of 636

Route objects not announced

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

2803:b050::/32RADBValid

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.