bgpreport

Network · data from 2026-11-12

AS198247 AD1 Star Satellite Communications Company - PJSC

Registry name: AD1 Star Satellite Communications Company - PJSC, AE · not in PeeringDB

23IPv4 routes 95.7% 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
1No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS198247, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198247, 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.
175.111.14.0/23 No ROA Other IRR onlyRADB, RIPE-NONAUTH 2 0%low visibility 2
43.225.96.0/24 Valid RIR databaseAPNIC 671 100% 67
82.180.176.0/24 Valid RIR databaseRIPE 671 100% 67
103.27.21.0/24 Valid RIR databaseAPNIC 671 100% 67
103.85.129.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 671 100% 67
103.244.134.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.244.135.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
116.58.7.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 671 100% 67
119.160.236.0/24 Valid RIR databaseAPNIC 671 100% 67
119.160.237.0/24 Valid RIR databaseAPNIC 671 100% 67
119.160.238.0/24 Valid RIR databaseAPNIC 671 100% 67
141.105.160.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
175.111.7.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 671 100% 67
185.12.25.0/24 Valid RIR databaseRIPE 671 100% 67
185.26.24.0/24 Valid RIR databaseRIPE 671 100% 67
185.60.176.0/24 Valid RIR databaseRIPE 671 100% 67
185.203.228.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 671 100% 67
185.203.229.0/24 Valid RIR databaseRIPE 671 100% 67
185.203.230.0/23 Valid RIR databaseRIPE 671 100% 67
185.243.13.0/24 Valid RIR databaseRIPE 671 100% 67
195.94.28.0/24 Valid RIR databaseRIPE 671 100% 67
203.171.126.0/24 Valid RIR databaseAPNIC 671 100% 67
2001:fe8:8f01::/48 Valid RIR databaseAPNIC 634 100% 68
156.238.84.0/24 Valid RIR databaseAFRINIC, RADB 2 0%low visibility 2

AS-SET

AS198247 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none175.111.14.0/23No ROA covers it. Add a ROA for AS198247, maxLength 23.2 of 673
Route object: RIR175.111.14.0/23Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

41.188.159.0/24AFRINIC, RIPE-NONAUTHValid
58.147.159.0/24APNICNo ROA
103.244.134.0/23RIPE-NONAUTHNo ROA
117.55.196.0/24RIPE-NONAUTHNo ROA
119.160.236.0/22RIPE-NONAUTHNo ROA
185.12.26.0/24RADBNo ROA
185.26.24.0/22RADB, RIPENo ROA
196.41.52.0/23RIPE-NONAUTHNo ROA
196.41.52.0/24AFRINICNo ROA
197.211.17.0/24AFRINIC, RIPE-NONAUTHNo ROA
197.220.105.0/24RIPE-NONAUTHNo ROA
2a02:f407:4::/48RADBValid

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.