bgpreport

Network · data from 2026-11-12

AS268255 AS268255 - FIBRANET BRASIL

Registry name: AS268255 - FIBRANET BRASIL, BR · not in PeeringDB

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

Announced routes

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

2804:4e58::/33 No ROA Nonecovered by 2804:4e58::/32 636 100% 67
2804:4e58:8000::/33 No ROA Nonecovered by 2804:4e58::/32 632 99% 67
209.14.148.0/22 No ROA Other IRR onlyRADB 666 99% 67
45.236.152.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.236.153.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.236.154.0/24 No ROA Other IRR onlyRADB 662 98% 67
45.236.155.0/24 No ROA Other IRR onlyRADB 662 98% 67
209.14.148.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
209.14.148.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
209.14.149.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
209.14.150.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
209.14.150.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
209.14.151.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

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

  • ROA: none13
  • Route object: none2
  • Route object: RIR11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:4e58::/33No ROA covers it. Add a ROA for AS268255, maxLength 33.636 of 636
Route object: none2804:4e58::/33No route object for it. A route object for 2804:4e58::/32 with origin AS268255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268255 in the RIR database for the space.636 of 636
ROA: none2804:4e58:8000::/33No ROA covers it. Add a ROA for AS268255, maxLength 33.632 of 636
Route object: none2804:4e58:8000::/33No route object for it. A route object for 2804:4e58::/32 with origin AS268255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268255 in the RIR database for the space.632 of 636
ROA: none209.14.148.0/22No ROA covers it. Add a ROA for AS268255, maxLength 22.666 of 673
Route object: RIR209.14.148.0/22Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none45.236.152.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.664 of 673
Route object: RIR45.236.152.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.236.153.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.664 of 673
Route object: RIR45.236.153.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.236.154.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.662 of 673
Route object: RIR45.236.154.0/24Route object only in RADB. Add it in the RIR database for the space.662 of 673
ROA: none45.236.155.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.662 of 673
Route object: RIR45.236.155.0/24Route object only in RADB. Add it in the RIR database for the space.662 of 673
ROA: none209.14.148.0/23No ROA covers it. Add a ROA for AS268255, maxLength 23.2 of 673
Route object: RIR209.14.148.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none209.14.148.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.2 of 673
Route object: RIR209.14.148.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none209.14.149.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.2 of 673
Route object: RIR209.14.149.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none209.14.150.0/23No ROA covers it. Add a ROA for AS268255, maxLength 23.2 of 673
Route object: RIR209.14.150.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none209.14.150.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.2 of 673
Route object: RIR209.14.150.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none209.14.151.0/24No ROA covers it. Add a ROA for AS268255, maxLength 24.2 of 673
Route object: RIR209.14.151.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.236.152.0/22RADBNo ROA
2804:4e58::/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.