Network · data from 2026-11-12
AS399272 BARNHOLDT-NA
Registry name: BARNHOLDT-NA - Barnholdt, LLC, US · PeeringDB
3IPv4 routes
100.0% RPKI valid · 100.0% with a route object
14IPv6 routes
100.0% RPKI valid · 14.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS399272, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS399272, 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.
| 2604:26a0:5005::/48 | Valid | Nonecovered by 2604:26a0::/32 | 636 100% |
| 2604:26a0:500c::/46 | Valid | Nonecovered by 2604:26a0::/32 | 636 100% |
| 2604:26a0:500c::/48 | Valid | Nonecovered by 2604:26a0::/32 | 636 100% |
| 2604:26a0:500d::/48 | Valid | Nonecovered by 2604:26a0::/32 | 636 100% |
| 2604:26a0:5000::/40 | Valid | Nonecovered by 2604:26a0::/32 | 635 100% |
| 2604:26a0:500a::/48 | Valid | Nonecovered by 2604:26a0::/32 | 635 100% |
| 2604:26a0:500f::/48 | Valid | Nonecovered by 2604:26a0::/32 | 635 100% |
| 2604:26a0:6100::/48 | Valid | Nonecovered by 2604:26a0::/32 | 634 100% |
| 2604:26a0:5007::/48 | Valid | Nonecovered by 2604:26a0::/32 | 633 100% |
| 2604:26a0:500e::/48 | Valid | Nonecovered by 2604:26a0::/32 | 633 100% |
| 2604:26a0:5002::/48 | Valid | Nonecovered by 2604:26a0::/32 | 632 99% |
| 2604:26a0:5003::/48 | Valid | Nonecovered by 2604:26a0::/32 | 632 99% |
| 2604:26a0:6000::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2604:26a0:6001::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 31.77.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 23.144.204.0/24 | Valid | RIR databaseARIN | 671 100% |
| 198.153.215.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
AS-SET
AS399272'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 19 are in fix.csv.
- Route object: none12
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2604:26a0:5005::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500c::/46 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500c::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500d::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:5000::/40 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500a::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500f::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:6100::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:5007::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:500e::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:5002::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: none | 2604:26a0:5003::/48 | No route object for it. A route object for 2604:26a0::/32 with origin AS399272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399272 in the RIR database for the space. |
| Route object: RIR | 2604:26a0:6000::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2604:26a0:6001::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399272 whose prefix no peer sees AS399272 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.42.123.0/24 | RIPE | Valid |
| 2602:81b:5000::/44 | RADB | No ROA |
| 2602:f4a8::/36 | ARIN | Invalid: origin |
| 2602:f4a8:40::/44 | ARIN | Valid |
| 2604:26a0::/32 | ARIN, RADB | Valid |
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.