bgpreport

Network · data from 2026-11-12

AS17264 CERNER-COM - Cerner Corporation

Registry name: CERNER-COM - Cerner Corporation, US · not in PeeringDB

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

Announced routes

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

159.140.4.0/23 No ROA None 673 100% 67
159.140.6.0/23 No ROA None 673 100% 67
159.140.142.0/23 No ROA None 673 100% 67
159.140.192.0/22 No ROA None 673 100% 67
159.140.192.0/23 No ROA None 673 100% 67
159.140.194.0/23 No ROA None 673 100% 67
159.140.198.0/24 No ROA None 673 100% 67
159.140.204.0/23 No ROA None 673 100% 67
159.140.204.0/24 No ROA None 673 100% 67
159.140.205.0/24 No ROA None 673 100% 67
159.140.206.0/23 No ROA None 673 100% 67
159.140.206.0/24 No ROA None 673 100% 67
159.140.207.0/24 No ROA None 673 100% 67
159.140.244.0/24 No ROA None 673 100% 67
198.203.228.0/23 No ROA None 673 100% 67

AS-SET

AS17264 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 30 are in fix.csv.

  • ROA: none15
  • Route object: none15
ChangePrefix or setDetailFull-table peers
ROA: none159.140.4.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.4.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.6.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.6.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.142.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.142.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.192.0/22No ROA covers it. Add a ROA for AS17264, maxLength 22.673 of 673
Route object: none159.140.192.0/22No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.192.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.192.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.194.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.194.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.198.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.198.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.204.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.204.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.204.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.204.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.205.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.205.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.206.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none159.140.206.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.206.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.206.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.207.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.207.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none159.140.244.0/24No ROA covers it. Add a ROA for AS17264, maxLength 24.673 of 673
Route object: none159.140.244.0/24No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673
ROA: none198.203.228.0/23No ROA covers it. Add a ROA for AS17264, maxLength 23.673 of 673
Route object: none198.203.228.0/23No route object for it. Add a route object with origin AS17264 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS17264 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.