bgpreport

Network · data from 2026-11-12

AS17216 DC74-AS - DC74 LLC

Registry name: DC74-AS - DC74 LLC, US · not in PeeringDB

18IPv4 routes 55.6% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS17216, seen from no peer

Announced routes

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

38.83.128.0/22 No ROA Other IRR onlyRADB 671 100% 68
155.254.246.0/23 No ROA Other IRR onlyRADB 671 100% 68
174.46.131.0/24 No ROA Other IRR onlyRADB 671 100% 68
174.46.132.0/24 No ROA Other IRR onlyRADB 671 100% 68
174.46.133.0/24 No ROA Other IRR onlyRADB 671 100% 68
174.46.134.0/24 No ROA Other IRR onlyRADB 671 100% 68
192.52.242.0/23 No ROA Other IRR onlyRADB 671 100% 68
206.53.136.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
2001:504:43::/48 No ROA RIR databaseARIN, RADB 632 99% 69
198.24.14.0/24 Valid Other IRR onlyRADB 673 100% 67
198.24.15.0/24 Valid Other IRR onlyRADB 673 100% 67
198.37.107.0/24 Valid Other IRR onlyRADB 671 100% 68
198.37.112.0/22 Valid Other IRR onlyRADB 671 100% 68
67.212.0.0/20 Valid RIR databaseARIN, RADB 671 100% 68
140.235.252.0/24 Valid RIR databaseARIN, RADB 671 100% 68
162.254.28.0/22 Valid RIR databaseARIN, RADB 671 100% 68
192.151.136.0/21 Valid RIR databaseARIN, RADB 671 100% 68
198.24.12.0/22 Valid RIR databaseARIN, RADB 671 100% 68
199.47.224.0/21 Valid RIR databaseARIN, RADB 671 100% 68
2604:9980::/32 Valid RIR databaseARIN, RADB 635 100% 69
2620:129:9000::/48 Valid RIR databaseARIN 635 100% 69

AS-SET

AS17216 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 40 are in fix.csv.

  • ROA: none9
  • Route object: RIR11
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none38.83.128.0/22No ROA covers it. Add a ROA for AS17216, maxLength 22.671 of 673
Route object: RIR38.83.128.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none155.254.246.0/23No ROA covers it. Add a ROA for AS17216, maxLength 23.671 of 673
Route object: RIR155.254.246.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none174.46.131.0/24No ROA covers it. Add a ROA for AS17216, maxLength 24.671 of 673
Route object: RIR174.46.131.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none174.46.132.0/24No ROA covers it. Add a ROA for AS17216, maxLength 24.671 of 673
Route object: RIR174.46.132.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none174.46.133.0/24No ROA covers it. Add a ROA for AS17216, maxLength 24.671 of 673
Route object: RIR174.46.133.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none174.46.134.0/24No ROA covers it. Add a ROA for AS17216, maxLength 24.671 of 673
Route object: RIR174.46.134.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.52.242.0/23No ROA covers it. Add a ROA for AS17216, maxLength 23.671 of 673
Route object: RIR192.52.242.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.53.136.0/24No ROA covers it. Add a ROA for AS17216, maxLength 24.671 of 673
ROA: none2001:504:43::/48No ROA covers it. Add a ROA for AS17216, maxLength 48.632 of 636
Route object: RIR198.24.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.24.15.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.37.107.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.37.112.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.11.124.0/24ARINNo ROA
67.212.9.0/24RADBValid
67.212.13.0/24RADBValid
67.212.14.0/24RADBValid
162.250.88.0/22RADBNo ROA
173.212.192.0/18RADBNo ROA
181.214.149.0/24RIPEInvalid: origin
181.215.47.0/24RIPEInvalid: origin
181.215.49.0/24RIPEInvalid: origin
191.96.155.0/24RIPEInvalid: origin
191.96.166.0/24RIPEInvalid: origin
191.101.172.0/24RIPEInvalid: origin
192.151.140.0/24RADBValid
198.37.112.0/20ARIN, RADBValid
199.47.95.0/24RADBNo ROA
199.47.227.0/24RADBValid
199.47.228.0/24RADBValid
199.47.231.0/24RADBValid
2604:9980::/48RADBValid
2604:9980:230::/48RADBValid

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.