bgpreport

Network · data from 2026-11-12

AS20472 SYNN - Synergy Networks

Registry name: SYNN - Synergy Networks, US · not in PeeringDB

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

Announced routes

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

65.87.192.0/21 No ROA None 673 100% 67
63.75.167.0/24 No ROA None 2 0%low visibility 3
63.107.10.0/23 No ROA None 2 0%low visibility 2
63.109.38.0/24 No ROA None 2 0%low visibility 3
63.109.44.0/24 No ROA None 2 0%low visibility 2
63.109.45.0/24 No ROA None 2 0%low visibility 2
63.118.152.0/23 No ROA None 2 0%low visibility 2
63.126.138.0/23 No ROA None 2 0%low visibility 2
64.200.0.0/22 No ROA None 2 0%low visibility 2
64.200.4.0/22 No ROA None 2 0%low visibility 2
64.200.8.0/22 No ROA None 2 0%low visibility 2
65.193.76.0/22 No ROA None 2 0%low visibility 2
65.202.64.0/22 No ROA None 2 0%low visibility 2
67.238.54.0/24 No ROA Other origin only 2 0%low visibility 2

AS-SET

AS20472 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none14
ChangePrefix or setDetailFull-table peers
ROA: none65.87.192.0/21No ROA covers it. Add a ROA for AS20472, maxLength 21.673 of 673
Route object: none65.87.192.0/21No route object for it. Add a route object with origin AS20472 in the RIR database for the space.673 of 673
ROA: none63.75.167.0/24No ROA covers it. Add a ROA for AS20472, maxLength 24.2 of 673
Route object: none63.75.167.0/24No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.107.10.0/23No ROA covers it. Add a ROA for AS20472, maxLength 23.2 of 673
Route object: none63.107.10.0/23No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.109.38.0/24No ROA covers it. Add a ROA for AS20472, maxLength 24.2 of 673
Route object: none63.109.38.0/24No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.109.44.0/24No ROA covers it. Add a ROA for AS20472, maxLength 24.2 of 673
Route object: none63.109.44.0/24No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.109.45.0/24No ROA covers it. Add a ROA for AS20472, maxLength 24.2 of 673
Route object: none63.109.45.0/24No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.118.152.0/23No ROA covers it. Add a ROA for AS20472, maxLength 23.2 of 673
Route object: none63.118.152.0/23No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none63.126.138.0/23No ROA covers it. Add a ROA for AS20472, maxLength 23.2 of 673
Route object: none63.126.138.0/23No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none64.200.0.0/22No ROA covers it. Add a ROA for AS20472, maxLength 22.2 of 673
Route object: none64.200.0.0/22No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none64.200.4.0/22No ROA covers it. Add a ROA for AS20472, maxLength 22.2 of 673
Route object: none64.200.4.0/22No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none64.200.8.0/22No ROA covers it. Add a ROA for AS20472, maxLength 22.2 of 673
Route object: none64.200.8.0/22No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none65.193.76.0/22No ROA covers it. Add a ROA for AS20472, maxLength 22.2 of 673
Route object: none65.193.76.0/22No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none65.202.64.0/22No ROA covers it. Add a ROA for AS20472, maxLength 22.2 of 673
Route object: none65.202.64.0/22No route object for it. Add a route object with origin AS20472 in the RIR database for the space.2 of 673
ROA: none67.238.54.0/24No ROA covers it. Add a ROA for AS20472, maxLength 24.2 of 673
Route object: none67.238.54.0/24Route objects for it name AS46887. Add a route object with origin AS20472 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS20472 is announced.

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.