bgpreport

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

9IPv4 routes 55.6% RPKI valid · 55.6% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
3RPKI invalid 1 origin · 2 maxLength
1No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS50819, seen from no peer

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 1
91.234.169.130/32 Invalid: maxLength Nonecovered by 91.234.168.0/23 2 0%low visibility 8
185.102.88.13/32 Invalid: maxLength Nonecovered by 185.102.88.0/22 2 0%low visibility 8
85.120.235.0/24 No ROA None 2 0%low visibility 3
91.234.168.0/23 Valid RIR databaseRIPE 673 100% 66
185.102.88.0/22 Valid RIR databaseRIPE 673 100% 66
194.1.169.0/24 Valid RIR databaseRIPE 673 100% 66
80.96.50.0/24 Valid RIR databaseRIPE 672 100% 66
185.18.226.0/23 Valid RIR databaseRIPE 672 100% 66
2a00:1480:3::/48 Valid RIR databaseRIPE 635 100% 67
2a0c:eec0::/29 Valid RIR databaseRIPE 635 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: origin185.18.224.0/23ROAs covering it name AS215160, not AS50819. If AS50819 should announce it, add a ROA for AS50819.0 of 673
Route object: none185.18.224.0/23Route objects for it name AS215160. Add a route object with origin AS50819 in the RIR database for the space.0 of 673
ROA: maxLength91.234.169.130/32ROA 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.2 of 673
Route object: none91.234.169.130/32No 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.2 of 673
ROA: maxLength185.102.88.13/32ROA 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.2 of 673
Route object: none185.102.88.13/32No 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.2 of 673
ROA: none85.120.235.0/24No ROA covers it. Add a ROA for AS50819, maxLength 24.2 of 673
Route object: none85.120.235.0/24No route object for it. Add a route object with origin AS50819 in the RIR database for the space.2 of 673

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/24RIPEInvalid: 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.