Network · data from 2026-11-12
AS45725 Kings Network Indonesia
Registry name: KINGS-AS-ID - Kings Network Indonesia, PT, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45725, 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:780::/48 | Valid | Nonecovered by 2402:780::/32 | 635 100% |
| 2402:780:4::/48 | Valid | Nonecovered by 2402:780::/32 | 635 100% |
| 2402:780:100::/40 | Valid | Nonecovered by 2402:780::/32 | 635 100% |
| 43.230.152.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.230.153.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.230.154.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.230.155.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.245.136.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.245.137.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.245.138.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.245.139.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.88.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.88.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.89.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.90.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.90.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.91.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.92.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.92.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.93.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.94.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.94.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.95.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.160.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.160.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.161.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.162.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.162.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.163.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.164.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.164.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.165.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.166.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.166.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.167.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.168.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.168.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.169.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.170.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.170.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.171.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.172.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.150.172.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.173.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.150.174.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.211.88.0/21 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 180.211.88.0/22 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 180.211.92.0/22 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS45725: AS45725:AS-KINGSNETWORK. 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 (AS45725 isn't in the set, or no route object for AS45725 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 | AS45725 in it | Not covered |
|---|---|---|---|---|---|
| AS45725:AS-KINGSNETWORK | APNIC | 7 | 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 19 are in fix.csv.
- Route object: none3
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2402:780::/48 | No route object for it. A route object for 2402:780::/32 with origin AS45725 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45725 in the RIR database for the space. |
| Route object: none | 2402:780:4::/48 | No route object for it. A route object for 2402:780::/32 with origin AS45725 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45725 in the RIR database for the space. |
| Route object: none | 2402:780:100::/40 | No route object for it. A route object for 2402:780::/32 with origin AS45725 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45725 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45725 whose prefix no peer sees AS45725 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.230.152.0/22 | APNIC, RADB | Valid |
| 49.0.4.0/22 | NTTCOM | No ROA |
| 49.156.20.0/22 | NTTCOM | No ROA |
| 103.245.136.0/22 | APNIC, RADB | Valid |
| 202.61.124.0/23 | NTTCOM | No ROA |
| 202.67.32.0/21 | NTTCOM | No ROA |
| 202.67.40.0/21 | NTTCOM | No ROA |
| 202.150.160.0/20 | APNIC, RADB | Valid |
| 202.150.160.0/21 | APNIC | Valid |
| 202.150.160.0/22 | APNIC | Valid |
| 202.150.164.0/22 | APNIC | Valid |
| 202.150.168.0/21 | APNIC | Valid |
| 202.150.168.0/22 | APNIC | Valid |
| 202.150.172.0/22 | APNIC | Valid |
| 202.150.174.0/23 | APNIC | Valid |
| 2402:780::/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.