bgpreport

Network · data from 2026-11-12

AS274022 274022

Registry name: AS274022 - SUCRENET, C.A., VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274022, 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.

2803:4cd0::/32 No ROA Other IRR onlyRADB 635 100% 67
38.247.6.0/23 Valid Nonecovered by 38.247.4.0/22 673 100% 67
38.247.4.0/23 Valid Nonecovered by 38.247.4.0/22 670 100% 67
38.247.4.0/22 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS274022'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 4 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2803:4cd0::/32No ROA covers it. Add a ROA for AS274022, maxLength 32.635 of 636
Route object: RIR2803:4cd0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none38.247.6.0/23No route object for it. A route object for 38.247.4.0/22 with origin AS274022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274022 in the RIR database for the space.673 of 673
Route object: none38.247.4.0/23No route object for it. A route object for 38.247.4.0/22 with origin AS274022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274022 in the RIR database for the space.670 of 673

Route objects not announced

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