bgpreport

Network · data from 2026-11-12

AS17140 CBRE-US - CBRE, INC.

Registry name: CBRE-US - CBRE, INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17140, 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.68.244.0/22 No ROA None 673 100% 67
208.68.244.0/24 No ROA Nonecovered by 208.68.244.0/23 672 100% 67
208.68.245.0/24 No ROA Nonecovered by 208.68.244.0/23 672 100% 67
192.34.68.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.34.69.0/24 No ROA Other IRR onlyRADB 673 100% 67
208.68.244.0/23 No ROA Other IRR onlyRADB 673 100% 67
208.68.246.0/23 No ROA Other IRR onlyRADB 672 100% 67
194.35.3.0/24 Valid RIR databaseRIPE 673 100% 67
194.35.7.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS17140 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none208.68.244.0/22No ROA covers it. Add a ROA for AS17140, maxLength 22.673 of 673
Route object: none208.68.244.0/22No route object for it. Add a route object with origin AS17140 in the RIR database for the space.673 of 673
ROA: none208.68.244.0/24No ROA covers it. Add a ROA for AS17140, maxLength 24.672 of 673
Route object: none208.68.244.0/24No route object for it. A route object for 208.68.244.0/23 with origin AS17140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17140 in the RIR database for the space.672 of 673
ROA: none208.68.245.0/24No ROA covers it. Add a ROA for AS17140, maxLength 24.672 of 673
Route object: none208.68.245.0/24No route object for it. A route object for 208.68.244.0/23 with origin AS17140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17140 in the RIR database for the space.672 of 673
ROA: none192.34.68.0/24No ROA covers it. Add a ROA for AS17140, maxLength 24.673 of 673
Route object: RIR192.34.68.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.34.69.0/24No ROA covers it. Add a ROA for AS17140, maxLength 24.673 of 673
Route object: RIR192.34.69.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.68.244.0/23No ROA covers it. Add a ROA for AS17140, maxLength 23.673 of 673
Route object: RIR208.68.244.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.68.246.0/23No ROA covers it. Add a ROA for AS17140, maxLength 23.672 of 673
Route object: RIR208.68.246.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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