bgpreport

Network · data from 2026-11-12

AS27615 HOVRS - Purple Language Services Co.

Registry name: HOVRS - Purple Language Services Co., US · not in PeeringDB

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

Announced routes

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

174.137.37.0/24 No ROA None 673 100% 67
208.17.91.0/24 No ROA None 673 100% 67
67.23.80.0/24 No ROA RIR databaseARIN 673 100% 67
67.23.82.0/24 No ROA RIR databaseARIN 673 100% 67
67.23.83.0/24 No ROA RIR databaseARIN 673 100% 67
67.23.87.0/24 No ROA RIR databaseARIN 673 100% 67
67.23.94.0/24 No ROA RIR databaseARIN 673 100% 67
162.253.29.0/24 No ROA RIR databaseARIN 673 100% 67
162.253.30.0/24 No ROA RIR databaseARIN 673 100% 67
162.253.31.0/24 No ROA RIR databaseARIN 673 100% 67
67.23.84.0/24 No ROA RIR databaseARIN 671 100% 67
67.23.85.0/24 No ROA RIR databaseARIN 671 100% 67
67.23.86.0/24 No ROA RIR databaseARIN 671 100% 67
67.23.88.0/24 No ROA RIR databaseARIN 671 100% 67

AS-SET

AS27615 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 27 are in fix.csv.

  • ROA: none14
  • Route object: none2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none174.137.37.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
Route object: none174.137.37.0/24No route object for it. Add a route object with origin AS27615 in the RIR database for the space.673 of 673
ROA: none208.17.91.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
Route object: none208.17.91.0/24No route object for it. Add a route object with origin AS27615 in the RIR database for the space.673 of 673
ROA: none67.23.80.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none67.23.82.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none67.23.83.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none67.23.87.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none67.23.94.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none162.253.29.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none162.253.30.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none162.253.31.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.673 of 673
ROA: none67.23.84.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.671 of 673
ROA: none67.23.85.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.671 of 673
ROA: none67.23.86.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.671 of 673
ROA: none67.23.88.0/24No ROA covers it. Add a ROA for AS27615, maxLength 24.671 of 673

Route objects not announced

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

12.146.25.0/24RADBNo ROA
66.150.249.0/24RADBNo ROA
67.23.81.0/24ARINNo ROA
67.23.89.0/24ARINNo ROA
67.23.90.0/24ARINNo ROA
67.23.91.0/24ARINNo ROA
67.23.92.0/24ARINNo ROA
67.23.93.0/24ARINNo ROA
67.23.95.0/24ARINNo ROA
162.253.28.0/22ARINNo ROA
162.253.28.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.