Network · data from 2026-11-12
AS206283 YAHSAT-FRANKFURT Star Satellite Communications Company - PJSC
Registry name: YAHSAT-FRANKFURT Star Satellite Communications Company - PJSC, AE · not in PeeringDB
41IPv4 routes
82.9% RPKI valid · 97.6% with a route object
7IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
7No ROA
1 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
16Route objects not announced
registered with origin AS206283, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS206283, 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.
| 206.42.114.0/24 | No ROA | Other origin only | 670 100% |
| 204.157.156.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 102.36.223.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
| 102.223.124.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
| 102.223.125.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
| 102.223.126.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
| 102.223.127.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
| 66.37.111.0/24 | Valid | Other IRR onlyRADB | 638 95% |
| 82.180.176.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 41.92.248.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.193.254.0/23 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.18.95.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 102.215.192.0/22 | Valid | RIR databaseAFRINIC | 670 100% |
| 103.85.130.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 119.160.239.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 168.253.44.0/22 | Valid | RIR databaseAFRINIC | 670 100% |
| 168.253.48.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 175.111.6.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 185.26.26.0/23 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 185.123.20.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.123.21.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.123.22.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.243.12.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.243.14.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.243.15.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.152.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.153.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.154.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.155.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.75.16.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.17.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.18.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.19.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.20.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.21.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.75.23.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 156.238.85.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 41.193.240.0/23 | Valid | RIR databaseAFRINIC | 668 99% |
| 45.222.102.0/24 | Valid | RIR databaseAFRINIC | 668 99% |
| 2001:fe8:8f00::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:8f02::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2a02:f401::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f402::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f403::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f406:fe50::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f406:fe90::/48 | Valid | RIR databaseRIPE | 635 100% |
| 103.27.20.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 116.0.38.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS206283 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 26 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: RIR2
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.42.114.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| Route object: none | 206.42.114.0/24 | Route objects for it name AS133495, AS198949. Add a route object with origin AS206283 in the RIR database for the space. |
| ROA: none | 204.157.156.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| Route object: RIR | 204.157.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 102.36.223.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| ROA: none | 102.223.124.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| ROA: none | 102.223.125.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| ROA: none | 102.223.126.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| ROA: none | 102.223.127.0/24 | No ROA covers it. Add a ROA for AS206283, maxLength 24. |
| Route object: RIR | 66.37.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206283 whose prefix no peer sees AS206283 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.85.197.0/24 | AFRINIC | Invalid: origin |
| 41.86.11.0/24 | AFRINIC | No ROA |
| 41.87.88.0/22 | AFRINIC | Invalid: origin |
| 58.147.158.0/24 | APNIC | No ROA |
| 80.75.16.0/21 | RIPE | No ROA |
| 82.180.177.0/24 | RIPE | Invalid: maxLength |
| 82.180.178.0/23 | RIPE | Invalid: maxLength |
| 82.180.180.0/22 | RIPE | Invalid: maxLength |
| 82.180.183.0/24 | RIPE | Valid |
| 102.67.60.0/22 | AFRINIC | No ROA |
| 102.131.63.192/26 | AFRINIC | No ROA |
| 102.221.96.192/27 | AFRINIC | Invalid: origin |
| 169.239.214.0/24 | AFRINIC | No ROA |
| 185.123.23.0/24 | RIPE | No ROA |
| 204.157.157.0/24 | RADB | No ROA |
| 2a02:f406:fdc0::/42 | RIPE | No 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.