bgpreport

Network · data from 2026-11-12

AS271457 AS271457 - VOLTSNET PROVEDOR COMERCIO E SERVICO LTDA ME ME

Registry name: AS271457 - VOLTSNET PROVEDOR COMERCIO E SERVICO LTDA ME ME, BR · not in PeeringDB

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

Announced routes

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

190.52.65.0/24 No ROA Nonecovered by 190.52.64.0/22 671 100% 67
190.52.64.0/23 No ROA Nonecovered by 190.52.64.0/22 670 100% 67
190.52.64.0/24 No ROA Nonecovered by 190.52.64.0/22 670 100% 67
2804:7bd4::/33 No ROA Nonecovered by 2804:7bd4::/32 636 100% 67
190.52.66.0/23 No ROA Other IRR onlyRADB 673 100% 66
190.52.66.0/24 No ROA Other IRR onlyRADB 673 100% 66
190.52.67.0/24 No ROA Other IRR onlyRADB 673 100% 66
2804:7bd4:f000::/36 No ROA Other IRR onlyRADB 633 100% 67

AS-SET

AS271457 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: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none190.52.65.0/24No ROA covers it. Add a ROA for AS271457, maxLength 24.671 of 673
Route object: none190.52.65.0/24No route object for it. A route object for 190.52.64.0/22 with origin AS271457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271457 in the RIR database for the space.671 of 673
ROA: none190.52.64.0/23No ROA covers it. Add a ROA for AS271457, maxLength 23.670 of 673
Route object: none190.52.64.0/23No route object for it. A route object for 190.52.64.0/22 with origin AS271457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271457 in the RIR database for the space.670 of 673
ROA: none190.52.64.0/24No ROA covers it. Add a ROA for AS271457, maxLength 24.670 of 673
Route object: none190.52.64.0/24No route object for it. A route object for 190.52.64.0/22 with origin AS271457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271457 in the RIR database for the space.670 of 673
ROA: none2804:7bd4::/33No ROA covers it. Add a ROA for AS271457, maxLength 33.636 of 636
Route object: none2804:7bd4::/33No route object for it. A route object for 2804:7bd4::/32 with origin AS271457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271457 in the RIR database for the space.636 of 636
ROA: none190.52.66.0/23No ROA covers it. Add a ROA for AS271457, maxLength 23.673 of 673
Route object: RIR190.52.66.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none190.52.66.0/24No ROA covers it. Add a ROA for AS271457, maxLength 24.673 of 673
Route object: RIR190.52.66.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none190.52.67.0/24No ROA covers it. Add a ROA for AS271457, maxLength 24.673 of 673
Route object: RIR190.52.67.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2804:7bd4:f000::/36No ROA covers it. Add a ROA for AS271457, maxLength 36.633 of 636
Route object: RIR2804:7bd4:f000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

190.52.64.0/22TCNo ROA
2804:7bd4::/32TCNo 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.