bgpreport

Network · data from 2026-11-12

AS17056 CIPHERSPACE - CipherSpace, LLC

Registry name: CIPHERSPACE - CipherSpace, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17056, 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.

5.1.113.0/24 No ROA Nonecovered by 5.1.112.0/21 673 100% 67
5.1.114.0/24 No ROA Nonecovered by 5.1.112.0/21 673 100% 67
5.1.119.0/24 No ROA Nonecovered by 5.1.112.0/21 673 100% 67
63.116.75.0/24 No ROA Nonecovered by 63.116.72.0/22 673 100% 67
63.85.78.0/24 No ROA Other IRR onlyRADB 673 100% 67
2604:a300::/32 No ROA Other IRR onlyRADB 605 95% 67
74.115.112.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
74.115.114.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
74.115.116.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
74.115.117.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
74.115.118.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
74.115.119.0/24 Valid Nonecovered by 74.115.112.0/21 672 100% 67
199.168.224.0/22 Valid Other IRR onlyRADB 673 100% 67
74.115.112.0/21 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS17056 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 24 are in fix.csv.

  • ROA: none6
  • Route object: none10
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none5.1.113.0/24No ROA covers it. Add a ROA for AS17056, maxLength 24.673 of 673
Route object: none5.1.113.0/24No route object for it. A route object for 5.1.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.673 of 673
ROA: none5.1.114.0/24No ROA covers it. Add a ROA for AS17056, maxLength 24.673 of 673
Route object: none5.1.114.0/24No route object for it. A route object for 5.1.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.673 of 673
ROA: none5.1.119.0/24No ROA covers it. Add a ROA for AS17056, maxLength 24.673 of 673
Route object: none5.1.119.0/24No route object for it. A route object for 5.1.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.673 of 673
ROA: none63.116.75.0/24No ROA covers it. Add a ROA for AS17056, maxLength 24.673 of 673
Route object: none63.116.75.0/24No route object for it. A route object for 63.116.72.0/22 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.673 of 673
ROA: none63.85.78.0/24No ROA covers it. Add a ROA for AS17056, maxLength 24.673 of 673
Route object: RIR63.85.78.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2604:a300::/32No ROA covers it. Add a ROA for AS17056, maxLength 32.605 of 636
Route object: RIR2604:a300::/32Route object only in RADB. Add it in the RIR database for the space.605 of 636
Route object: none74.115.112.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: none74.115.114.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: none74.115.116.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: none74.115.117.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: none74.115.118.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: none74.115.119.0/24No route object for it. A route object for 74.115.112.0/21 with origin AS17056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17056 in the RIR database for the space.672 of 673
Route object: RIR199.168.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.115.112.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

5.1.112.0/21RADB, RIPENo ROA
63.116.72.0/22RADBNo ROA
65.200.169.0/24RADBNo ROA
185.148.136.0/22RADB, RIPENo 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.