Network · data from 2026-11-12
AS135942 ADSOTA-AS-VN - Adsota Corporation
Registry name: ADSOTA-AS-VN - Adsota Corporation, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135942, 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.109.36.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.109.37.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.109.38.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.109.39.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 43.239.223.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.53.170.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.53.171.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.138.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.138.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.138.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.138.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 2001:df0:3980::/48 | Valid | RIR databaseAPNIC, NTTCOM | 636 100% |
AS-SET
AS135942 isn't in PeeringDB, where networks name their AS-SET.
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 15 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.109.36.0/24 | No ROA covers it. Add a ROA for AS135942, maxLength 24. |
| Route object: RIR | 103.109.36.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.109.37.0/24 | No ROA covers it. Add a ROA for AS135942, maxLength 24. |
| Route object: RIR | 103.109.37.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.109.38.0/24 | No ROA covers it. Add a ROA for AS135942, maxLength 24. |
| Route object: RIR | 103.109.38.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.109.39.0/24 | No ROA covers it. Add a ROA for AS135942, maxLength 24. |
| Route object: RIR | 103.109.39.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135942 whose prefix no peer sees AS135942 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.239.222.0/24 | APNIC | Valid |
| 103.109.36.0/22 | NTTCOM | No ROA |
| 103.109.36.0/23 | NTTCOM, RADB | No ROA |
| 103.109.38.0/23 | NTTCOM | No ROA |
| 103.138.112.0/23 | APNIC, NTTCOM | Valid |
| 103.138.114.0/23 | APNIC, NTTCOM | Valid |
| 2001:df0:3880::/48 | APNIC, 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.