Network · data from 2026-11-12
AS50819 STAR-STORAGE-AS Cloud Vault SRL
Registry name: STAR-STORAGE-AS Cloud Vault SRL, RO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50819, 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.18.224.0/23 | Invalid: origin | Other origin only | 0 0%low visibility |
| 91.234.169.130/32 | Invalid: maxLength | Nonecovered by 91.234.168.0/23 | 2 0%low visibility |
| 185.102.88.13/32 | Invalid: maxLength | Nonecovered by 185.102.88.0/22 | 2 0%low visibility |
| 85.120.235.0/24 | No ROA | None | 2 0%low visibility |
| 91.234.168.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.1.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.96.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.18.226.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:1480:3::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:eec0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS50819 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 9 are in fix.csv.
- ROA: origin1
- ROA: maxLength2
- ROA: none1
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.18.224.0/23 | ROAs covering it name AS215160, not AS50819. If AS50819 should announce it, add a ROA for AS50819. |
| Route object: none | 185.18.224.0/23 | Route objects for it name AS215160. Add a route object with origin AS50819 in the RIR database for the space. |
| ROA: maxLength | 91.234.169.130/32 | ROA 91.234.168.0/23 AS50819 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 91.234.169.130/32. |
| Route object: none | 91.234.169.130/32 | No route object for it. A route object for 91.234.168.0/23 with origin AS50819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS50819 in the RIR database for the space. |
| ROA: maxLength | 185.102.88.13/32 | ROA 185.102.88.0/22 AS50819 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.102.88.13/32. |
| Route object: none | 185.102.88.13/32 | No route object for it. A route object for 185.102.88.0/22 with origin AS50819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS50819 in the RIR database for the space. |
| ROA: none | 85.120.235.0/24 | No ROA covers it. Add a ROA for AS50819, maxLength 24. |
| Route object: none | 85.120.235.0/24 | No route object for it. Add a route object with origin AS50819 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50819 whose prefix no peer sees AS50819 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.18.108.0/24 | 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.