Network · data from 2026-11-12
AS149400 CYBERAKSES
Registry name: CYBERAKSES-AS-ID - PT Cyber Akses Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149400, 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.
| 103.70.95.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.181.249.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2401:15a0::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 103.70.94.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 202.164.220.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.164.221.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.164.220.0/23 | Valid | RIR databaseAPNIC, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS149400: AS-CYBERAKSES. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS149400 isn't in the set, or no route object for AS149400 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS149400 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-CYBERAKSES | In no IRR database read today. | |||||
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.
- Route object: RIR4
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.70.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.181.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:15a0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.70.94.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-CYBERAKSES | PeeringDB names AS-CYBERAKSES; no IRR database read has it. |
Route objects not announced
Route objects with origin AS149400 whose prefix no peer sees AS149400 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.70.94.0/23 | RADB | Valid |
| 103.181.248.0/23 | RADB | No ROA |
| 202.164.220.0/22 | APNIC | No ROA |
| 202.164.222.0/23 | APNIC | Invalid: origin |
| 202.164.222.0/24 | APNIC | Invalid: origin |
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.