bgpreport

Network · data from 2026-11-12

AS28248 AS28248 - BRB - Banco de Brasilia S/A

Registry name: AS28248 - BRB - Banco de Brasilia S/A, BR · not in PeeringDB

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

Announced routes

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

200.11.21.0/24 No ROA Nonecovered by 200.11.16.0/21 669 99% 67
200.11.22.0/24 No ROA Other IRR onlyRADB 670 100% 66
200.11.16.0/24 No ROA Other IRR onlyRADB 669 99% 66
200.11.17.0/24 No ROA Other IRR onlyRADB 669 99% 66
200.11.27.0/24 No ROA Other IRR onlyRADB 669 99% 66
200.11.26.0/24 No ROA Other IRR onlyRADB 668 99% 67
200.11.28.0/24 No ROA Other IRR onlyRADB 666 99% 66
2801:80:1aa0::/48 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS28248 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.11.21.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.669 of 673
Route object: none200.11.21.0/24No route object for it. A route object for 200.11.16.0/21 with origin AS28248 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28248 in the RIR database for the space.669 of 673
ROA: none200.11.22.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.670 of 673
Route object: RIR200.11.22.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.11.16.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.669 of 673
Route object: RIR200.11.16.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.11.17.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.669 of 673
Route object: RIR200.11.17.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.11.27.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.669 of 673
Route object: RIR200.11.27.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.11.26.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.668 of 673
Route object: RIR200.11.26.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.11.28.0/24No ROA covers it. Add a ROA for AS28248, maxLength 24.666 of 673
Route object: RIR200.11.28.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2801:80:1aa0::/48No ROA covers it. Add a ROA for AS28248, maxLength 48.634 of 636
Route object: RIR2801:80:1aa0::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

200.11.16.0/21RADBNo ROA
200.11.24.0/22RADBNo 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.