Network · data from 2026-11-12
AS205009 HDMS HDM Solutions LTD
Registry name: HDMS HDM Solutions LTD, MH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205009, 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.
| 216.173.121.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.200.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.92.52.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 185.141.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.94.52.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.94.53.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.47.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.47.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 103.47.144.0/24 | Valid | RIR databaseAPNIC | 660 98% |
AS-SET
AS205009 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 2 are in fix.csv.
- ROA: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.173.121.0/24 | No ROA covers it. Add a ROA for AS205009, maxLength 24. |
Route objects not announced
Route objects with origin AS205009 whose prefix no peer sees AS205009 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.39.252.0/24 | 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.