Network · data from 2026-11-12
AS137346 PT. Cyber Network Indonesia - Bali
Registry name: CNI-AS-ID - PT Cyber Network Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137346, 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.
| 2402:3700::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:1::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:2::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:3::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:4::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:11::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 2402:3700:13::/48 | Valid | Nonecovered by 2402:3700::/32 | 34 5%low visibility |
| 115.178.123.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.124.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.125.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.126.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.127.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 116.66.205.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 182.23.171.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.87.187.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 223.27.147.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 223.27.155.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS137346: AS137346:AS-SET-CNI. 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 (AS137346 isn't in the set, or no route object for AS137346 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 | AS137346 in it | Not covered |
|---|---|---|---|---|---|
| AS137346:AS-SET-CNI | APNIC | 5 | 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 13 are in fix.csv.
- Route object: none7
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2402:3700::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:1::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:2::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:3::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:4::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:11::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: none | 2402:3700:13::/48 | No route object for it. A route object for 2402:3700::/32 with origin AS137346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137346 in the RIR database for the space. |
| Route object: RIR | 115.178.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.124.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.125.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.126.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.127.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS137346 whose prefix no peer sees AS137346 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2402:3700::/32 | 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.