bgpreport

Network · data from 2026-11-12

AS6102 CBS

Registry name: CBSCORPORATE - CBS inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6102, 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.
129.228.128.0/17 No ROA Other IRR onlyRADB 673 100% 67
129.228.128.0/18 No ROA Other IRR onlyRADB 673 100% 67
170.20.0.0/17 No ROA Other IRR onlyRADB 673 100% 67
170.20.0.0/18 No ROA Other IRR onlyRADB 673 100% 67
170.20.128.0/17 No ROA Other IRR onlyRADB 673 100% 67
192.238.64.0/19 No ROA Other IRR onlyRADB 673 100% 67
192.238.96.0/19 No ROA Other IRR onlyRADB 673 100% 67
129.228.192.0/18 No ROA Other IRR onlyRADB 672 100% 67
170.20.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
170.20.96.0/19 No ROA Other IRR onlyRADB 672 100% 67
170.20.128.0/20 No ROA Other IRR onlyRADB 672 100% 67
192.238.64.0/18 No ROA Other IRR onlyRADB 672 100% 67
192.238.112.0/20 No ROA Other IRR onlyRADB 672 100% 67
198.99.118.0/23 No ROA Other IRR onlyRADB 672 100% 67
198.99.120.0/23 No ROA Other IRR onlyRADB 672 100% 67
198.99.122.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS6102's PeeringDB record names no 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 44 are in fix.csv.

  • ROA: none16
  • Route object: RIR16
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none129.228.128.0/17No ROA covers it. Add a ROA for AS6102, maxLength 17.673 of 673
Route object: RIR129.228.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.228.128.0/18No ROA covers it. Add a ROA for AS6102, maxLength 18.673 of 673
Route object: RIR129.228.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.20.0.0/17No ROA covers it. Add a ROA for AS6102, maxLength 17.673 of 673
Route object: RIR170.20.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.20.0.0/18No ROA covers it. Add a ROA for AS6102, maxLength 18.673 of 673
Route object: RIR170.20.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.20.128.0/17No ROA covers it. Add a ROA for AS6102, maxLength 17.673 of 673
Route object: RIR170.20.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.238.64.0/19No ROA covers it. Add a ROA for AS6102, maxLength 19.673 of 673
Route object: RIR192.238.64.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.238.96.0/19No ROA covers it. Add a ROA for AS6102, maxLength 19.673 of 673
Route object: RIR192.238.96.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.228.192.0/18No ROA covers it. Add a ROA for AS6102, maxLength 18.672 of 673
Route object: RIR129.228.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none170.20.0.0/16No ROA covers it. Add a ROA for AS6102, maxLength 16.672 of 673
Route object: RIR170.20.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none170.20.96.0/19No ROA covers it. Add a ROA for AS6102, maxLength 19.672 of 673
Route object: RIR170.20.96.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none170.20.128.0/20No ROA covers it. Add a ROA for AS6102, maxLength 20.672 of 673
Route object: RIR170.20.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.238.64.0/18No ROA covers it. Add a ROA for AS6102, maxLength 18.672 of 673
Route object: RIR192.238.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.238.112.0/20No ROA covers it. Add a ROA for AS6102, maxLength 20.672 of 673
Route object: RIR192.238.112.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.99.118.0/23No ROA covers it. Add a ROA for AS6102, maxLength 23.672 of 673
Route object: RIR198.99.118.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.99.120.0/23No ROA covers it. Add a ROA for AS6102, maxLength 23.672 of 673
Route object: RIR198.99.120.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.99.122.0/24No ROA covers it. Add a ROA for AS6102, maxLength 24.672 of 673
Route object: RIR198.99.122.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS6102 whose prefix no peer sees AS6102 announce. Many are kept on purpose (backup routes, space announced only in some places).

8.33.201.0/24RADBNo ROA
8.34.48.0/24RADBNo ROA
64.30.224.0/20RADBNo ROA
170.20.0.0/24RADBNo ROA
170.20.11.0/24RADBNo ROA
170.20.12.0/24RADBNo ROA
170.20.64.0/19RADBNo ROA
170.20.134.0/24RADBNo ROA
170.20.144.0/20RADBNo ROA
170.20.160.0/19RADBNo ROA
170.20.192.0/18RADBNo ROA
192.238.124.0/22RADBNo 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.