Network · data from 2026-11-12
AS63497 Arana Teknologi Indonesia
Registry name: ARANANETWORK-AS-ID - PT. Arana Teknologi Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63497, 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.232.242.0/24 | Valid | None | 672 100% |
| 103.250.199.0/24 | Valid | Other origin only | 672 100% |
| 103.90.25.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.232.240.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.232.243.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS63497: AS63497. 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 (AS63497 isn't in the set, or no route object for AS63497 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 | AS63497 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS63497 | A single AS number, not a set: AS63497 (this network), 11 route objects. | |||||
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 13 are in fix.csv.
- Route object: none2
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.232.242.0/24 | No route object for it. Add a route object with origin AS63497 in the RIR database for the space. |
| Route object: none | 103.250.199.0/24 | Route objects for it name AS132673. Add a route object with origin AS63497 in the RIR database for the space. |
| Route object: RIR | 103.90.25.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.232.240.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.232.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63497 whose prefix no peer sees AS63497 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.90.26.0/24 | RADB | Valid |
| 103.134.104.0/22 | APNIC | Valid |
| 103.134.104.0/23 | APNIC | Valid |
| 103.134.104.0/24 | APNIC, NTTCOM | Valid |
| 103.134.105.0/24 | APNIC | Valid |
| 103.134.106.0/23 | APNIC | Valid |
| 103.134.106.0/24 | APNIC | Valid |
| 103.134.107.0/24 | APNIC | Valid |
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.