bgpreport

Network · data from 2026-11-12

AS269371 AS269371 - J Z A Comunicacoes LTDA

Registry name: AS269371 - J Z A Comunicacoes LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269371, 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.
45.185.80.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:6398::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS269371 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 40 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none45.185.80.0/22No ROA covers it. Add a ROA for AS269371, maxLength 22.671 of 673
Route object: RIR45.185.80.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:6398::/32No ROA covers it. Add a ROA for AS269371, maxLength 32.635 of 636
Route object: RIR2804:6398::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.185.80.0/23RADBNo ROA
45.185.80.0/24RADBNo ROA
45.185.81.0/24RADBNo ROA
45.185.82.0/23RADBNo ROA
45.185.82.0/24RADBNo ROA
45.185.83.0/24RADBNo ROA
2804:6398::/33RADBNo ROA
2804:6398::/34RADBNo ROA
2804:6398::/35RADBNo ROA
2804:6398::/36RADBNo ROA
2804:6398:1000::/36RADBNo ROA
2804:6398:2000::/35RADBNo ROA
2804:6398:2000::/36RADBNo ROA
2804:6398:3000::/36RADBNo ROA
2804:6398:4000::/34RADBNo ROA
2804:6398:4000::/35RADBNo ROA
2804:6398:4000::/36RADBNo ROA
2804:6398:5000::/36RADBNo ROA
2804:6398:6000::/35RADBNo ROA
2804:6398:6000::/36RADBNo ROA
2804:6398:7000::/36RADBNo ROA
2804:6398:8000::/33RADBNo ROA
2804:6398:8000::/34RADBNo ROA
2804:6398:8000::/35RADBNo ROA
2804:6398:8000::/36RADBNo ROA
2804:6398:9000::/36RADBNo ROA
2804:6398:a000::/35RADBNo ROA
2804:6398:a000::/36RADBNo ROA
2804:6398:b000::/36RADBNo ROA
2804:6398:c000::/34RADBNo ROA
2804:6398:c000::/35RADBNo ROA
2804:6398:c000::/36RADBNo ROA
2804:6398:d000::/36RADBNo ROA
2804:6398:e000::/35RADBNo ROA
2804:6398:e000::/36RADBNo ROA
2804:6398:f000::/36RADBNo 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.