Network · data from 2026-11-12
AS141921 Jaringan Keluarga Bersama
Registry name: IDNIC-ISEVEN-AS-ID - PT Jaringan Keluarga Bersama, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141921, 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.
| 2001:df3:ac0::/48 | Valid | None | 635 100% |
| 103.165.155.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.178.194.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS141921: AS-JKB-ID. 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 (AS141921 isn't in the set, or no route object for AS141921 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 | AS141921 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-JKB-ID | 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 4 are in fix.csv.
- Route object: none1
- Route object: RIR2
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2001:df3:ac0::/48 | No route object for it. Add a route object with origin AS141921 in the RIR database for the space. |
| Route object: RIR | 103.165.155.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-JKB-ID | PeeringDB names AS-JKB-ID; no IRR database read has it. |
Route objects not announced
Every route object with origin AS141921 is announced.
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.