bgpreport

Network · data from 2026-11-12

AS269437 AS269437 - PRADO TELECOM E SISTEMAS DE SEGURANCA ELETRONICA

Registry name: AS269437 - PRADO TELECOM E SISTEMAS DE SEGURANCA ELETRONICA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269437, 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.186.221.0/24 No ROA Other IRR onlyRADB 672 100% 67
170.0.184.0/22 No ROA Other IRR onlyTC 669 99% 67
45.186.220.0/22 No ROA Other IRR onlyALTDB, RADB, TC 668 99% 67
2804:6498:7000::/36 No ROA Other IRR onlyRADB 636 100% 67
2804:6498::/32 No ROA Other IRR onlyALTDB, TC 634 100% 67

AS-SET

AS269437 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 44 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none45.186.221.0/24No ROA covers it. Add a ROA for AS269437, maxLength 24.672 of 673
Route object: RIR45.186.221.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none170.0.184.0/22No ROA covers it. Add a ROA for AS269437, maxLength 22.669 of 673
Route object: RIR170.0.184.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none45.186.220.0/22No ROA covers it. Add a ROA for AS269437, maxLength 22.668 of 673
Route object: RIR45.186.220.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:6498:7000::/36No ROA covers it. Add a ROA for AS269437, maxLength 36.636 of 636
Route object: RIR2804:6498:7000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:6498::/32No ROA covers it. Add a ROA for AS269437, maxLength 32.634 of 636
Route object: RIR2804:6498::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.186.220.0/23RADBNo ROA
45.186.220.0/24RADBNo ROA
45.186.222.0/23RADBNo ROA
45.186.222.0/24RADBNo ROA
45.186.223.0/24RADBNo ROA
2804:6498::/33RADBNo ROA
2804:6498::/34RADBNo ROA
2804:6498::/35RADBNo ROA
2804:6498::/36RADBNo ROA
2804:6498:1000::/36RADBNo ROA
2804:6498:2000::/35RADBNo ROA
2804:6498:2000::/36RADBNo ROA
2804:6498:3000::/36RADBNo ROA
2804:6498:4000::/34RADBNo ROA
2804:6498:4000::/35RADBNo ROA
2804:6498:4000::/36RADBNo ROA
2804:6498:5000::/36RADBNo ROA
2804:6498:6000::/35RADBNo ROA
2804:6498:6000::/36RADBNo ROA
2804:6498:8000::/33RADBNo ROA
2804:6498:8000::/34RADBNo ROA
2804:6498:8000::/35RADBNo ROA
2804:6498:8000::/36RADBNo ROA
2804:6498:9000::/36RADBNo ROA
2804:6498:a000::/35RADBNo ROA
2804:6498:a000::/36RADBNo ROA
2804:6498:b000::/36RADBNo ROA
2804:6498:c000::/34RADBNo ROA
2804:6498:c000::/35RADBNo ROA
2804:6498:c000::/36RADBNo ROA
2804:6498:d000::/36RADBNo ROA
2804:6498:e000::/35RADBNo ROA
2804:6498:e000::/36RADBNo ROA
2804:6498: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.