bgpreport

Network · data from 2026-11-12

AS274243 AS274243 - EVOLUTIONNET SAN NICOLAS S. A.

Registry name: AS274243 - EVOLUTIONNET SAN NICOLAS S. A., AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274243, 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.
209.61.4.0/24 Invalid: maxLength Nonecovered by 209.61.4.0/22 1 0%low visibility 2
209.61.5.0/24 Invalid: maxLength Nonecovered by 209.61.4.0/22 1 0%low visibility 2
209.61.7.0/24 Invalid: maxLength Nonecovered by 209.61.4.0/22 1 0%low visibility 2
209.61.4.0/23 Valid Nonecovered by 209.61.4.0/22 670 100% 67
209.61.6.0/23 Valid Nonecovered by 209.61.4.0/22 670 100% 67
209.61.4.0/22 Valid RIR databaseARIN 670 100% 67
2803:d7d0::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS274243 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 8 are in fix.csv.

  • ROA: maxLength3
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: maxLength209.61.4.0/24ROA 209.61.4.0/22 AS274243 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 209.61.4.0/24.1 of 673
Route object: none209.61.4.0/24No route object for it. A route object for 209.61.4.0/22 with origin AS274243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274243 in the RIR database for the space.1 of 673
ROA: maxLength209.61.5.0/24ROA 209.61.4.0/22 AS274243 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 209.61.5.0/24.1 of 673
Route object: none209.61.5.0/24No route object for it. A route object for 209.61.4.0/22 with origin AS274243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274243 in the RIR database for the space.1 of 673
ROA: maxLength209.61.7.0/24ROA 209.61.4.0/22 AS274243 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 209.61.7.0/24.1 of 673
Route object: none209.61.7.0/24No route object for it. A route object for 209.61.4.0/22 with origin AS274243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274243 in the RIR database for the space.1 of 673
Route object: none209.61.4.0/23No route object for it. A route object for 209.61.4.0/22 with origin AS274243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274243 in the RIR database for the space.670 of 673
Route object: none209.61.6.0/23No route object for it. A route object for 209.61.4.0/22 with origin AS274243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274243 in the RIR database for the space.670 of 673

Route objects not announced

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