bgpreport

Network · data from 2026-11-12

AS272012 U ENERGY CORP

Registry name: AS272012 - U ENERGY CORP, S. A., GT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272012, 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.165.224.0/24 Valid Other IRR onlyRADB 670 100% 67
38.165.225.0/24 Valid Other IRR onlyRADB 670 100% 67
38.165.226.0/24 Valid Other IRR onlyRADB 670 100% 67
38.165.227.0/24 Valid Other IRR onlyRADB 670 100% 67
2803:3910:2000::/35 Valid Other IRR onlyRADB 636 100% 67
2803:3910:4000::/35 Valid Other IRR onlyRADB 636 100% 67
38.165.224.0/22 Valid RIR databaseARIN, RADB 671 100% 67
2803:3910::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS272012: AS-HURRICANEV6 AS-NWN-TRANSIT. 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 (AS272012 isn't in the set, or no route object for AS272012 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 objectsAS272012 in itNot covered
AS-HURRICANEV6 RADB 19,43611,981,191 No 8
AS-NWN-TRANSIT RADB 2,1941186,857 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 7 are in fix.csv.

  • Route object: RIR6
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: RIR38.165.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.165.225.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.165.226.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.165.227.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2803:3910:2000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:3910:4000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: own ASNAS-HURRICANEV6AS272012 isn't in AS-HURRICANEV6 (RADB) once expanded. Add AS272012 to it.

Route objects not announced

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