Network · data from 2026-11-12
AS131745 Cybertechtonic Pratama AS131745
Registry name: IDNIC-CYBERTECHTONIC-AS-ID - PT. Cybertechtonic Pratama, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131745, 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.
| 2400:85e0:807::/48 | Valid | Nonecovered by 2400:85e0::/32 | 341 54% |
| 103.139.175.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.241.192.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 210.247.242.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 210.247.243.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.3.215.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 2400:85e0::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:1::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:2::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:3::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:4::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:5::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:6::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:7::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:85e0:804::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 49.128.184.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 49.128.186.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 49.128.187.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.30.244.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.30.245.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.30.246.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.30.247.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.83.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.83.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.83.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.83.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 210.247.240.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 210.247.245.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 210.247.246.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 210.247.248.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 210.247.253.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 210.247.254.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 49.128.185.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.247.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.249.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.250.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.251.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.252.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.255.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.247.244.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS131745: AS-CBTP. 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 (AS131745 isn't in the set, or no route object for AS131745 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 | AS131745 in it | Not covered |
|---|---|---|---|---|---|
| AS-CBTP | RADB | 13 | 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 31 are in fix.csv.
- Route object: none1
- Route object: RIR14
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2400:85e0:807::/48 | No route object for it. A route object for 2400:85e0::/32 with origin AS131745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131745 in the RIR database for the space. |
| Route object: RIR | 103.139.175.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.241.192.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.247.242.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.247.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.3.215.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:1::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:2::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:3::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:4::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:6::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:7::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:85e0:804::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131745 whose prefix no peer sees AS131745 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 49.128.184.0/22 | APNIC, RADB | Valid |
| 49.128.184.0/23 | RADB | Valid |
| 49.128.186.0/23 | RADB | Valid |
| 103.30.244.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.30.244.0/23 | NTTCOM, RADB | Valid |
| 103.30.246.0/23 | NTTCOM, RADB | Valid |
| 103.151.190.0/24 | RADB | No ROA |
| 103.178.146.0/24 | RADB | Valid |
| 202.83.120.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.83.120.0/23 | NTTCOM, RADB | Valid |
| 202.83.122.0/23 | NTTCOM, RADB | Valid |
| 210.247.244.0/22 | RADB | No ROA |
| 210.247.248.0/22 | RADB | No ROA |
| 2400:85e0::/32 | RADB | Valid |
| 2400:85e0:8::/48 | RADB | Valid |
| 2400:85e0:9::/48 | RADB | 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.