Network · data from 2026-11-12
AS46055 ROKA LANE ASIA
Registry name: ROKA-AS-ID - PT ROKA LANE ASIA, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46055, 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.198.120.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.198.122.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 202.52.48.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.198.120.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 103.198.121.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 103.198.122.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 202.52.49.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.52.48.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 35 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS46055: AS46055:AS-ROKA. 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 (AS46055 isn't in the set, or no route object for AS46055 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 | AS46055 in it | Not covered |
|---|---|---|---|---|---|
| AS46055:AS-ROKA | APNIC | 2 | 1 | Yes | 0 |
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 11 are in fix.csv.
- Route object: RIR7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.198.120.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.198.122.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.52.48.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.198.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.198.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.198.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.52.49.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46055 whose prefix no peer sees AS46055 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.198.120.0/22 | RADB | No ROA |
| 103.198.123.0/24 | RADB | Valid |
| 103.255.29.0/24 | RADB | No ROA |
| 2403:1880::/32 | RADB | 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.