bgpreport

Network · data from 2026-11-12

AS42067 SKYBAND-AS Luna Space Digital for Information and Technology Company Ltd.

Registry name: SKYBAND-AS Luna Space Digital for Information and Technology Company Ltd., SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42067, 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.

91.151.160.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
91.151.161.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
91.151.162.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
212.93.160.0/19 Valid RIR databaseRIPE 673 100% 66
212.93.160.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.162.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.164.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.165.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.176.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.178.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.179.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.180.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.181.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.182.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.187.0/24 Valid RIR databaseRIPE 673 100% 70
212.93.188.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.189.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.190.0/24 Valid RIR databaseRIPE 673 100% 66
212.93.191.0/24 Valid RIR databaseRIPE 673 100% 66
2a00:50a0::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS42067 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 24 are in fix.csv.

  • Route object: not announced24

Route objects not announced

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

91.151.160.0/22RIPENo ROA
91.151.160.0/23RADBNo ROA
91.151.162.0/23RADBNo ROA
91.151.163.0/24RADB, RIPENo ROA
212.93.160.0/20RIPEInvalid: maxLength
212.93.161.0/24RIPEValid
212.93.163.0/24RIPEValid
212.93.166.0/24RIPEInvalid: maxLength
212.93.167.0/24RIPEInvalid: maxLength
212.93.168.0/24RIPEInvalid: maxLength
212.93.169.0/24RIPEInvalid: maxLength
212.93.170.0/24RIPEValid
212.93.171.0/24RIPEInvalid: maxLength
212.93.172.0/24RIPEInvalid: maxLength
212.93.173.0/24RIPEInvalid: maxLength
212.93.174.0/24RIPEInvalid: maxLength
212.93.175.0/24RIPEInvalid: maxLength
212.93.176.0/21RIPEInvalid: maxLength
212.93.177.0/24RIPEValid
212.93.183.0/24RIPEValid
212.93.184.0/22RIPEInvalid: maxLength
212.93.184.0/24RIPEInvalid: maxLength
212.93.185.0/24RIPEInvalid: maxLength
212.93.186.0/24RIPEValid

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.