Network · data from 2026-11-12
AS201768 ISP-SAT ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD
Registry name: ISP-SAT ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD, SA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201768, 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.
| 78.93.168.0/22 | Valid | None | 673 100% |
| 78.93.172.0/22 | Valid | None | 673 100% |
| 86.60.44.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS201768 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 9 are in fix.csv.
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 78.93.168.0/22 | No route object for it. Add a route object with origin AS201768 in the RIR database for the space. |
| Route object: none | 78.93.172.0/22 | No route object for it. Add a route object with origin AS201768 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201768 whose prefix no peer sees AS201768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.240.130.0/23 | RIPE | No ROA |
| 77.240.131.0/24 | RIPE | No ROA |
| 86.60.34.0/23 | RIPE | Invalid: origin |
| 86.60.42.0/23 | RIPE | Invalid: origin |
| 89.189.224.0/19 | RIPE | No ROA |
| 213.230.0.0/19 | RIPE | No ROA |
| 213.230.4.0/24 | 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.