Network · data from 2026-11-12
AS7699 CTL-AS-AP - Cabos de Timor-Leste, E.P.
Registry name: CTL-AS-AP - Cabos de Timor-Leste, E.P., TL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7699, 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.
| 163.128.48.0/24 | No ROA | None | 425 63% |
| 163.128.49.0/24 | No ROA | None | 425 63% |
AS-SET
AS7699 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 10 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 163.128.48.0/24 | No ROA covers it. Add a ROA for AS7699, maxLength 24. |
| Route object: none | 163.128.48.0/24 | No route object for it. Add a route object with origin AS7699 in the RIR database for the space. |
| ROA: none | 163.128.49.0/24 | No ROA covers it. Add a ROA for AS7699, maxLength 24. |
| Route object: none | 163.128.49.0/24 | No route object for it. Add a route object with origin AS7699 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7699 whose prefix no peer sees AS7699 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.6.133.0/24 | RADB | No ROA |
| 203.25.241.0/24 | RADB | No ROA |
| 203.191.36.0/24 | RADB | No ROA |
| 203.191.37.0/24 | RADB | No ROA |
| 203.191.38.0/24 | RADB | No ROA |
| 203.191.39.0/24 | 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.