Network · data from 2026-11-12
AS202090 ACTIVECLOUD-BY-AS Aktivnie Tehnologii LLC
Registry name: ACTIVECLOUD-BY-AS Aktivnie Tehnologii LLC, BY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202090, 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.47.152.52/32 | Invalid: maxLength | Nonecovered by 185.47.152.0/23 | 5 1%low visibility |
| 185.47.153.0/24 | Valid | Nonecovered by 185.47.152.0/23 | 673 100% |
| 81.91.190.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.91.191.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.159.44.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.47.152.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.65.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.99.142.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.176.180.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.65.136.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a0c:b1c0::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS202090 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 13 are in fix.csv.
- ROA: maxLength1
- Route object: none2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.47.152.52/32 | ROA 185.47.152.0/23 AS202090 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.47.152.52/32. |
| Route object: none | 185.47.152.52/32 | No route object for it. A route object for 185.47.152.0/23 with origin AS202090 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202090 in the RIR database for the space. |
| Route object: none | 185.47.153.0/24 | No route object for it. A route object for 185.47.152.0/23 with origin AS202090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202090 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202090 whose prefix no peer sees AS202090 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.159.44.0/24 | RIPE | Valid |
| 178.159.45.0/24 | RIPE | Valid |
| 178.159.46.0/24 | RIPE | Valid |
| 178.159.47.0/24 | RIPE | Valid |
| 185.99.143.0/24 | RIPE | Valid |
| 193.176.180.0/24 | RIPE | Valid |
| 193.176.181.0/24 | RIPE | Valid |
| 193.176.182.0/24 | RIPE | Valid |
| 193.176.183.0/24 | RIPE | Valid |
| 2a0c:b1c0::/29 | 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.