bgpreport

Network · data from 2026-11-12

AS15198 CCPI---SITE-1 - Convention Communications Provisioners, Inc.

Registry name: CCPI---SITE-1 - Convention Communications Provisioners, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15198, 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.
24.75.208.0/22 No ROA RIR databaseARIN 673 100% 67
24.52.44.0/22 Valid RIR databaseARIN 673 100% 67
24.75.232.0/23 Valid RIR databaseARIN 673 100% 67
24.75.238.0/23 Valid RIR databaseARIN 673 100% 67
208.115.94.0/23 Valid RIR databaseARIN 673 100% 67
24.75.234.0/24 Valid RIR databaseARIN 672 100% 67
24.75.235.0/24 Valid RIR databaseARIN 672 100% 67
24.75.236.0/24 Valid RIR databaseARIN 672 100% 67
24.75.237.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS15198 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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none24.75.208.0/22No ROA covers it. Add a ROA for AS15198, maxLength 22.673 of 673

Route objects not announced

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

67.217.25.0/24ARINNo ROA
2604:b180:200::/44ARINValid

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.