Network · data from 2026-11-12
AS135375 Today Communication
Registry name: TCC-AS-AP - Today Communication Co.,Ltd, KH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135375, 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.
| 38.252.150.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 38.252.150.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 38.252.151.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.133.168.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 102.165.58.0/24 | Valid | RIR databaseAFRINIC, NTTCOM, RADB | 673 100% |
| 103.63.190.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.118.44.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.118.45.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.118.46.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.118.47.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.216.48.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.216.48.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.216.49.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.216.50.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.95.196.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.95.196.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.95.197.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.95.199.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 50.114.33.0/24 | Valid | RIR databaseARIN, NTTCOM, RADB | 672 100% |
| 103.118.44.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.216.51.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.95.198.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS135375: AS-135375. 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 (AS135375 isn't in the set, or no route object for AS135375 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 | AS135375 in it | Not covered |
|---|---|---|---|---|---|
| AS-135375 | RADB | 5 | 1 | Yes | 0 |
| APNIC (also) | 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 6 are in fix.csv.
- ROA: none3
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.252.150.0/23 | No ROA covers it. Add a ROA for AS135375, maxLength 23. |
| Route object: RIR | 38.252.150.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.252.150.0/24 | No ROA covers it. Add a ROA for AS135375, maxLength 24. |
| Route object: RIR | 38.252.150.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.252.151.0/24 | No ROA covers it. Add a ROA for AS135375, maxLength 24. |
| Route object: RIR | 38.252.151.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS135375 is announced.
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.