Network · data from 2026-11-12
AS60064 HostPalace (Global)
Registry name: HOSTPALACE HOSTPALACE DATACENTERS LTD, GB · PeeringDB
36IPv4 routes
94.4% RPKI valid · 58.3% with a route object
6IPv6 routes
83.3% RPKI valid · 83.3% with a route object
1RPKI invalid
1 origin · 0 maxLength
2No ROA
16 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS60064, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS60064, 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.
| 2a0f:bc05::/32 | Invalid: origin | Other origin only | 27 4%low visibility |
| 84.12.255.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 208.10.32.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 149.57.26.0/24 | Valid | None | 673 100% |
| 192.142.25.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.26.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.27.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.28.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.29.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.30.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.31.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 673 100% |
| 192.142.56.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.57.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.58.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.61.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.62.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.63.0/24 | Valid | Nonecovered by 192.142.56.0/21 | 673 100% |
| 192.142.24.0/24 | Valid | Nonecovered by 192.142.24.0/21 | 663 99% |
| 5.178.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 43.239.140.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.239.141.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.239.142.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.239.143.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.194.170.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.252.221.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.252.222.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 149.18.87.0/24 | Valid | RIR databaseARIN | 673 100% |
| 149.57.4.0/24 | Valid | RIR databaseARIN | 673 100% |
| 149.57.18.0/24 | Valid | RIR databaseARIN | 673 100% |
| 149.57.152.0/24 | Valid | RIR databaseARIN | 673 100% |
| 185.63.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.142.24.0/21 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.180.170.0/23 | Valid | RIR databaseAFRINIC | 672 100% |
| 45.134.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 103.252.220.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2a04:f780::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:f781::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:f781:100::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:f781:200::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:f781:300::/40 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS60064: RIPE::AS-HOSTPALACE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS60064 isn't in the set, or no route object for AS60064 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS60064 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-HOSTPALACE | RIPE | 11 | 1 | Yes | 2 |
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: origin1
- ROA: none2
- Route object: none16
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0f:bc05::/32 | ROAs covering it name AS60781, not AS60064. If AS60064 should announce it, add a ROA for AS60064. |
| Route object: none | 2a0f:bc05::/32 | Route objects for it name AS60781. Add a route object with origin AS60064 in the RIR database for the space. |
| ROA: none | 84.12.255.0/24 | No ROA covers it. Add a ROA for AS60064, maxLength 24. |
| Route object: RIR | 84.12.255.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.10.32.0/24 | No ROA covers it. Add a ROA for AS60064, maxLength 24. |
| Route object: RIR | 208.10.32.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 149.57.26.0/24 | No route object for it. Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.25.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.26.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.27.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.28.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.29.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.30.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.31.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.56.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.57.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.58.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.61.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.62.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.63.0/24 | No route object for it. A route object for 192.142.56.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
| Route object: none | 192.142.24.0/24 | No route object for it. A route object for 192.142.24.0/21 with origin AS60064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60064 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60064 whose prefix no peer sees AS60064 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.40.160.0/24 | RIPE | Invalid: origin |
| 89.46.92.0/24 | RIPE | Invalid: origin |
| 103.71.175.0/24 | APNIC | Valid |
| 162.44.255.0/24 | ALTDB | No ROA |
| 188.214.27.0/24 | RIPE | Invalid: origin |
| 192.142.56.0/21 | AFRINIC | Valid |
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.