bgpreport

Network · data from 2026-11-12

AS268945 AS268945 - Boa vista Net Ltda - me

Registry name: AS268945 - Boa vista Net Ltda - me, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268945, 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:5d00::/33 No ROA Nonecovered by 2804:5d00::/32 636 100% 67
2804:5d00:8000::/33 No ROA Nonecovered by 2804:5d00::/32 636 100% 67
2804:5d00:d000::/36 No ROA Nonecovered by 2804:5d00::/32 636 100% 67
45.176.145.0/24 No ROA Other IRR onlyRADB, TC 673 100% 67
45.176.147.0/24 No ROA Other IRR onlyRADB, TC 673 100% 67
45.176.144.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
45.176.144.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
45.176.146.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
45.190.0.0/22 No ROA Other IRR onlyALTDB, TC 672 100% 67
45.190.0.0/23 No ROA Other IRR onlyTC 671 100% 67
45.190.2.0/23 No ROA Other IRR onlyTC 671 100% 67
2804:5d00::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS268945 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 33 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none2804:5d00::/33No ROA covers it. Add a ROA for AS268945, maxLength 33.636 of 636
Route object: none2804:5d00::/33No route object for it. A route object for 2804:5d00::/32 with origin AS268945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268945 in the RIR database for the space.636 of 636
ROA: none2804:5d00:8000::/33No ROA covers it. Add a ROA for AS268945, maxLength 33.636 of 636
Route object: none2804:5d00:8000::/33No route object for it. A route object for 2804:5d00::/32 with origin AS268945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268945 in the RIR database for the space.636 of 636
ROA: none2804:5d00:d000::/36No ROA covers it. Add a ROA for AS268945, maxLength 36.636 of 636
Route object: none2804:5d00:d000::/36No route object for it. A route object for 2804:5d00::/32 with origin AS268945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268945 in the RIR database for the space.636 of 636
ROA: none45.176.145.0/24No ROA covers it. Add a ROA for AS268945, maxLength 24.673 of 673
Route object: RIR45.176.145.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
ROA: none45.176.147.0/24No ROA covers it. Add a ROA for AS268945, maxLength 24.673 of 673
Route object: RIR45.176.147.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
ROA: none45.176.144.0/22No ROA covers it. Add a ROA for AS268945, maxLength 22.672 of 673
Route object: RIR45.176.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.176.144.0/24No ROA covers it. Add a ROA for AS268945, maxLength 24.672 of 673
Route object: RIR45.176.144.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.176.146.0/24No ROA covers it. Add a ROA for AS268945, maxLength 24.672 of 673
Route object: RIR45.176.146.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.190.0.0/22No ROA covers it. Add a ROA for AS268945, maxLength 22.672 of 673
Route object: RIR45.190.0.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.190.0.0/23No ROA covers it. Add a ROA for AS268945, maxLength 23.671 of 673
Route object: RIR45.190.0.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.190.2.0/23No ROA covers it. Add a ROA for AS268945, maxLength 23.671 of 673
Route object: RIR45.190.2.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:5d00::/32No ROA covers it. Add a ROA for AS268945, maxLength 32.636 of 636
Route object: RIR2804:5d00::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.176.144.0/23TCNo ROA
45.176.146.0/23TCNo ROA
45.190.0.0/24TCNo ROA
45.190.1.0/24TCNo ROA
45.190.2.0/24TCNo ROA
45.190.3.0/24TCNo ROA
2804:5d00:c000::/36RADBNo ROA
2804:5d00:c200::/40RADBNo ROA
2804:5d00:c400::/40RADBNo 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.