Network · data from 2026-11-12
AS34587 Hillside (Technology)
Registry name: HLM2-AS Hillside (Technology) Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34587, 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.
| 178.237.162.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 5.226.176.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 5.226.177.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 5.226.178.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 5.226.180.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 5.226.182.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.160.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.161.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.163.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.164.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.165.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.170.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.172.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.173.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.174.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.237.175.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 81.94.208.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.209.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.210.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.211.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.212.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.213.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.214.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.215.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 81.94.216.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS34587's PeeringDB record names no 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 9 are in fix.csv.
- ROA: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.237.162.0/24 | No ROA covers it. Add a ROA for AS34587, maxLength 24. |
Route objects not announced
Route objects with origin AS34587 whose prefix no peer sees AS34587 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a03:a860:10::/44 | RIPE | Valid |
| 2a03:a860:11::/48 | RIPE | Valid |
| 2a03:a860:16::/48 | RIPE | Valid |
| 2a03:a860:a01::/48 | RADB, RIPE | Valid |
| 2a03:a860:a03::/48 | RIPE | Valid |
| 2a03:a860:a04::/48 | RIPE | Valid |
| 2a03:a860:a05::/48 | RADB, RIPE | Valid |
| 2a03:a860:a1d::/48 | RIPE | 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.