bgpreport

Network · data from 2026-11-12

AS274117 SUPER-NET TELECOM

Registry name: AS274117 - SUPER-NET TELECOM C.A, VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274117, 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.
38.41.50.0/24 Valid Nonecovered by 38.41.48.0/22 671 100% 67
38.41.51.0/24 Valid Nonecovered by 38.41.48.0/22 671 100% 67
38.41.48.0/24 Valid Nonecovered by 38.41.48.0/22 667 99% 67
38.41.49.0/24 Valid Nonecovered by 38.41.48.0/22 667 99% 67
89.42.124.0/23 Valid RIR databaseRIPE 672 100% 67
89.42.124.0/24 Valid RIR databaseRIPE 672 100% 67
89.42.125.0/24 Valid RIR databaseRIPE 669 99% 67
38.41.48.0/22 Valid RIR databaseARIN, RADB 668 99% 67
2803:5ed0::/32 Valid RIR databaseLACNIC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS274117: AS274117:AS-CONE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS274117 isn't in the set, or no route object for AS274117 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS274117 in itNot covered
AS274117:AS-CONE RADB 010 No 9
LACNIC (also) 115 Yes 0

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

  • Route object: none4
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none38.41.50.0/24No route object for it. A route object for 38.41.48.0/22 with origin AS274117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274117 in the RIR database for the space.671 of 673
Route object: none38.41.51.0/24No route object for it. A route object for 38.41.48.0/22 with origin AS274117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274117 in the RIR database for the space.671 of 673
Route object: none38.41.48.0/24No route object for it. A route object for 38.41.48.0/22 with origin AS274117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274117 in the RIR database for the space.667 of 673
Route object: none38.41.49.0/24No route object for it. A route object for 38.41.48.0/22 with origin AS274117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274117 in the RIR database for the space.667 of 673
AS-SET: own ASNAS274117:AS-CONEAS274117 isn't in AS274117:AS-CONE (RADB) once expanded. Add AS274117 to it.

Route objects not announced

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