Network · data from 2026-11-12
AS8444 HENDERSON JANUS HENDERSON ADMINISTRATION UK LIMITED
Registry name: HENDERSON JANUS HENDERSON ADMINISTRATION UK LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8444, 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.
| 144.2.128.0/24 | Valid | Nonecovered by 144.2.128.0/20 | 673 100% |
| 144.2.129.0/24 | Valid | Nonecovered by 144.2.128.0/20 | 673 100% |
| 144.2.143.0/24 | Valid | Nonecovered by 144.2.128.0/20 | 671 100% |
| 144.2.142.0/24 | Valid | Nonecovered by 144.2.128.0/20 | 670 100% |
| 144.2.136.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 144.2.140.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 144.2.130.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 144.2.131.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS8444 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 11 are in fix.csv.
- Route object: none4
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 144.2.128.0/24 | No route object for it. A route object for 144.2.128.0/20 with origin AS8444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8444 in the RIR database for the space. |
| Route object: none | 144.2.129.0/24 | No route object for it. A route object for 144.2.128.0/20 with origin AS8444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8444 in the RIR database for the space. |
| Route object: none | 144.2.143.0/24 | No route object for it. A route object for 144.2.128.0/20 with origin AS8444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8444 in the RIR database for the space. |
| Route object: none | 144.2.142.0/24 | No route object for it. A route object for 144.2.128.0/20 with origin AS8444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8444 in the RIR database for the space. |
| Route object: RIR | 144.2.136.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 144.2.140.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 144.2.130.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 144.2.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8444 whose prefix no peer sees AS8444 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 144.2.128.0/20 | RIPE | No ROA |
| 144.2.132.0/24 | RADB | No ROA |
| 144.2.133.0/24 | RADB | No ROA |
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.