bgpreport

Network · data from 2026-11-12

AS272838 AS272838 - FIBERRED SAC

Registry name: AS272838 - FIBERRED SAC, PE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272838, 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.225.86.0/24 No ROA Nonecovered by 38.225.86.0/23 672 100% 67
38.225.87.0/24 No ROA Nonecovered by 38.225.86.0/23 672 100% 67
38.158.82.0/24 No ROA Nonecovered by 38.158.82.0/23 671 100% 67
38.158.83.0/24 No ROA Nonecovered by 38.158.82.0/23 671 100% 67
38.225.86.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.158.82.0/23 No ROA Other IRR onlyRADB 672 100% 67
204.199.174.0/24 Valid None 672 100% 67
2803:9c90::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none38.225.86.0/24No ROA covers it. Add a ROA for AS272838, maxLength 24.672 of 673
Route object: none38.225.86.0/24No route object for it. A route object for 38.225.86.0/23 with origin AS272838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272838 in the RIR database for the space.672 of 673
ROA: none38.225.87.0/24No ROA covers it. Add a ROA for AS272838, maxLength 24.672 of 673
Route object: none38.225.87.0/24No route object for it. A route object for 38.225.86.0/23 with origin AS272838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272838 in the RIR database for the space.672 of 673
ROA: none38.158.82.0/24No ROA covers it. Add a ROA for AS272838, maxLength 24.671 of 673
Route object: none38.158.82.0/24No route object for it. A route object for 38.158.82.0/23 with origin AS272838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272838 in the RIR database for the space.671 of 673
ROA: none38.158.83.0/24No ROA covers it. Add a ROA for AS272838, maxLength 24.671 of 673
Route object: none38.158.83.0/24No route object for it. A route object for 38.158.82.0/23 with origin AS272838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272838 in the RIR database for the space.671 of 673
ROA: none38.225.86.0/23No ROA covers it. Add a ROA for AS272838, maxLength 23.673 of 673
Route object: RIR38.225.86.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.158.82.0/23No ROA covers it. Add a ROA for AS272838, maxLength 23.672 of 673
Route object: RIR38.158.82.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none204.199.174.0/24No route object for it. Add a route object with origin AS272838 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS272838 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.