bgpreport

Network · data from 2026-11-12

AS199270 HILAT_NETWORKS HASHIKMA NGN International Communications 015LTD

Registry name: HILAT_NETWORKS HASHIKMA NGN International Communications 015LTD, IL · not in PeeringDB

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

Announced routes

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

185.110.110.0/24 No ROA Other origin only 673 100% 67
185.110.111.0/24 No ROA Other origin only 673 100% 67
2a00:66a0::/35 Valid Nonecovered by 2a00:66a0::/32 635 100% 67
185.23.172.0/23 Valid RIR databaseRIPE 672 100% 67
185.23.172.0/24 Valid RIR databaseRIPE 672 100% 67
185.23.174.0/24 Valid RIR databaseRIPE 672 100% 67
141.226.249.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS199270 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 14 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none185.110.110.0/24No ROA covers it. Add a ROA for AS199270, maxLength 24.673 of 673
Route object: none185.110.110.0/24Route objects for it name AS21145. Add a route object with origin AS199270 in the RIR database for the space.673 of 673
ROA: none185.110.111.0/24No ROA covers it. Add a ROA for AS199270, maxLength 24.673 of 673
Route object: none185.110.111.0/24Route objects for it name AS21145. Add a route object with origin AS199270 in the RIR database for the space.673 of 673
Route object: none2a00:66a0::/35No route object for it. A route object for 2a00:66a0::/32 with origin AS199270 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199270 in the RIR database for the space.635 of 636

Route objects not announced

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

85.155.94.0/24RIPEValid
185.23.173.0/24RIPEValid
213.137.80.0/24RIPEInvalid: origin
213.137.81.0/24RIPEInvalid: origin
213.169.141.0/24RIPEInvalid: origin
213.169.142.0/23RIPEInvalid: origin
213.169.142.0/24RIPEInvalid: origin
213.169.143.0/24RIPEInvalid: origin
2a00:66a0::/32RIPENo 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.