Network · data from 2026-11-12
AS131735 PT Telemedia Network Cakrawala
Registry name: IDNIC-TNC-ID - PT Telemedia Network Cakrawala, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131735, 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.15.240.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.15.241.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.15.242.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.15.243.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.52.65.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.52.66.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.52.67.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.52.64.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 103.231.81.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 669 99% |
| 103.231.83.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS131735: AS-TNC. 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 (AS131735 isn't in the set, or no route object for AS131735 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 | AS131735 in it | Not covered |
|---|---|---|---|---|---|
| AS-TNC | RIPE | 11 | 1 | No | 10 |
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 23 are in fix.csv.
- Route object: RIR10
- AS-SET: own ASN1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.15.240.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.15.241.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.15.242.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.15.243.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.52.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.52.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.52.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.52.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.231.81.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.231.83.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-TNC | AS131735 isn't in AS-TNC (RIPE) once expanded. Add AS131735 to it. |
Route objects not announced
Route objects with origin AS131735 whose prefix no peer sees AS131735 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.15.240.0/22 | APNIC, RADB | Valid |
| 103.15.240.0/23 | NTTCOM, RADB | Valid |
| 103.15.242.0/23 | RADB | Valid |
| 103.52.64.0/22 | APNIC | Valid |
| 103.137.124.0/23 | RADB | No ROA |
| 103.231.80.0/22 | NTTCOM, RADB | No ROA |
| 103.231.80.0/23 | NTTCOM, RADB | No ROA |
| 103.231.80.0/24 | NTTCOM, RADB | Valid |
| 103.231.82.0/23 | NTTCOM, RADB | No ROA |
| 103.231.82.0/24 | NTTCOM, RADB | Valid |
| 2001:df5:b400::/48 | NTTCOM, RADB | No ROA |
| 2001:df5:b400::/64 | NTTCOM | 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.