Network · data from 2026-11-12
AS35594 HOSTERBY-AS Reliable Software, Ltd.
Registry name: HOSTERBY-AS Reliable Software, Ltd., BY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35594, 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.172.174.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 178.172.242.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 91.149.189.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.137.160.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 87.232.68.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a0a:7d80:3::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7d80:9::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS35594 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: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.172.174.0/24 | No ROA covers it. Add a ROA for AS35594, maxLength 24. |
| ROA: none | 178.172.242.0/24 | No ROA covers it. Add a ROA for AS35594, maxLength 24. |
Route objects not announced
Route objects with origin AS35594 whose prefix no peer sees AS35594 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.232.66.0/24 | RIPE | Invalid: origin |
| 2a0a:7d80:8::/48 | RIPE | No ROA |
| 2a0a:7d80:f::/48 | RIPE | Invalid: origin |
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.