bgpreport

Network · data from 2026-11-12

AS264530 JPP PANCINI

Registry name: AS264530 - JPP PANCINI LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264530, 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.
138.0.36.0/24 No ROA Nonecovered by 138.0.36.0/22 668 99% 67
138.0.37.0/24 No ROA Nonecovered by 138.0.36.0/22 668 99% 67
138.0.38.0/24 No ROA Nonecovered by 138.0.36.0/22 668 99% 67
138.0.39.0/24 No ROA Nonecovered by 138.0.36.0/22 668 99% 67
138.0.36.0/22 No ROA Other IRR onlyRADB 668 99% 67
2804:2110::/32 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none138.0.36.0/24No ROA covers it. Add a ROA for AS264530, maxLength 24.668 of 673
Route object: none138.0.36.0/24No route object for it. A route object for 138.0.36.0/22 with origin AS264530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264530 in the RIR database for the space.668 of 673
ROA: none138.0.37.0/24No ROA covers it. Add a ROA for AS264530, maxLength 24.668 of 673
Route object: none138.0.37.0/24No route object for it. A route object for 138.0.36.0/22 with origin AS264530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264530 in the RIR database for the space.668 of 673
ROA: none138.0.38.0/24No ROA covers it. Add a ROA for AS264530, maxLength 24.668 of 673
Route object: none138.0.38.0/24No route object for it. A route object for 138.0.36.0/22 with origin AS264530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264530 in the RIR database for the space.668 of 673
ROA: none138.0.39.0/24No ROA covers it. Add a ROA for AS264530, maxLength 24.668 of 673
Route object: none138.0.39.0/24No route object for it. A route object for 138.0.36.0/22 with origin AS264530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264530 in the RIR database for the space.668 of 673
ROA: none138.0.36.0/22No ROA covers it. Add a ROA for AS264530, maxLength 22.668 of 673
Route object: RIR138.0.36.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:2110::/32No ROA covers it. Add a ROA for AS264530, maxLength 32.632 of 636
Route object: RIR2804:2110::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS264530 is announced.

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.