Network · data from 2026-11-12
AS29873 BIZLAND-SD - Newfold Digital, Inc.
Registry name: BIZLAND-SD - Newfold Digital, Inc., US · not in PeeringDB
32IPv4 routes
93.8% RPKI valid · 78.1% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
7 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
34Route objects not announced
registered with origin AS29873, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS29873, 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.113.1.0/24 | No ROA | Other IRR onlyALTDB | 671 100% |
| 38.113.20.0/24 | No ROA | Other IRR onlyALTDB | 671 100% |
| 209.59.208.0/22 | Valid | Nonecovered by 209.59.192.0/19 | 673 100% |
| 209.59.212.0/22 | Valid | Nonecovered by 209.59.192.0/19 | 673 100% |
| 209.59.216.0/21 | Valid | Nonecovered by 209.59.192.0/19 | 673 100% |
| 207.148.225.0/24 | Valid | Nonecovered by 207.148.224.0/19 | 672 100% |
| 65.254.250.0/24 | Valid | Nonecovered by 65.254.224.0/19 | 4 1%low visibility |
| 65.254.244.0/24 | Valid | Nonecovered by 65.254.224.0/19 | 2 0%low visibility |
| 207.148.248.0/24 | Valid | Nonecovered by 207.148.224.0/19 | 2 0%low visibility |
| 67.23.138.0/23 | Valid | Other IRR onlyALTDB | 673 100% |
| 72.22.88.0/22 | Valid | Other IRR onlyALTDB | 673 100% |
| 209.34.164.0/22 | Valid | Other IRR onlyALTDB | 673 100% |
| 209.59.192.0/20 | Valid | Other IRR onlyALTDB | 673 100% |
| 64.150.169.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 64.150.175.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 207.148.228.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 207.148.252.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 72.22.78.0/24 | Valid | Other IRR onlyALTDB | 671 100% |
| 72.22.94.0/24 | Valid | Other IRR onlyALTDB | 671 100% |
| 2605:f300:ffff::/48 | Valid | Other IRR onlyALTDB | 635 100% |
| 64.79.192.0/19 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 64.150.160.0/23 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 64.150.164.0/22 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 65.254.224.0/19 | Valid | RIR databaseALTDB, ARIN, RADB | 673 100% |
| 66.96.128.0/18 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 66.242.16.0/20 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 66.249.0.0/19 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 67.223.224.0/19 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 72.22.72.0/23 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 72.22.80.0/22 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 74.126.192.0/20 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 206.125.208.0/20 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 209.40.192.0/20 | Valid | RIR databaseALTDB, ARIN | 673 100% |
AS-SET
AS29873 isn't in PeeringDB, where networks name their 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 56 are in fix.csv.
- ROA: none2
- Route object: none7
- Route object: RIR13
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.113.1.0/24 | No ROA covers it. Add a ROA for AS29873, maxLength 24. |
| Route object: RIR | 38.113.1.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 38.113.20.0/24 | No ROA covers it. Add a ROA for AS29873, maxLength 24. |
| Route object: RIR | 38.113.20.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 209.59.208.0/22 | No route object for it. A route object for 209.59.192.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 209.59.212.0/22 | No route object for it. A route object for 209.59.192.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 209.59.216.0/21 | No route object for it. A route object for 209.59.192.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 207.148.225.0/24 | No route object for it. A route object for 207.148.224.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 65.254.250.0/24 | No route object for it. A route object for 65.254.224.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 65.254.244.0/24 | No route object for it. A route object for 65.254.224.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: none | 207.148.248.0/24 | No route object for it. A route object for 207.148.224.0/19 with origin AS29873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29873 in the RIR database for the space. |
| Route object: RIR | 67.23.138.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 72.22.88.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 209.34.164.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 209.59.192.0/20 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 64.150.169.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 64.150.175.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 207.148.228.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 207.148.252.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 72.22.78.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 72.22.94.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2605:f300:ffff::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29873 whose prefix no peer sees AS29873 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.150.162.0/24 | ALTDB | No ROA |
| 64.150.168.0/21 | ARIN | Valid |
| 64.150.168.0/24 | ALTDB | Valid |
| 64.150.170.0/23 | ALTDB | Valid |
| 64.150.172.0/23 | ALTDB | Valid |
| 64.150.174.0/24 | ALTDB | Valid |
| 65.254.254.0/24 | RADB | Valid |
| 66.11.224.0/21 | ALTDB | No ROA |
| 66.235.192.0/24 | ALTDB | No ROA |
| 66.235.196.0/22 | ARIN | Valid |
| 66.235.202.0/23 | ALTDB | No ROA |
| 66.235.216.0/21 | ALTDB | No ROA |
| 67.23.128.0/20 | ARIN | Valid |
| 72.22.69.0/24 | ARIN | Valid |
| 72.22.70.0/23 | ARIN | Valid |
| 72.22.75.0/24 | ARIN | Valid |
| 72.22.76.0/24 | ALTDB, ARIN | Valid |
| 72.22.78.0/23 | ARIN | Valid |
| 72.22.84.0/23 | ARIN | Valid |
| 72.22.88.0/21 | ARIN | Valid |
| 207.148.224.0/19 | ARIN, RADB | Valid |
| 207.148.224.0/24 | ALTDB | Valid |
| 207.148.226.0/24 | ALTDB | Valid |
| 207.148.230.0/23 | ALTDB | Valid |
| 207.148.232.0/21 | ALTDB | Valid |
| 207.148.240.0/21 | ALTDB | Valid |
| 207.148.250.0/23 | ALTDB | Valid |
| 207.148.254.0/23 | ALTDB | Valid |
| 209.34.160.0/19 | ARIN | Valid |
| 209.34.160.0/22 | ALTDB | Valid |
| 209.34.168.0/22 | ALTDB | Valid |
| 209.34.172.0/23 | ALTDB | Valid |
| 209.59.192.0/19 | ARIN | Valid |
| 2605:f300::/32 | ARIN | 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.