bgpreport

Network · data from 2026-11-12

AS17099 CALLIS-COMMUNICATIONS-AS - Callis Communications

Registry name: CALLIS-COMMUNICATIONS-AS - Callis Communications, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17099, 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.
64.193.112.0/22 No ROA None 672 100% 67
208.66.60.0/22 No ROA None 672 100% 67
74.113.88.0/21 No ROA Other IRR onlyRADB 672 100% 67
162.210.116.0/22 No ROA Other IRR onlyRADB 672 100% 67
199.204.40.0/22 No ROA Other IRR onlyRADB 672 100% 67
204.114.12.0/22 No ROA Other IRR onlyRADB 672 100% 67
205.167.126.0/23 No ROA Other IRR onlyALTDB 672 100% 67
208.83.92.0/22 No ROA Other IRR onlyALTDB 672 100% 67

AS-SET

AS17099 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 17 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none64.193.112.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: none64.193.112.0/22No route object for it. Add a route object with origin AS17099 in the RIR database for the space.672 of 673
ROA: none208.66.60.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: none208.66.60.0/22No route object for it. Add a route object with origin AS17099 in the RIR database for the space.672 of 673
ROA: none74.113.88.0/21No ROA covers it. Add a ROA for AS17099, maxLength 21.672 of 673
Route object: RIR74.113.88.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none162.210.116.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: RIR162.210.116.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.204.40.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: RIR199.204.40.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none204.114.12.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: RIR204.114.12.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.167.126.0/23No ROA covers it. Add a ROA for AS17099, maxLength 23.672 of 673
Route object: RIR205.167.126.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none208.83.92.0/22No ROA covers it. Add a ROA for AS17099, maxLength 22.672 of 673
Route object: RIR208.83.92.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

204.128.222.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.