Network · data from 2026-11-12
AS14379 N-T-C - The Northern Trust Company
Registry name: N-T-C - The Northern Trust Company, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14379, 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.
| 208.95.148.0/23 | No ROA | Nonecovered by 208.95.144.0/21 | 672 100% |
| 208.95.150.0/23 | No ROA | Nonecovered by 208.95.144.0/21 | 672 100% |
| 208.95.144.0/22 | No ROA | Nonecovered by 208.95.144.0/21 | 655 97% |
| 199.16.200.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.16.204.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.16.206.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 12.148.180.0/22 | No ROA | Other IRR onlyRADB | 648 96% |
| 208.95.144.0/21 | No ROA | Other IRR onlyRADB | 558 83% |
AS-SET
AS14379 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 20 are in fix.csv.
- ROA: none8
- Route object: none3
- Route object: RIR5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 208.95.148.0/23 | No ROA covers it. Add a ROA for AS14379, maxLength 23. |
| Route object: none | 208.95.148.0/23 | No route object for it. A route object for 208.95.144.0/21 with origin AS14379 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14379 in the RIR database for the space. |
| ROA: none | 208.95.150.0/23 | No ROA covers it. Add a ROA for AS14379, maxLength 23. |
| Route object: none | 208.95.150.0/23 | No route object for it. A route object for 208.95.144.0/21 with origin AS14379 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14379 in the RIR database for the space. |
| ROA: none | 208.95.144.0/22 | No ROA covers it. Add a ROA for AS14379, maxLength 22. |
| Route object: none | 208.95.144.0/22 | No route object for it. A route object for 208.95.144.0/21 with origin AS14379 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14379 in the RIR database for the space. |
| ROA: none | 199.16.200.0/22 | No ROA covers it. Add a ROA for AS14379, maxLength 22. |
| Route object: RIR | 199.16.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.16.204.0/23 | No ROA covers it. Add a ROA for AS14379, maxLength 23. |
| Route object: RIR | 199.16.204.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.16.206.0/23 | No ROA covers it. Add a ROA for AS14379, maxLength 23. |
| Route object: RIR | 199.16.206.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 12.148.180.0/22 | No ROA covers it. Add a ROA for AS14379, maxLength 22. |
| Route object: RIR | 12.148.180.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.95.144.0/21 | No ROA covers it. Add a ROA for AS14379, maxLength 21. |
| Route object: RIR | 208.95.144.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14379 whose prefix no peer sees AS14379 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.16.200.0/21 | RADB | No ROA |
| 199.16.200.0/23 | RADB | No ROA |
| 199.16.202.0/23 | RADB | No ROA |
| 199.16.204.0/22 | 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.