bgpreport

Network · data from 2026-11-12

AS271397 AS271397 - Anderson Barreto da Cruz

Registry name: AS271397 - Anderson Barreto da Cruz, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271397, 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.
177.71.110.0/24 No ROA Nonecovered by 177.71.110.0/23 669 99% 67
177.71.111.0/24 No ROA Nonecovered by 177.71.110.0/23 669 99% 67
2804:7ae0::/33 No ROA Nonecovered by 2804:7ae0::/32 633 100% 67
177.71.110.0/23 No ROA Other IRR onlyRADB 672 100% 67
177.71.108.0/23 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS271397 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none177.71.110.0/24No ROA covers it. Add a ROA for AS271397, maxLength 24.669 of 673
Route object: none177.71.110.0/24No route object for it. A route object for 177.71.110.0/23 with origin AS271397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271397 in the RIR database for the space.669 of 673
ROA: none177.71.111.0/24No ROA covers it. Add a ROA for AS271397, maxLength 24.669 of 673
Route object: none177.71.111.0/24No route object for it. A route object for 177.71.110.0/23 with origin AS271397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271397 in the RIR database for the space.669 of 673
ROA: none2804:7ae0::/33No ROA covers it. Add a ROA for AS271397, maxLength 33.633 of 636
Route object: none2804:7ae0::/33No route object for it. A route object for 2804:7ae0::/32 with origin AS271397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271397 in the RIR database for the space.633 of 636
ROA: none177.71.110.0/23No ROA covers it. Add a ROA for AS271397, maxLength 23.672 of 673
Route object: RIR177.71.110.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.71.108.0/23No ROA covers it. Add a ROA for AS271397, maxLength 23.670 of 673
Route object: RIR177.71.108.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

177.71.108.0/22RADBNo ROA
2804:7ae0::/32ALTDB, RADBNo 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.