Network · data from 2026-11-12
AS154217 Fiber Akses Nusantara
Registry name: IDNIC-FIBERAKSES-ID - PT Fiber Akses Nusantara, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154217, 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.20.108.0/24 | Invalid: origin | None | 1 0%low visibility |
| 103.186.91.0/24 | Valid | Other origin only | 672 100% |
| 103.227.107.0/24 | Valid | Other origin only | 5 1%low visibility |
| 103.186.90.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.6.192.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.6.192.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2001:df6:dc0::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 202.6.193.0/24 | Valid | RIR databaseAPNIC, RADB | 135 20% |
AS-SET
PeeringDB's irr_as_set for AS154217: AS154217:AS-FIBERAKSES. 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 (AS154217 isn't in the set, or no route object for AS154217 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 | AS154217 in it | Not covered |
|---|---|---|---|---|---|
| AS154217:AS-FIBERAKSES | APNIC | 1 | 1 | Yes | 3 |
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 6 are in fix.csv.
- ROA: origin1
- Route object: none3
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.20.108.0/24 | ROAs covering it name AS55701, not AS154217. If AS154217 should announce it, add a ROA for AS154217. |
| Route object: none | 103.20.108.0/24 | No route object for it. Add a route object with origin AS154217 in the RIR database for the space. |
| Route object: none | 103.186.91.0/24 | Route objects for it name AS149707. Add a route object with origin AS154217 in the RIR database for the space. |
| Route object: none | 103.227.107.0/24 | Route objects for it name AS139934. Add a route object with origin AS154217 in the RIR database for the space. |
| Route object: RIR | 103.186.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154217 whose prefix no peer sees AS154217 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:dd6:dc0::/48 | 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.