Network · data from 2026-11-12
AS24725 ASN-HM LLC "Hostmaster"
Registry name: ASN-HM LLC "Hostmaster", UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24725, 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.
| 109.70.104.189/32 | Invalid: maxLength | Nonecovered by 109.70.104.0/24 | 3 0%low visibility |
| 109.70.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2001:4130::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS24725 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 8 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 109.70.104.189/32 | ROA 109.70.104.0/24 AS24725 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 109.70.104.189/32. |
| Route object: none | 109.70.104.189/32 | No route object for it. A route object for 109.70.104.0/24 with origin AS24725 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24725 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24725 whose prefix no peer sees AS24725 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.70.106.0/24 | RIPE | Valid |
| 2001:4130::/32 | RIPE | Valid |
| 2001:4130::/34 | RIPE | Valid |
| 2001:4130:18::/48 | RIPE | Valid |
| 2001:4130:107::/48 | RIPE | Valid |
| 2001:4130:50f2::/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.