bgpreport

Network · data from 2026-11-12

AS19299 NPC-P1 - The Northern Trust Company

Registry name: NPC-P1 - The Northern Trust Company, US · not in PeeringDB

12IPv4 routes 0.0% RPKI valid · 41.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
12No ROA 7 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS19299, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS19299, 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.

12.148.180.0/23 No ROA Nonecovered by 12.148.180.0/22 672 100% 67
12.148.182.0/23 No ROA Nonecovered by 12.148.180.0/22 672 100% 67
199.16.202.0/23 No ROA Other origin onlycovered by 199.16.200.0/21 672 100% 67
208.95.144.0/23 No ROA Nonecovered by 208.95.144.0/21 672 100% 67
208.95.146.0/23 No ROA Nonecovered by 208.95.144.0/21 672 100% 67
208.95.148.0/22 No ROA Nonecovered by 208.95.144.0/21 672 100% 67
208.95.144.0/22 No ROA Nonecovered by 208.95.144.0/21 17 3%low visibility 7
199.16.200.0/21 No ROA Other IRR onlyRADB 672 100% 67
199.16.200.0/23 No ROA Other IRR onlyRADB 672 100% 67
199.16.204.0/22 No ROA Other IRR onlyRADB 672 100% 67
208.95.144.0/21 No ROA Other IRR onlyRADB 115 17% 40
12.148.180.0/22 No ROA Other IRR onlyRADB 24 4%low visibility 11

AS-SET

AS19299 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 24 are in fix.csv.

  • ROA: none12
  • Route object: none7
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none12.148.180.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: none12.148.180.0/23No route object for it. A route object for 12.148.180.0/22 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none12.148.182.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: none12.148.182.0/23No route object for it. A route object for 12.148.180.0/22 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none199.16.202.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: none199.16.202.0/23Route objects for it name AS14379. A route object for 199.16.200.0/21 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none208.95.144.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: none208.95.144.0/23No route object for it. A route object for 208.95.144.0/21 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none208.95.146.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: none208.95.146.0/23No route object for it. A route object for 208.95.144.0/21 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none208.95.148.0/22No ROA covers it. Add a ROA for AS19299, maxLength 22.672 of 673
Route object: none208.95.148.0/22No route object for it. A route object for 208.95.144.0/21 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.672 of 673
ROA: none208.95.144.0/22No ROA covers it. Add a ROA for AS19299, maxLength 22.17 of 673
Route object: none208.95.144.0/22No route object for it. A route object for 208.95.144.0/21 with origin AS19299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19299 in the RIR database for the space.17 of 673
ROA: none199.16.200.0/21No ROA covers it. Add a ROA for AS19299, maxLength 21.672 of 673
Route object: RIR199.16.200.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.16.200.0/23No ROA covers it. Add a ROA for AS19299, maxLength 23.672 of 673
Route object: RIR199.16.200.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.16.204.0/22No ROA covers it. Add a ROA for AS19299, maxLength 22.672 of 673
Route object: RIR199.16.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.95.144.0/21No ROA covers it. Add a ROA for AS19299, maxLength 21.115 of 673
Route object: RIR208.95.144.0/21Route object only in RADB. Add it in the RIR database for the space.115 of 673
ROA: none12.148.180.0/22No ROA covers it. Add a ROA for AS19299, maxLength 22.24 of 673
Route object: RIR12.148.180.0/22Route object only in RADB. Add it in the RIR database for the space.24 of 673

Route objects not announced

Every route object with origin AS19299 is announced.

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.