bgpreport

Network · data from 2026-11-12

AS50939 Space RO

Registry name: SPACE-AS Space Ro SRL, RO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50939, 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.
80.96.32.6/32 Invalid: maxLength Nonecovered by 80.96.32.0/22 2 0%low visibility 6
195.88.174.0/24 No ROA RIR databaseRIPE 673 100% 67
195.88.175.0/24 No ROA RIR databaseRIPE 673 100% 67
45.134.160.0/22 Valid RIR databaseRIPE 673 100% 67
80.96.32.0/22 Valid RIR databaseRIPE 673 100% 67
194.153.236.0/22 Valid RIR databaseRIPE 673 100% 67
195.88.80.0/24 Valid RIR databaseRIPE 673 100% 67
195.88.81.0/24 Valid RIR databaseRIPE 673 100% 67
2a0f:4480::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS50939's PeeringDB record names no 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: maxLength1
  • ROA: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength80.96.32.6/32ROA 80.96.32.0/22 AS50939 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 80.96.32.6/32.2 of 673
Route object: none80.96.32.6/32No route object for it. A route object for 80.96.32.0/22 with origin AS50939 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS50939 in the RIR database for the space.2 of 673
ROA: none195.88.174.0/24No ROA covers it. Add a ROA for AS50939, maxLength 24.673 of 673
ROA: none195.88.175.0/24No ROA covers it. Add a ROA for AS50939, maxLength 24.673 of 673

Route objects not announced

Route objects with origin AS50939 whose prefix no peer sees AS50939 announce. Many are kept on purpose (backup routes, space announced only in some places).

195.88.174.0/23RIPENo 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.