bgpreport

Network · data from 2026-11-12

AS268604 AS268604 - SILAS E F DE AQUINO ELETROELETRONICOS

Registry name: AS268604 - SILAS E F DE AQUINO ELETROELETRONICOS, BR · not in 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 AS268604, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268604, 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.164.24.0/24 No ROA Nonecovered by 45.164.24.0/22 669 99% 67
45.164.25.0/24 No ROA Nonecovered by 45.164.24.0/22 669 99% 67
45.164.26.0/24 No ROA Nonecovered by 45.164.24.0/22 669 99% 67
45.164.27.0/24 No ROA Nonecovered by 45.164.24.0/22 669 99% 67
45.164.24.0/22 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:53c0::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS268604 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: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.164.24.0/24No ROA covers it. Add a ROA for AS268604, maxLength 24.669 of 673
Route object: none45.164.24.0/24No route object for it. A route object for 45.164.24.0/22 with origin AS268604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268604 in the RIR database for the space.669 of 673
ROA: none45.164.25.0/24No ROA covers it. Add a ROA for AS268604, maxLength 24.669 of 673
Route object: none45.164.25.0/24No route object for it. A route object for 45.164.24.0/22 with origin AS268604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268604 in the RIR database for the space.669 of 673
ROA: none45.164.26.0/24No ROA covers it. Add a ROA for AS268604, maxLength 24.669 of 673
Route object: none45.164.26.0/24No route object for it. A route object for 45.164.24.0/22 with origin AS268604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268604 in the RIR database for the space.669 of 673
ROA: none45.164.27.0/24No ROA covers it. Add a ROA for AS268604, maxLength 24.669 of 673
Route object: none45.164.27.0/24No route object for it. A route object for 45.164.24.0/22 with origin AS268604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268604 in the RIR database for the space.669 of 673
ROA: none45.164.24.0/22No ROA covers it. Add a ROA for AS268604, maxLength 22.669 of 673
Route object: RIR45.164.24.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:53c0::/32No ROA covers it. Add a ROA for AS268604, maxLength 32.635 of 636
Route object: RIR2804:53c0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS268604 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.