Network · data from 2026-11-12
AS25122 Gulfsat_Communications-AS GULFSATCOMMUNICATIONS COMPANY K.S.C.
Registry name: Gulfsat_Communications-AS GULFSATCOMMUNICATIONS COMPANY K.S.C., KW · not in PeeringDB
31IPv4 routes
12.9% RPKI valid · 96.8% with a route object
2IPv6 routes
50.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
28No ROA
2 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
51Route objects not announced
registered with origin AS25122, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS25122, 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.
| 194.126.36.0/23 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 194.126.58.0/23 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 194.126.62.0/23 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 194.126.35.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.36.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.39.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.50.0/23 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.51.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.53.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.56.0/23 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 194.126.32.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.126.37.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.40.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.41.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.42.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.46.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 194.126.50.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.57.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.59.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.62.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 194.126.32.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 194.126.38.0/23 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 194.126.49.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 194.126.52.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 194.126.56.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 194.126.60.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 194.126.61.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 2a03:5780:198::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 194.126.33.0/24 | Valid | Other origin onlycovered by 194.126.32.0/23 | 672 100% |
| 2a03:5780:197::/48 | Valid | None | 605 95% |
| 194.126.38.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 194.126.34.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 194.126.54.0/24 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
AS-SET
AS25122 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 93 are in fix.csv.
- ROA: none28
- Route object: none2
- Route object: RIR12
- Route object: not announced51
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.126.36.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| Route object: RIR | 194.126.36.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.58.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| Route object: RIR | 194.126.58.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.62.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| Route object: RIR | 194.126.62.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.35.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| Route object: RIR | 194.126.35.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.36.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| Route object: RIR | 194.126.36.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.39.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| Route object: RIR | 194.126.39.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.50.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| Route object: RIR | 194.126.50.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.51.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| Route object: RIR | 194.126.51.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.53.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| Route object: RIR | 194.126.53.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.56.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| Route object: RIR | 194.126.56.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 194.126.32.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| ROA: none | 194.126.37.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.40.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.41.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.42.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.46.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.50.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.57.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.59.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.62.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.32.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.38.0/23 | No ROA covers it. Add a ROA for AS25122, maxLength 23. |
| ROA: none | 194.126.49.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.52.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.56.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.60.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 194.126.61.0/24 | No ROA covers it. Add a ROA for AS25122, maxLength 24. |
| ROA: none | 2a03:5780:198::/48 | No ROA covers it. Add a ROA for AS25122, maxLength 48. |
| Route object: none | 194.126.33.0/24 | Route objects for it name AS24627. A route object for 194.126.32.0/23 with origin AS25122 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25122 in the RIR database for the space. |
| Route object: none | 2a03:5780:197::/48 | No route object for it. Add a route object with origin AS25122 in the RIR database for the space. |
| Route object: RIR | 194.126.38.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 194.126.34.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25122 whose prefix no peer sees AS25122 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.116.130.0/23 | RADB | No ROA |
| 82.116.136.0/21 | NTTCOM | No ROA |
| 82.116.136.0/22 | NTTCOM, RADB | No ROA |
| 82.116.136.0/23 | NTTCOM | No ROA |
| 82.116.137.0/24 | NTTCOM | No ROA |
| 82.116.138.0/23 | NTTCOM | No ROA |
| 82.116.140.0/22 | NTTCOM | No ROA |
| 82.116.140.0/23 | NTTCOM | No ROA |
| 82.116.142.0/23 | NTTCOM | No ROA |
| 82.116.144.0/21 | NTTCOM | No ROA |
| 82.116.144.0/22 | NTTCOM | No ROA |
| 82.116.144.0/23 | NTTCOM | No ROA |
| 82.116.146.0/23 | NTTCOM | No ROA |
| 82.116.148.0/22 | NTTCOM | No ROA |
| 82.116.148.0/23 | NTTCOM | No ROA |
| 82.116.150.0/23 | NTTCOM | No ROA |
| 194.54.238.0/23 | RIPE | Invalid: origin |
| 194.54.238.0/24 | RIPE | Invalid: origin |
| 194.126.32.0/19 | NTTCOM, RIPE | No ROA |
| 194.126.32.0/20 | NTTCOM | No ROA |
| 194.126.32.0/21 | NTTCOM | No ROA |
| 194.126.32.0/22 | NTTCOM | No ROA |
| 194.126.34.0/23 | NTTCOM | No ROA |
| 194.126.36.0/22 | NTTCOM | No ROA |
| 194.126.40.0/21 | NTTCOM | No ROA |
| 194.126.40.0/22 | NTTCOM | No ROA |
| 194.126.40.0/23 | NTTCOM | No ROA |
| 194.126.42.0/23 | NTTCOM, RADB | No ROA |
| 194.126.43.0/24 | NTTCOM, RIPE | No ROA |
| 194.126.44.0/22 | NTTCOM | No ROA |
| 194.126.44.0/23 | NTTCOM | No ROA |
| 194.126.44.0/24 | NTTCOM | Valid |
| 194.126.45.0/24 | NTTCOM | No ROA |
| 194.126.46.0/23 | NTTCOM, RADB | No ROA |
| 194.126.47.0/24 | NTTCOM, RIPE | No ROA |
| 194.126.48.0/20 | NTTCOM | No ROA |
| 194.126.48.0/21 | NTTCOM | No ROA |
| 194.126.48.0/22 | NTTCOM | No ROA |
| 194.126.48.0/23 | NTTCOM | No ROA |
| 194.126.48.0/24 | NTTCOM, RIPE | No ROA |
| 194.126.52.0/22 | NTTCOM | No ROA |
| 194.126.52.0/23 | NTTCOM | No ROA |
| 194.126.54.0/23 | NTTCOM | No ROA |
| 194.126.55.0/24 | NTTCOM, RIPE | No ROA |
| 194.126.56.0/21 | NTTCOM | No ROA |
| 194.126.56.0/22 | NTTCOM | No ROA |
| 194.126.58.0/24 | NTTCOM | No ROA |
| 194.126.60.0/22 | NTTCOM | No ROA |
| 194.126.60.0/23 | NTTCOM | No ROA |
| 194.126.63.0/24 | NTTCOM | No ROA |
| 2a03:5780::/48 | 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.