bgpreport

Network · data from 2026-11-12

AS273467 H R B LACERDA

Registry name: AS273467 - H R B LACERDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273467, 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:8f18:6800::/40 Invalid: maxLength Nonecovered by 2804:8f18::/33 51 8%low visibility 28
170.245.174.0/23 No ROA Other IRR onlyTC 665 99% 66
168.194.179.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
170.245.172.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
170.245.174.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
170.245.173.0/24 Valid Other IRR onlyRADB, TC 665 99% 66
170.245.175.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
2804:8f18::/32 Valid Other IRR onlyRADB, TC 632 99% 69
2804:8f18::/33 Valid Other IRR onlyRADB 632 99% 69
2804:8f18:8000::/33 Valid Other IRR onlyRADB 632 99% 69
2804:8f18:c000::/34 Valid Other IRR onlyRADB 631 99% 69

AS-SET

AS273467's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:8f18:6800::/40ROA 2804:8f18::/32 AS273467 has maxLength 32; ROA 2804:8f18::/33 AS273467 has maxLength 33; the route is a /40. Raise the maxLength, or add a ROA for 2804:8f18:6800::/40.51 of 636
Route object: none2804:8f18:6800::/40No route object for it. A route object for 2804:8f18::/33 with origin AS273467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273467 in the RIR database for the space.51 of 636
ROA: none170.245.174.0/23No ROA covers it. Add a ROA for AS273467, maxLength 23.665 of 673
Route object: RIR170.245.174.0/23Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR168.194.179.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.245.172.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.245.174.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR170.245.173.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR170.245.175.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:8f18::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8f18::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8f18:8000::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8f18:c000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

170.245.172.0/22RADB, TCNo ROA
170.245.172.0/23TCNo 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.