Network · data from 2026-11-12
AS24530 PT. Power Telecom
Registry name: POWERNET-AS-ID - PT. Power Telecom Indonesia, ID · PeeringDB
33IPv4 routes
100.0% RPKI valid · 100.0% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
37Route objects not announced
registered with origin AS24530, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24530, 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.178.196.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.178.196.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.178.197.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 119.10.176.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.176.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.176.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.177.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.178.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.178.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.179.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.180.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.180.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.180.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.181.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.182.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.182.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.10.183.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.48.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.48.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.48.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.50.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.50.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.51.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.52.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.52.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.53.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.54.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.54.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.55.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.190.49.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 213 32% |
| 203.190.52.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 2401:d940::/32 | Valid | Other IRR onlyNTTCOM, RADB | 4 1%low visibility |
| 2401:d940:e0ff::/48 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 119.10.176.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.190.48.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS24530: AS24530:AS-POWERID. 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 (AS24530 isn't in the set, or no route object for AS24530 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 | AS24530 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS24530:AS-POWERID | 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 71 are in fix.csv.
- Route object: RIR33
- AS-SET: not found1
- Route object: not announced37
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.178.196.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.196.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.197.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.176.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.176.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.176.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.177.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.178.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.178.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.179.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.180.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.180.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.180.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.181.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.182.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.182.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.10.183.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.48.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.48.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.48.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.50.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.50.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.51.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.52.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.52.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.53.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.54.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.54.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.55.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.49.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:d940::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:d940:e0ff::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS24530:AS-POWERID | PeeringDB names AS24530:AS-POWERID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS24530 whose prefix no peer sees AS24530 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.230.5.0/24 | NTTCOM | No ROA |
| 45.118.112.0/21 | NTTCOM | No ROA |
| 45.118.116.0/22 | NTTCOM | No ROA |
| 45.118.116.0/23 | NTTCOM | No ROA |
| 45.118.118.0/23 | NTTCOM | No ROA |
| 103.4.206.0/23 | NTTCOM | No ROA |
| 103.4.206.0/24 | NTTCOM | No ROA |
| 103.4.207.0/24 | NTTCOM | No ROA |
| 103.196.43.0/24 | NTTCOM | No ROA |
| 103.196.46.0/24 | NTTCOM | No ROA |
| 103.237.32.0/24 | NTTCOM | No ROA |
| 103.237.33.0/24 | NTTCOM | No ROA |
| 103.237.35.0/24 | NTTCOM | No ROA |
| 103.246.129.0/24 | NTTCOM, RADB | No ROA |
| 117.121.200.0/21 | RADB | No ROA |
| 119.10.160.0/21 | NTTCOM, RADB | No ROA |
| 119.10.160.0/24 | NTTCOM, RADB | No ROA |
| 119.10.161.0/24 | NTTCOM, RADB | No ROA |
| 119.10.162.0/24 | NTTCOM, RADB | No ROA |
| 119.10.163.0/24 | NTTCOM, RADB | No ROA |
| 119.10.164.0/24 | NTTCOM, RADB | No ROA |
| 119.10.165.0/24 | NTTCOM, RADB | No ROA |
| 119.10.166.0/24 | NTTCOM, RADB | No ROA |
| 119.10.167.0/24 | NTTCOM, RADB | No ROA |
| 202.57.16.0/20 | NTTCOM | No ROA |
| 202.57.16.0/21 | NTTCOM | No ROA |
| 202.57.16.0/22 | NTTCOM | No ROA |
| 202.57.16.0/23 | NTTCOM | No ROA |
| 202.57.17.0/24 | NTTCOM | No ROA |
| 202.57.18.0/23 | NTTCOM | No ROA |
| 202.57.20.0/22 | NTTCOM | No ROA |
| 202.57.22.0/23 | NTTCOM | No ROA |
| 202.57.22.0/24 | NTTCOM | No ROA |
| 202.57.23.0/24 | NTTCOM | No ROA |
| 202.57.24.0/21 | NTTCOM | No ROA |
| 202.57.24.0/22 | NTTCOM | No ROA |
| 202.61.104.0/23 | 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.