bgpreport

Network · data from 2026-11-12

AS399291 FiberNetPR

Registry name: PRFIBERNET - Puerto Rico Fiber Network Inc, PR · PeeringDB

5IPv4 routes 40.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS399291, seen from no peer

Announced routes

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

154.64.217.0/24 No ROA Other IRR onlyRADB 667 99% 68
23.134.164.0/24 No ROA RIR databaseARIN 671 100% 68
38.226.32.0/21 No ROA RIR databaseARIN, RADB 667 99% 68
2607:efc0::/32 No ROA RIR databaseARIN 635 100% 69
104.238.192.0/24 Valid RIR databaseARIN, RADB 667 99% 68
200.5.31.0/24 Valid RIR databaseARIN, RADB 667 99% 68

AS-SET

PeeringDB's irr_as_set for AS399291: AS399291:AS-CUSTOMERS. 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 (AS399291 isn't in the set, or no route object for AS399291 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 objectsAS399291 in itNot covered
AS399291:AS-CUSTOMERS RADB 3111 Yes 0
ARIN (also) 217 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.

  • ROA: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none154.64.217.0/24No ROA covers it. Add a ROA for AS399291, maxLength 24.667 of 673
Route object: RIR154.64.217.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none23.134.164.0/24No ROA covers it. Add a ROA for AS399291, maxLength 24.671 of 673
ROA: none38.226.32.0/21No ROA covers it. Add a ROA for AS399291, maxLength 21.667 of 673
ROA: none2607:efc0::/32No ROA covers it. Add a ROA for AS399291, maxLength 32.635 of 636

Route objects not announced

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