bgpreport

Network · data from 2026-11-12

AS38439 zfs.rent

Registry name: ZFSRENT-38439 - ZFS.RENT LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38439, 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.
2602:f831:d0::/48 Valid Nonecovered by 2602:f831:d0::/44 632 99% 69
2602:f831:d1::/48 Valid Nonecovered by 2602:f831:d0::/44 632 99% 69
2602:f831:d2::/48 Valid Nonecovered by 2602:f831:d0::/44 632 99% 69
2602:f831:d3::/48 Valid Nonecovered by 2602:f831:d0::/44 632 99% 69
199.127.129.0/24 Valid RIR databaseARIN 670 100% 68
2001:470:d0::/48 Valid RIR databaseARIN 632 99% 69
2001:470:40a::/48 Valid RIR databaseARIN 632 99% 69
2602:f831::/48 Valid RIR databaseARIN 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS38439: AS-ZFSRENT. 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 (AS38439 isn't in the set, or no route object for AS38439 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 objectsAS38439 in itNot covered
AS-ZFSRENT ARIN 2316 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
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2602:f831:d0::/48No route object for it. A route object for 2602:f831:d0::/44 with origin AS38439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38439 in the RIR database for the space.632 of 636
Route object: none2602:f831:d1::/48No route object for it. A route object for 2602:f831:d0::/44 with origin AS38439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38439 in the RIR database for the space.632 of 636
Route object: none2602:f831:d2::/48No route object for it. A route object for 2602:f831:d0::/44 with origin AS38439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38439 in the RIR database for the space.632 of 636
Route object: none2602:f831:d3::/48No route object for it. A route object for 2602:f831:d0::/44 with origin AS38439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38439 in the RIR database for the space.632 of 636

Route objects not announced

Route objects with origin AS38439 whose prefix no peer sees AS38439 announce. Many are kept on purpose (backup routes, space announced only in some places).

2602:f831:d0::/44ARINValid

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.