bgpreport

Network · data from 2026-11-12

AS22077 RENAISSANCE-TECH - Renaissance Technologies Corp.

Registry name: RENAISSANCE-TECH - Renaissance Technologies Corp., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22077, 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.
216.223.240.0/22 No ROA Other origin only 673 100% 67
216.223.244.0/22 No ROA None 673 100% 67
216.223.240.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.242.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.244.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.246.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.252.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.253.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.254.0/24 No ROA RIR databaseARIN 673 100% 67
216.223.243.0/24 No ROA RIR databaseARIN 671 100% 67
216.223.247.0/24 No ROA RIR databaseARIN 671 100% 67

AS-SET

AS22077 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: none11
  • Route object: none2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none216.223.240.0/22No ROA covers it. Add a ROA for AS22077, maxLength 22.673 of 673
Route object: none216.223.240.0/22Route objects for it name AS7029. Add a route object with origin AS22077 in the RIR database for the space.673 of 673
ROA: none216.223.244.0/22No ROA covers it. Add a ROA for AS22077, maxLength 22.673 of 673
Route object: none216.223.244.0/22No route object for it. Add a route object with origin AS22077 in the RIR database for the space.673 of 673
ROA: none216.223.240.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.242.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.244.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.246.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.252.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.253.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.254.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.673 of 673
ROA: none216.223.243.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.671 of 673
ROA: none216.223.247.0/24No ROA covers it. Add a ROA for AS22077, maxLength 24.671 of 673

Route objects not announced

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

216.223.240.0/23ARINNo ROA
216.223.241.0/24ARINNo ROA
216.223.242.0/23ARINNo ROA
216.223.244.0/23ARINNo ROA
216.223.245.0/24ARINNo ROA
216.223.246.0/23ARINNo ROA
216.223.248.0/23ARINNo ROA
216.223.248.0/24ARINNo ROA
216.223.249.0/24ARINNo ROA
216.223.250.0/23ARINNo ROA
216.223.250.0/24ARINNo ROA
216.223.251.0/24ARINNo ROA
216.223.252.0/23ARINNo ROA
216.223.254.0/23ARINNo ROA
216.223.255.0/24ARINNo 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.