Network · data from 2026-11-12
AS60680 OMANTRA-AS Telecommunications Regulatory Authority (TRA)
Registry name: OMANTRA-AS Telecommunications Regulatory Authority (TRA), OM · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60680, 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.
| 2a00:9120:1:3::/64 | Valid | Nonecovered by 2a00:9120:1::/48 | 3 0%low visibility |
| 185.27.88.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.27.89.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a00:9120:2::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:9120:1::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS60680 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a00:9120:1:3::/64 | No route object for it. A route object for 2a00:9120:1::/48 with origin AS60680 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS60680 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60680 whose prefix no peer sees AS60680 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.27.88.0/22 | RADB | 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.