bgpreport

Network · data from 2026-11-12

AS262149 Sistemas Fratec S.A.

Registry name: AS262149 - Sistemas Fratec S.A., CR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262149, 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.
170.83.8.0/24 Valid Nonecovered by 170.83.8.0/23 672 100% 68
170.83.9.0/24 Valid Nonecovered by 170.83.8.0/23 672 100% 68
200.59.20.0/24 Valid Nonecovered by 200.59.20.0/23 669 99% 68
200.59.22.0/24 Valid Nonecovered by 200.59.22.0/23 669 99% 68
200.59.23.0/24 Valid Nonecovered by 200.59.22.0/23 669 99% 68
200.59.21.0/24 Valid Nonecovered by 200.59.20.0/23 662 98% 68
170.83.8.0/23 Valid RIR databaseLACNIC 663 99% 68
200.59.16.0/23 Valid RIR databaseLACNIC 662 98% 68
200.59.18.0/23 Valid RIR databaseLACNIC 662 98% 68
2800:640::/32 Valid RIR databaseLACNIC 631 99% 68

AS-SET

AS262149'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 10 are in fix.csv.

  • Route object: none6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none170.83.8.0/24No route object for it. A route object for 170.83.8.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.672 of 673
Route object: none170.83.9.0/24No route object for it. A route object for 170.83.8.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.672 of 673
Route object: none200.59.20.0/24No route object for it. A route object for 200.59.20.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.669 of 673
Route object: none200.59.22.0/24No route object for it. A route object for 200.59.22.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.669 of 673
Route object: none200.59.23.0/24No route object for it. A route object for 200.59.22.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.669 of 673
Route object: none200.59.21.0/24No route object for it. A route object for 200.59.20.0/23 with origin AS262149 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262149 in the RIR database for the space.662 of 673

Route objects not announced

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

170.83.8.0/22RADBNo ROA
200.59.16.0/21RADBNo ROA
200.59.20.0/23LACNICValid
200.59.22.0/23LACNICValid

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.