Network · data from 2026-11-12
AS202958 Hoster-ALM LLP "Kompaniya Hoster.KZ"
Registry name: Hoster-ALM LLP "Kompaniya Hoster.KZ", KZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202958, 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.
| 185.98.6.0/24 | Invalid: origin | RIR databaseRIPE | 1 0%low visibility |
| 2a06:941:3::/48 | Valid | None | 636 100% |
| 89.126.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.126.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.4.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.140.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.105.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.107.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.108.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.109.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.110.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.141.111.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.107.198.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.107.199.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.207.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.243.71.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.98.4.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.113.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.116.192.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.116.193.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.116.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.116.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.125.88.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.125.90.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.125.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.249.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.249.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.244.115.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.4.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.4.57.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.4.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.40.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.41.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.42.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.43.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.109.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.226.123.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.246.247.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.115.14.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a06:941::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:941:2::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:941:1::/48 | Valid | RIR databaseRIPE | 3 0%low visibility |
AS-SET
AS202958 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: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.98.6.0/24 | ROAs covering it name AS200532, AS207333, not AS202958. If AS202958 should announce it, add a ROA for AS202958. |
| Route object: none | 2a06:941:3::/48 | No route object for it. Add a route object with origin AS202958 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202958 whose prefix no peer sees AS202958 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.100.66.0/24 | RIPE | Valid |
| 185.116.192.0/22 | RIPE | Invalid: origin |
| 194.4.56.0/22 | RIPE | No ROA |
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.