bgpreport

Network · data from 2026-11-12

AS5716 CYBERCOM - Cyber Access Internet Communications, Inc.

Registry name: CYBERCOM - Cyber Access Internet Communications, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5716, 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.46.128.0/21 No ROA None 673 100% 67
64.46.136.0/22 No ROA None 673 100% 67
64.46.141.0/24 No ROA None 673 100% 67
64.46.144.0/20 No ROA None 673 100% 67
198.175.254.0/24 No ROA None 673 100% 67
198.232.228.0/24 No ROA Other origin only 673 100% 67
206.220.156.0/23 No ROA Nonecovered by 206.220.156.0/22 3 0%low visibility 3
202.12.127.0/24 Valid RIR databaseAPNIC 546 81% 66

AS-SET

AS5716 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 46 are in fix.csv.

  • ROA: none7
  • Route object: none7
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none64.46.128.0/21No ROA covers it. Add a ROA for AS5716, maxLength 21.673 of 673
Route object: none64.46.128.0/21No route object for it. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none64.46.136.0/22No ROA covers it. Add a ROA for AS5716, maxLength 22.673 of 673
Route object: none64.46.136.0/22No route object for it. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none64.46.141.0/24No ROA covers it. Add a ROA for AS5716, maxLength 24.673 of 673
Route object: none64.46.141.0/24No route object for it. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none64.46.144.0/20No ROA covers it. Add a ROA for AS5716, maxLength 20.673 of 673
Route object: none64.46.144.0/20No route object for it. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none198.175.254.0/24No ROA covers it. Add a ROA for AS5716, maxLength 24.673 of 673
Route object: none198.175.254.0/24No route object for it. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none198.232.228.0/24No ROA covers it. Add a ROA for AS5716, maxLength 24.673 of 673
Route object: none198.232.228.0/24Route objects for it name AS21719. Add a route object with origin AS5716 in the RIR database for the space.673 of 673
ROA: none206.220.156.0/23No ROA covers it. Add a ROA for AS5716, maxLength 23.3 of 673
Route object: none206.220.156.0/23No route object for it. A route object for 206.220.156.0/22 with origin AS5716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5716 in the RIR database for the space.3 of 673

Route objects not announced

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

64.46.128.0/24RADBNo ROA
64.46.129.0/24RADBNo ROA
64.46.130.0/24RADBNo ROA
64.46.131.0/24RADBNo ROA
64.46.132.0/24RADBNo ROA
64.46.133.0/24RADBNo ROA
64.46.134.0/24RADBNo ROA
64.46.135.0/24RADBNo ROA
64.46.136.0/24RADBNo ROA
64.46.137.0/24RADBNo ROA
64.46.138.0/24RADBNo ROA
64.46.139.0/24RADBNo ROA
64.46.140.0/24RADBNo ROA
64.46.142.0/24RADBNo ROA
64.46.143.0/24RADBNo ROA
64.46.144.0/24RADBNo ROA
64.46.145.0/24RADBNo ROA
64.46.146.0/24RADBNo ROA
64.46.147.0/24RADBNo ROA
64.46.148.0/24RADBNo ROA
64.46.149.0/24RADBNo ROA
64.46.150.0/24RADBNo ROA
64.46.151.0/24RADBNo ROA
64.46.152.0/24RADBNo ROA
64.46.153.0/24RADBNo ROA
64.46.154.0/24RADBNo ROA
64.46.157.0/24RADBNo ROA
64.46.158.0/24RADBNo ROA
64.46.159.0/24RADBNo ROA
188.240.240.0/20RADBNo ROA
199.26.225.0/24RADBNo ROA
206.220.156.0/22RADBNo 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.