bgpreport

Network · data from 2026-11-12

AS39486 HOSTROYALE HostRoyale Technologies Pvt Ltd

Registry name: HOSTROYALE HostRoyale Technologies Pvt Ltd, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39486, 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.
43.225.191.0/24 Invalid: origin Other origin only 2 0%low visibility 2
66.111.61.0/24 No ROA RIR databaseARIN 673 100% 67
185.39.8.0/24 No ROA RIR databaseRIPE 673 100% 67
165.140.199.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
43.228.237.0/24 Valid RIR databaseAPNIC 673 100% 67
103.109.244.0/24 Valid RIR databaseAPNIC 673 100% 66
103.192.205.0/24 Valid RIR databaseAPNIC 673 100% 66
171.22.248.0/23 Valid RIR databaseRIPE 673 100% 66
171.22.250.0/23 Valid RIR databaseRIPE 673 100% 66
185.184.228.0/24 Valid RIR databaseRIPE 673 100% 67
193.42.224.0/23 Valid RIR databaseRIPE 673 100% 66
193.42.226.0/23 Valid RIR databaseRIPE 673 100% 66
194.116.248.0/23 Valid RIR databaseRIPE 673 100% 66
194.116.250.0/23 Valid RIR databaseRIPE 673 100% 66
45.134.79.0/24 Valid RIR databaseRIPE 672 100% 66
193.161.128.0/22 Valid RIR databaseRIPE 671 100% 67
193.161.128.0/24 Valid RIR databaseRIPE 671 100% 67
193.161.129.0/24 Valid RIR databaseRIPE 671 100% 67
193.161.130.0/24 Valid RIR databaseRIPE 671 100% 67
193.161.131.0/24 Valid RIR databaseRIPE 671 100% 67
194.104.104.0/22 Valid RIR databaseRIPE 671 100% 67
194.104.104.0/24 Valid RIR databaseRIPE 671 100% 67
194.104.105.0/24 Valid RIR databaseRIPE 671 100% 67
194.104.106.0/24 Valid RIR databaseRIPE 671 100% 67
194.104.107.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS39486 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 5 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin43.225.191.0/24ROAs covering it name AS203020, not AS39486. If AS39486 should announce it, add a ROA for AS39486.2 of 673
Route object: none43.225.191.0/24Route objects for it name AS203020. Add a route object with origin AS39486 in the RIR database for the space.2 of 673
ROA: none66.111.61.0/24No ROA covers it. Add a ROA for AS39486, maxLength 24.673 of 673
ROA: none185.39.8.0/24No ROA covers it. Add a ROA for AS39486, maxLength 24.673 of 673
ROA: none165.140.199.0/24No ROA covers it. Add a ROA for AS39486, maxLength 24.2 of 673

Route objects not announced

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