bgpreport

Network · data from 2026-11-12

AS197173 HIGHLIGHT-NET HIGHLIGHT APPS LTD

Registry name: HIGHLIGHT-NET HIGHLIGHT APPS LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197173, 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.27.0/24 Invalid: origin Other origin only 17 3%low visibility 17
143.20.244.0/24 Invalid: origin Other origin only 6 1%low visibility 7
69.33.192.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.24.72.0/24 Invalid: origin Other origin only 2 0%low visibility 2
157.254.204.0/24 Invalid: origin Other origin only 2 0%low visibility 2
194.26.3.0/24 Invalid: origin Other origin only 2 0%low visibility 2
209.200.232.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.83.220.0/24 Invalid: origin Other origin only 1 0%low visibility 1
95.214.175.0/24 Invalid: origin Other origin only 1 0%low visibility 1
148.135.187.0/24 Invalid: origin Other origin only 1 0%low visibility 1
217.25.6.0/24 Invalid: origin Other origin only 1 0%low visibility 1
23.226.142.0/24 No ROA Other origin only 2 0%low visibility 2
64.188.19.0/24 No ROA Other origin only 2 0%low visibility 2

AS-SET

AS197173 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 26 are in fix.csv.

  • ROA: origin11
  • ROA: none2
  • Route object: none13
ChangePrefix or setDetailFull-table peers
ROA: origin65.87.27.0/24ROAs covering it name AS14315, not AS197173. If AS197173 should announce it, add a ROA for AS197173.17 of 673
Route object: none65.87.27.0/24Route objects for it name AS14315. Add a route object with origin AS197173 in the RIR database for the space.17 of 673
ROA: origin143.20.244.0/24ROAs covering it name AS218322, not AS197173. If AS197173 should announce it, add a ROA for AS197173.6 of 673
Route object: none143.20.244.0/24Route objects for it name AS218322. Add a route object with origin AS197173 in the RIR database for the space.6 of 673
ROA: origin69.33.192.0/24ROAs covering it name AS31898, not AS197173. If AS197173 should announce it, add a ROA for AS197173.2 of 673
Route object: none69.33.192.0/24Route objects for it name AS31898. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: origin82.24.72.0/24ROAs covering it name AS834, not AS197173. If AS197173 should announce it, add a ROA for AS197173.2 of 673
Route object: none82.24.72.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: origin157.254.204.0/24ROAs covering it name AS834, not AS197173. If AS197173 should announce it, add a ROA for AS197173.2 of 673
Route object: none157.254.204.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: origin194.26.3.0/24ROAs covering it name AS47172, not AS197173. If AS197173 should announce it, add a ROA for AS197173.2 of 673
Route object: none194.26.3.0/24Route objects for it name AS47172. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: origin209.200.232.0/24ROAs covering it name AS834, not AS197173. If AS197173 should announce it, add a ROA for AS197173.2 of 673
Route object: none209.200.232.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: origin5.83.220.0/24ROAs covering it name AS834, not AS197173. If AS197173 should announce it, add a ROA for AS197173.1 of 673
Route object: none5.83.220.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.1 of 673
ROA: origin95.214.175.0/24ROAs covering it name AS152606, not AS197173. If AS197173 should announce it, add a ROA for AS197173.1 of 673
Route object: none95.214.175.0/24Route objects for it name AS152606. Add a route object with origin AS197173 in the RIR database for the space.1 of 673
ROA: origin148.135.187.0/24ROAs covering it name AS134494, not AS197173. If AS197173 should announce it, add a ROA for AS197173.1 of 673
Route object: none148.135.187.0/24Route objects for it name AS134494. Add a route object with origin AS197173 in the RIR database for the space.1 of 673
ROA: origin217.25.6.0/24ROAs covering it name AS213962, not AS197173. If AS197173 should announce it, add a ROA for AS197173.1 of 673
Route object: none217.25.6.0/24Route objects for it name AS213962. Add a route object with origin AS197173 in the RIR database for the space.1 of 673
ROA: none23.226.142.0/24No ROA covers it. Add a ROA for AS197173, maxLength 24.2 of 673
Route object: none23.226.142.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.2 of 673
ROA: none64.188.19.0/24No ROA covers it. Add a ROA for AS197173, maxLength 24.2 of 673
Route object: none64.188.19.0/24Route objects for it name AS834. Add a route object with origin AS197173 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS197173 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.