bgpreport

Network · data from 2026-11-12

AS6623 CBS Interactive

Registry name: CBSI-1 - CBS Interactive Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6623, 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.
62.108.128.0/24 No ROA RIR databaseRIPE 673 100% 67
62.108.129.0/24 No ROA RIR databaseRIPE 673 100% 67
64.30.224.0/20 No ROA RIR databaseARIN 673 100% 67
64.30.224.0/22 No ROA RIR databaseARIN 673 100% 67
64.30.228.0/22 No ROA RIR databaseARIN 673 100% 67
64.30.232.0/24 No ROA RIR databaseARIN 673 100% 67
216.239.112.0/20 No ROA RIR databaseARIN 673 100% 67
216.239.116.0/22 No ROA RIR databaseARIN 673 100% 67
2620:110:5000::/44 No ROA RIR databaseARIN, RADB 635 100% 67
2620:110:5003::/48 No ROA RIR databaseARIN 635 100% 67
2620:110:5004::/48 No ROA RIR databaseARIN 635 100% 67
64.30.231.0/24 No ROA RIR databaseARIN, RADB 2 0%low visibility 2
2620:110:5002::/48 No ROA RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS6623'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 15 are in fix.csv.

  • ROA: none13
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none62.108.128.0/24No ROA covers it. Add a ROA for AS6623, maxLength 24.673 of 673
ROA: none62.108.129.0/24No ROA covers it. Add a ROA for AS6623, maxLength 24.673 of 673
ROA: none64.30.224.0/20No ROA covers it. Add a ROA for AS6623, maxLength 20.673 of 673
ROA: none64.30.224.0/22No ROA covers it. Add a ROA for AS6623, maxLength 22.673 of 673
ROA: none64.30.228.0/22No ROA covers it. Add a ROA for AS6623, maxLength 22.673 of 673
ROA: none64.30.232.0/24No ROA covers it. Add a ROA for AS6623, maxLength 24.673 of 673
ROA: none216.239.112.0/20No ROA covers it. Add a ROA for AS6623, maxLength 20.673 of 673
ROA: none216.239.116.0/22No ROA covers it. Add a ROA for AS6623, maxLength 22.673 of 673
ROA: none2620:110:5000::/44No ROA covers it. Add a ROA for AS6623, maxLength 44.635 of 636
ROA: none2620:110:5003::/48No ROA covers it. Add a ROA for AS6623, maxLength 48.635 of 636
ROA: none2620:110:5004::/48No ROA covers it. Add a ROA for AS6623, maxLength 48.635 of 636
ROA: none64.30.231.0/24No ROA covers it. Add a ROA for AS6623, maxLength 24.2 of 673
ROA: none2620:110:5002::/48No ROA covers it. Add a ROA for AS6623, maxLength 48.2 of 636

Route objects not announced

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

216.239.124.0/24ARINNo ROA
2620:110:5001::/48ARINNo 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.