Network · data from 2026-11-12
AS24627 SHOWNET-KW-AS GULFSATCOMMUNICATIONS COMPANY K.S.C.
Registry name: SHOWNET-KW-AS GULFSATCOMMUNICATIONS COMPANY K.S.C., KW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24627, 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.
| 185.133.168.0/22 | No ROA | None | 2 0%low visibility |
| 194.126.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS24627 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 41 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.133.168.0/22 | No ROA covers it. Add a ROA for AS24627, maxLength 22. |
| Route object: none | 185.133.168.0/22 | No route object for it. Add a route object with origin AS24627 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24627 whose prefix no peer sees AS24627 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.116.128.0/19 | RADB | No ROA |
| 82.116.136.0/21 | RADB | No ROA |
| 82.116.136.0/23 | RADB | No ROA |
| 82.116.137.0/24 | RADB | No ROA |
| 82.116.138.0/23 | RADB | No ROA |
| 82.116.146.0/23 | RADB | No ROA |
| 82.116.148.0/23 | RADB | No ROA |
| 168.187.120.0/22 | RIPE | No ROA |
| 168.187.120.0/23 | RIPE | No ROA |
| 168.187.122.0/23 | RIPE | No ROA |
| 168.187.168.0/22 | RIPE | No ROA |
| 168.187.168.0/23 | RIPE | No ROA |
| 168.187.170.0/23 | RIPE | No ROA |
| 194.54.238.0/24 | RIPE | Invalid: origin |
| 194.54.240.0/23 | RIPE | Invalid: origin |
| 194.126.32.0/19 | RADB | No ROA |
| 194.126.32.0/22 | RIPE | No ROA |
| 194.126.32.0/23 | NTTCOM | No ROA |
| 194.126.32.0/24 | NTTCOM | No ROA |
| 194.126.33.0/24 | RIPE | Invalid: origin |
| 194.126.34.0/23 | RIPE | No ROA |
| 194.126.34.0/24 | RIPE | Invalid: origin |
| 194.126.35.0/24 | RIPE | No ROA |
| 194.126.39.0/24 | RADB, RIPE | No ROA |
| 194.126.42.0/24 | RADB | No ROA |
| 194.126.46.0/23 | RADB | No ROA |
| 194.126.46.0/24 | RADB, RIPE | No ROA |
| 194.126.47.0/24 | RIPE | No ROA |
| 194.126.48.0/22 | RIPE | No ROA |
| 194.126.48.0/23 | RADB | No ROA |
| 194.126.48.0/24 | RADB, RIPE | No ROA |
| 194.126.49.0/24 | RADB | No ROA |
| 194.126.54.0/23 | RIPE | No ROA |
| 194.126.56.0/22 | RIPE | No ROA |
| 194.126.58.0/23 | RIPE | No ROA |
| 194.126.58.0/24 | RIPE | No ROA |
| 194.126.59.0/24 | RIPE | No ROA |
| 194.126.60.0/24 | RIPE | No ROA |
| 2a03:5780:1000::/36 | 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.