bgpreport

Network · data from 2026-11-12

AS198381 ES1 Star Satellite Communications Company - PJSC

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

23IPv4 routes 78.3% RPKI valid · 95.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 1 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS198381, seen from no peer

Announced routes

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

204.157.157.0/24 No ROA Other origin only 670 100% 67
175.111.12.0/23 No ROA Other IRR onlyRIPE-NONAUTH 2 0%low visibility 2
105.235.214.0/23 No ROA RIR databaseAFRINIC 670 100% 67
196.41.54.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 67
197.220.120.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 67
41.188.168.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 67
103.244.132.0/23 Valid RIR databaseAPNIC, RIPE-NONAUTH 670 100% 67
116.58.5.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 670 100% 67
116.58.6.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 670 100% 67
141.105.162.0/23 Valid RIR databaseRIPE 670 100% 67
175.111.1.0/24 Valid RIR databaseAPNIC 670 100% 67
175.111.8.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 670 100% 67
175.111.9.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 670 100% 67
185.12.27.0/24 Valid RIR databaseRIPE 670 100% 67
185.31.188.0/22 Valid RIR databaseRIPE 670 100% 67
80.84.136.0/24 Valid RIR databaseRIPE 669 99% 67
80.84.145.0/24 Valid RIR databaseRIPE 669 99% 67
80.84.149.0/24 Valid RIR databaseRIPE 669 99% 67
103.27.23.0/24 Valid RIR databaseAPNIC 4 1%low visibility 3
175.111.10.0/23 Valid RIR databaseAPNIC, RIPE-NONAUTH 4 1%low visibility 3
103.255.128.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 2 0%low visibility 2
103.255.129.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 2 0%low visibility 2
103.255.130.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 2 0%low visibility 2

AS-SET

AS198381 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none204.157.157.0/24No ROA covers it. Add a ROA for AS198381, maxLength 24.670 of 673
Route object: none204.157.157.0/24Route objects for it name AS133495, AS198949, AS206283. Add a route object with origin AS198381 in the RIR database for the space.670 of 673
ROA: none175.111.12.0/23No ROA covers it. Add a ROA for AS198381, maxLength 23.2 of 673
Route object: RIR175.111.12.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.2 of 673
ROA: none105.235.214.0/23No ROA covers it. Add a ROA for AS198381, maxLength 23.670 of 673
ROA: none196.41.54.0/23No ROA covers it. Add a ROA for AS198381, maxLength 23.670 of 673
ROA: none197.220.120.0/24No ROA covers it. Add a ROA for AS198381, maxLength 24.669 of 673

Route objects not announced

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

105.235.214.0/24RIPE-NONAUTHNo ROA
105.235.215.0/24RIPE-NONAUTHNo ROA
196.41.54.0/24AFRINICNo ROA
197.148.88.0/22RIPE-NONAUTHNo 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.