Network · data from 2026-11-12
AS133499 HOSTROYALETECHNOLOGIES-AS-AP - HostRoyale Technologies Pvt Ltd
Registry name: HOSTROYALETECHNOLOGIES-AS-AP - HostRoyale Technologies Pvt Ltd, NZ · not in PeeringDB
63IPv4 routes
92.1% RPKI valid · 93.7% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
5No ROA
4 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
30Route objects not announced
registered with origin AS133499, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS133499, 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.
| 92.118.68.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 103.106.184.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 209.242.216.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 45.153.156.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 103.19.200.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 121.91.176.0/22 | Valid | Nonecovered by 121.91.176.0/20 | 673 100% |
| 121.91.180.0/22 | Valid | Nonecovered by 121.91.176.0/20 | 673 100% |
| 121.91.184.0/22 | Valid | Nonecovered by 121.91.176.0/20 | 673 100% |
| 121.91.188.0/22 | Valid | Nonecovered by 121.91.176.0/20 | 673 100% |
| 31.14.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.236.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 43.225.188.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.225.190.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.228.236.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.228.238.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 66.118.56.0/24 | Valid | RIR databaseARIN | 673 100% |
| 77.95.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 78.138.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.138.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.240.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.240.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.32.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.34.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.41.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.184.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 89.184.208.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.176.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.176.216.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 94.177.52.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 103.194.113.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 119.13.224.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 150.107.226.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 161.123.60.0/22 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.67.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.70.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.94.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.118.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.140.0/22 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.148.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.194.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.198.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.210.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.212.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.217.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 161.123.221.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 185.101.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.221.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.223.58.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.243.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.70.0.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.70.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 212.70.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 103.84.120.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.204.212.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 103.240.164.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.252.110.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2a12:adc0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS133499 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 39 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: not announced30
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.118.68.0/24 | No ROA covers it. Add a ROA for AS133499, maxLength 24. |
| ROA: none | 103.106.184.0/22 | No ROA covers it. Add a ROA for AS133499, maxLength 22. |
| ROA: none | 209.242.216.0/24 | No ROA covers it. Add a ROA for AS133499, maxLength 24. |
| ROA: none | 45.153.156.0/24 | No ROA covers it. Add a ROA for AS133499, maxLength 24. |
| ROA: none | 103.19.200.0/22 | No ROA covers it. Add a ROA for AS133499, maxLength 22. |
| Route object: none | 121.91.176.0/22 | No route object for it. A route object for 121.91.176.0/20 with origin AS133499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133499 in the RIR database for the space. |
| Route object: none | 121.91.180.0/22 | No route object for it. A route object for 121.91.176.0/20 with origin AS133499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133499 in the RIR database for the space. |
| Route object: none | 121.91.184.0/22 | No route object for it. A route object for 121.91.176.0/20 with origin AS133499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133499 in the RIR database for the space. |
| Route object: none | 121.91.188.0/22 | No route object for it. A route object for 121.91.176.0/20 with origin AS133499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133499 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133499 whose prefix no peer sees AS133499 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.228.238.0/24 | APNIC | Valid |
| 43.228.239.0/24 | APNIC | Valid |
| 103.75.228.0/23 | RADB | No ROA |
| 103.75.228.0/24 | RADB | No ROA |
| 103.75.229.0/24 | RADB | No ROA |
| 103.84.120.0/23 | APNIC | Valid |
| 103.84.120.0/24 | APNIC | Valid |
| 103.84.121.0/24 | APNIC | Valid |
| 103.84.122.0/23 | APNIC | Valid |
| 103.84.122.0/24 | APNIC | Valid |
| 103.84.123.0/24 | APNIC | Valid |
| 103.119.108.0/24 | APNIC | No ROA |
| 103.119.111.0/24 | APNIC | No ROA |
| 103.240.164.0/23 | APNIC | Valid |
| 103.240.164.0/24 | APNIC | Valid |
| 103.240.165.0/24 | APNIC | Valid |
| 103.240.166.0/23 | APNIC | Valid |
| 103.240.166.0/24 | APNIC | Valid |
| 103.240.167.0/24 | APNIC | Valid |
| 103.241.52.0/22 | APNIC | Valid |
| 103.241.52.0/24 | APNIC | Valid |
| 103.241.53.0/24 | APNIC | Valid |
| 103.241.54.0/24 | APNIC | Valid |
| 103.241.55.0/24 | APNIC | Valid |
| 121.91.176.0/20 | RIPE | Valid |
| 161.123.0.0/16 | AFRINIC | Valid |
| 161.123.34.0/24 | AFRINIC | Valid |
| 161.123.56.0/22 | AFRINIC | Valid |
| 161.123.64.0/24 | AFRINIC | Valid |
| 208.66.92.0/22 | ARIN | No 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.