Network · data from 2026-11-12
AS46426 HART-COMMUNICATIONS - HART COMMUNICATIONS, INC.
Registry name: HART-COMMUNICATIONS - HART COMMUNICATIONS, INC., US · not in PeeringDB
16IPv4 routes
100.0% RPKI valid · 18.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
13 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS46426, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS46426, 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.
| 64.179.192.0/24 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 64.179.193.0/24 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 64.179.194.0/24 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 64.179.196.0/22 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 64.179.200.0/22 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 64.179.204.0/22 | Valid | Nonecovered by 64.179.192.0/20 | 671 100% |
| 69.168.33.0/24 | Valid | Nonecovered by 69.168.32.0/20 | 671 100% |
| 69.168.34.0/23 | Valid | Nonecovered by 69.168.32.0/20 | 671 100% |
| 69.168.36.0/24 | Valid | Nonecovered by 69.168.32.0/20 | 671 100% |
| 69.168.40.0/22 | Valid | Nonecovered by 69.168.32.0/20 | 671 100% |
| 69.168.44.0/22 | Valid | Nonecovered by 69.168.32.0/20 | 671 100% |
| 162.246.153.0/24 | Valid | Nonecovered by 162.246.152.0/22 | 671 100% |
| 162.246.154.0/24 | Valid | Nonecovered by 162.246.152.0/22 | 671 100% |
| 64.179.192.0/20 | Valid | RIR databaseARIN, BBOI | 671 100% |
| 69.168.32.0/20 | Valid | RIR databaseARIN, BBOI | 671 100% |
| 162.246.152.0/22 | Valid | RIR databaseARIN, BBOI | 671 100% |
AS-SET
AS46426 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 21 are in fix.csv.
- Route object: none13
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 64.179.192.0/24 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 64.179.193.0/24 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 64.179.194.0/24 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 64.179.196.0/22 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 64.179.200.0/22 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 64.179.204.0/22 | No route object for it. A route object for 64.179.192.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 69.168.33.0/24 | No route object for it. A route object for 69.168.32.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 69.168.34.0/23 | No route object for it. A route object for 69.168.32.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 69.168.36.0/24 | No route object for it. A route object for 69.168.32.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 69.168.40.0/22 | No route object for it. A route object for 69.168.32.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 69.168.44.0/22 | No route object for it. A route object for 69.168.32.0/20 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 162.246.153.0/24 | No route object for it. A route object for 162.246.152.0/22 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
| Route object: none | 162.246.154.0/24 | No route object for it. A route object for 162.246.152.0/22 with origin AS46426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46426 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46426 whose prefix no peer sees AS46426 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.103.36.0/24 | BBOI | No ROA |
| 65.244.158.0/24 | BBOI | No ROA |
| 65.247.253.0/24 | BBOI | No ROA |
| 173.245.234.0/24 | RADB | No ROA |
| 173.245.237.0/24 | RADB | No ROA |
| 2001:470:5bc::/48 | ARIN | Valid |
| 2606:c840::/32 | ARIN | Valid |
| 2606:c840::/36 | 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.