Network · data from 2026-11-12
AS38325 WTP-AS-AP - WTP
Registry name: WTP-AS-AP - WTP, SG · not in PeeringDB
52IPv4 routes
96.2% RPKI valid · 98.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
2No ROA
1 with no route object for this origin
52Low visibility
seen by under 10% of full-table peers
39Route objects not announced
registered with origin AS38325, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38325, 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.
| 119.2.33.0/24 | No ROA | Other origin onlycovered by 119.2.32.0/21 | 1 0%low visibility |
| 119.2.39.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 79.170.35.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 27.106.216.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.216.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.217.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.218.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.219.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.220.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.221.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.222.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 27.106.223.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.56.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.56.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.57.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.58.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.59.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.61.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.62.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 112.78.63.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 113.20.144.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.144.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.145.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.146.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.147.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.148.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.149.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.150.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 113.20.151.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.24.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.25.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 123.108.120.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 123.108.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 123.108.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 123.108.125.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 182.239.32.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 182.239.34.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 182.239.35.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 182.239.36.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 182.239.37.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 122.252.24.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 123.108.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 1 0%low visibility |
| 123.108.124.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 1 0%low visibility |
| 123.108.127.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 1 0%low visibility |
| 182.239.39.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
AS-SET
AS38325 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 44 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR2
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 119.2.33.0/24 | No ROA covers it. Add a ROA for AS38325, maxLength 24. |
| Route object: none | 119.2.33.0/24 | Route objects for it name AS9497, AS38823, AS45474. A route object for 119.2.32.0/21 with origin AS38325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38325 in the RIR database for the space. |
| ROA: none | 119.2.39.0/24 | No ROA covers it. Add a ROA for AS38325, maxLength 24. |
| Route object: RIR | 119.2.39.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 79.170.35.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38325 whose prefix no peer sees AS38325 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.106.216.0/22 | APNIC, NTTCOM | Valid |
| 27.106.220.0/22 | APNIC, NTTCOM | Valid |
| 79.170.32.0/21 | NTTCOM, RADB | No ROA |
| 79.170.32.0/22 | NTTCOM, RADB | No ROA |
| 79.170.32.0/23 | NTTCOM, RADB | No ROA |
| 79.170.32.0/24 | NTTCOM, RADB | No ROA |
| 79.170.33.0/24 | NTTCOM, RADB | No ROA |
| 79.170.34.0/23 | NTTCOM, RADB | No ROA |
| 79.170.34.0/24 | NTTCOM, RADB | No ROA |
| 79.170.36.0/22 | NTTCOM, RADB | No ROA |
| 79.170.36.0/23 | NTTCOM, RADB | No ROA |
| 79.170.36.0/24 | NTTCOM, RADB | No ROA |
| 79.170.38.0/23 | NTTCOM, RADB | No ROA |
| 79.170.38.0/24 | NTTCOM, RADB | No ROA |
| 79.170.39.0/24 | NTTCOM, RADB | No ROA |
| 112.78.56.0/22 | APNIC, NTTCOM | Valid |
| 112.78.56.0/23 | APNIC, NTTCOM | Valid |
| 112.78.58.0/23 | APNIC, NTTCOM | Valid |
| 112.78.60.0/22 | APNIC, NTTCOM | Valid |
| 112.78.60.0/23 | APNIC, NTTCOM | Valid |
| 112.78.62.0/23 | APNIC, NTTCOM | Valid |
| 113.20.144.0/22 | APNIC, NTTCOM, RADB | Valid |
| 113.20.148.0/22 | APNIC, NTTCOM, RADB | Valid |
| 119.2.32.0/21 | NTTCOM, RADB | No ROA |
| 119.2.36.0/22 | NTTCOM, RADB | No ROA |
| 119.2.36.0/23 | NTTCOM, RADB | No ROA |
| 119.2.36.0/24 | NTTCOM, RADB | No ROA |
| 119.2.38.0/23 | NTTCOM, RADB | No ROA |
| 119.2.38.0/24 | NTTCOM, RADB | No ROA |
| 122.252.24.0/22 | APNIC, NTTCOM, RADB | Valid |
| 122.252.28.0/22 | APNIC, NTTCOM, RADB | Valid |
| 123.108.120.0/22 | APNIC, NTTCOM | Valid |
| 123.108.124.0/22 | APNIC, NTTCOM | Valid |
| 123.108.126.0/24 | APNIC, NTTCOM | Valid |
| 182.239.32.0/22 | APNIC, NTTCOM, RADB | Valid |
| 182.239.32.0/24 | APNIC, NTTCOM, RADB | Valid |
| 182.239.33.0/24 | APNIC, NTTCOM, RADB | Valid |
| 182.239.36.0/22 | APNIC, NTTCOM, RADB | Valid |
| 182.239.38.0/24 | APNIC, NTTCOM, 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.