bgpreport

Network · data from 2026-11-12

AS22243 CentraComm Communications

Registry name: CENTRACOMM - CentraComm Communications, US · PeeringDB

1IPv4 routes 0.0% 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
19Route objects not announced registered with origin AS22243, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22243, 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.
209.11.224.0/20 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS22243'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 21 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none209.11.224.0/20No ROA covers it. Add a ROA for AS22243, maxLength 20.672 of 673
Route object: RIR209.11.224.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

12.109.103.0/24RADBNo ROA
12.111.246.0/24RADBNo ROA
12.111.247.0/24RADBNo ROA
12.111.248.0/24RADBNo ROA
12.111.249.0/24RADBNo ROA
12.111.250.0/24RADBNo ROA
12.111.251.0/24RADBNo ROA
12.111.252.0/24RADBNo ROA
12.111.253.0/24RADBNo ROA
12.111.254.0/24RADBNo ROA
12.111.255.0/24RADBNo ROA
12.148.88.0/21RADBNo ROA
63.163.18.0/24RADBNo ROA
65.114.127.0/24RADBNo ROA
208.76.20.0/23RADBNo ROA
208.76.20.0/24RADBNo ROA
208.76.21.0/24RADBNo ROA
208.76.22.0/24RADBNo ROA
208.76.23.0/24RADBNo 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.